Difference between revisions of "Sublime Text"
m
changed user home directory in the previous edit to the proper variable used by the Python scripts
imported>Qazaaq (Added categories) |
imported>Nemesis m (changed user home directory in the previous edit to the proper variable used by the Python scripts) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 16: | Line 16: | ||
====If no previous Papyrus plugin==== | ====If no previous Papyrus plugin==== | ||
#In Sublime, press CTRL + SHIFT + P to type the command: "PapyrusF4" -> PapyrusF4 INI: Create default INI file | #In Sublime, press CTRL + SHIFT + P to type the command: "PapyrusF4" -> PapyrusF4 INI: Create default INI file. This will create the file <code>%USERPROFILE%\Documents\SublimePapyrusF4.ini</code> and open it in the editor. | ||
#Make the following changes: | #Make the following changes: | ||
#*Point "scripts=" at your script ''source'' folder | #*Point "scripts=" at your script ''source'' folder | ||
| Line 100: | Line 100: | ||
===Assembling and Disassembling Papyrus PEX files=== | ===Assembling and Disassembling Papyrus PEX files=== | ||
If you open a PEX file in Sublime it will show up as a binary file. If you set the "syntax" (via the View menu) to "Compiled PapyrusF4" and hit "Build", Sublime | If you open a PEX file in Sublime it will show up as a binary file. If you set the "syntax" (via the View menu) to "Compiled PapyrusF4" and hit "Build", Sublime will disassemble the PEX file for you into a PAS file which will then be auto-opened in Sublime with proper syntax coloring. | ||
Note that the PEX file needs to be in an "output" folder specified in the ini file for this to work. | Note that the PEX file needs to be in an "output" folder specified in the ini file for this to work. | ||