Jump to content

Give the vscode papyrus extension a try if you haven't already!


nimrodxy

Recommended Posts

We just got done adding PPJ build support and guided assistance to the extension. So this is "now easier to use than ever" as the people on TV commercials like to say.

All you have to do to try it out is:

  1. Download and install https://code.visualstudio.com/ then run it.
  2. Click the extension icon on the left (looks like four squares with a square coming loose) and type @joelday into the search panel.
  3. Click install on the papyrus extension.
  4. Click the new icon on the left that looks like a scroll.
  5. Follow the instructions that appear.

 

PPJ files are automatically detected and provide build tasks without any additional configuration. PPJ is all you need.

Everything is supported for everything except that there's no real-time debugging for Skyrim LE (Classic, Oldrim).

Features:

  • Code completion (tab)
  • IntelliSense tooltips for some in-editor docuentation
  • Syntax highlighting (of course)
  • Real-Time error checking (linting) as you type
  • Jump to definition
  • Autodetected Build Tasks
  • PPJ File Support thanks to fireundubh's Pyro tool.
  • Real-Time Debugging of script execution! (for FO4 and SSE)

And we shall not stop there.... we're still working on making it better!

Link to comment
Share on other sites

Seems interesting, but the built-in editor of the CreationKit is enough for the little bit of scripting that I am doing, but I will keep this in mind if I ever want to do anything "bigger".

Thanks!

If you're doing that little papyrus at this point then maybe you're right, though if you start doing quests the live debugger is quite handy for situations like a quest not triggering when you expect it to (since the triggers are usually in papyrus). It ends up being easier than Debug.log()

Link to comment
Share on other sites

Great work. I guess it is time to replace my own little extension now.

 

Are there any plans for functionality to write out the log file in the editor? Else, I may take out that part from my tool and make it an extension.

Technically it's not a tail but it's effectively the same thing because exactly the same debug log messages are received via the debug TCP connection and they appear in the debug console tab in the terminal pane.

 

We're pretty good about accepting PRs so if you think of a feature you'd like to have you don't really have to create your own extension unless you just want to for some reason. We have a pretty good CONTRIBUTING.md file in the repo explaining how to build the extension and add new commands. if you have any questions about adding stuff just jump on the discord here https://discord.gg/w8PNJCa (it might seem like we're idle all the time but we usually look for new messages at least once a day and are sometimes around for quite a while when working on stuff).

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...