ctrl+shift+p filters: :st2 :st3 :win :osx :linux

Papyrus Assembly

by Cipscis ALL

A Sublime package for viewing and editing Papyrus at the assembly level.


  • 2012.
  • github.​com
  • github.​com
  • 12 years ago
  • 2 hours ago
  • 12 years ago


  • Total 2K
  • Win 2K
  • Mac 171
  • Linux 177
Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30 Mar 29 Mar 28 Mar 27 Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8 Mar 7 Mar 6 Mar 5 Mar 4 Mar 3 Mar 2
Windows 0 0 0 0 0 0 1 0 1 0 0 0 1 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0



Papyrus Assembly package for Sublime Text 2

Author:Cipscis (Mark Hanna)


This is a package for Sublime Text 2 that makes it easier to view Papyrus assembly files (file extension .pas). Papyrus is the scripting language used by the video game Skyrim, which can be modified via the Creation Kit. These files can be generated in 2 ways:

  • Running the Papyrus compiler with either the -keepasm or -asmonly command line arguments. The former compiles the script but keeps the assembly file, whereas the latter does not compile the script and only generates the assembly file.
  • Running the Papyrus assembler with the -D command line argument to disassemble a compiled script (file extension .pex).

Papyrus assembly can be converted into fully compiled Papyrus scripts by running it through the Papyrus assembler. A build system is included in the package to make this easy.


Extract the "Papyrus Assembly" folder into the Packages directory for your Sublime Text 2 installation. This directory can be opened easily by selecting Preferences > Browse Packages... in Sublime Text 2.

That's it. Now you should be able to open files with the .pas extension in Sublime Text 2 and they'll automatically use the syntax highlighting I've defined.

A build system for disassembling compiled Papyrus files is also included in this package.


  • < 1.4 to >= 1.4 - If you're updating to version 1.4 or higher from a version prior to 1.4, you should also delete the following file from your Packages/User directory: Disassemble Papyrus.sublime-build
  • 1.4 to 1.5 - If you're updating from version 1.4 to version 1.5, you should also delete the Compiled Papyrus directory from your Packages directory.


Just delete the Papyrus Assembly folder from your Packages directory to uninstall this package.


To assemble these files into fully compiled scripts, press your Build keyboard shortcut (Ctrl+B or F7 both work by default) or select Build under Tools. For this to work, either Papyrus Assembly or Automatic need to be selected under Tools > Build System.

To use the Disassemble Papyrus build system to generate assembly files from compiled scripts, open up the compiled script in Sublime Text 2 (it should have a file extension of .pex), just run the build system either from Build under Tools or via the keyboard shortcut. Either Disassemble Papyrus or Automatic should be selected under Tools > Build System.

If either of the build packages doesn't work right away, you may need to alter them to match your Skyrim installation directory. Open up the relevant .sublime-build file and edit the path to match your Skyrim installation directory.

Generating Assembly Files

If you're a Sublime Text 2 user and a Papyrus scripter, you probably already have the Papyrus build system set up, thanks to the instructions on the Creation Kit Wiki. If not, I suggest you do that now - Sublime Text Setup

Note that the Papyrus Compiler and Papyrus Assembler are both components of the Creation Kit.

In order to easily generate Papyrus assembly files, I recommend you manually edit your ScriptCompile.bat file (in the Papyrus Compiler folder in your Skyrim installation directory) to include the -keepasm command line argument.

Assembly files are generated in the same folder as the compiled script, not the source.

Here is the usage information for the Papyrus compiler as reported via its -? command line argument:

PapyrusCompiler <object or folder> [<arguments>]

  object     Specifies the object to compile. (-all is not specified)
  folder     Specifies the folder to compile. (-all is specified)
  arguments  One or more of the following:
    Turns on compiler debugging, outputting dev information to the screen.
    Turns on optimization of scripts.
    Sets the compiler's output directory.
    Sets the compiler's import directories, separated by semicolons.
    Sets the file to use for user-defined flags.
    Invokes the compiler against all psc files in the specified directory
    (interprets object as the folder).
    Does not report progress or success (only failures).
    Does not generate an assembly file and does not run the assembler.
    Keeps the assembly file after running the assembler.
    Generates an assembly file but does not run the assembler.
    Prints usage information.

Here is the usage information for the Papyrus assembler as reported via its -? command line argument:

PapyrusAssembler object [-D] [-V] [-Q] [-A] [-S] [-?]

  object  Specifies the object to be assembled or disassembled. Assembly looks
          for a ".pas" extension. Disassembly looks for a ".pex" extension.
  -D      Disassembles the object, instead of assembling it.
  -V      Turns on verbose mode.
  -Q      Turns on quiet mode. (No status messages, only errors)
  -A      Do not assemble/disassemble the file, just load and analyze.
  -S      Strips debugging info from a compiled file. Cannot be used with -A
          or -D
  -?      Prints this usage information

Keep in mind that the compiler expects a file extension, whereas the assembler expects the file name without an extension.

Change Log

  • 1.0 - 12th September 2012
    • Initial Release
  • 1.1 - 12th September 2012
    • Added syntax highlighting for semicolon line comments outside of code. These comments are generated in disassembled files generated by the assembler, not assembly files generated by the compiler
    • Fixed terminology for assembly files generated by the assembler - should read "disassembled", not "decompiled". Renamed Decompile Papyrus build system to Disassemble Papyrus
  • 1.2 - 14th September 2012
  • 1.3 - 25th September 2012
    • Added JUMPT (JUMP if True) instruction
  • 1.3.1 - 25th September 2012
    • Made highlighting case-insensitive, so highlighting is also applied to disassembled files, for example
  • 1.4 - 26th September 2012
    • Added blank syntax highlighting for compiled Papyrus and updated "Disassemble Papyrus" build sytem. This means .pex files can be opened in Sublime Text 2 and the Disassemble Papyrus build system will automatically be used. This build file has been moved from the User directory into its own package.
  • 1.5 - 2nd October 2012
    • Added highlighting for escaped characters in strings. In particular, this prevents strings containing a double quote (escaped as \") from causing issues with strings not closing correctly.
    • Combined both Papyrus Assembly and Compiled Papyrus into a single package, as there was no benefit to separating them.
    • Removed case sensitivity from non-code assembly markup.
    • Removed inappropriate entity labelling to fix symbol search.
    • Added highlighting for incomplete lines for when you're writing your own assembly code.


Feel free to edit and redistribute this file (in edited or unedited form) anywhere you like without contacting me. I ask only the following:

  • Include adequate documentation, preferably this readme (potentially modified as appropriate)
  • Please provide a link to the original download location on Skyrim Nexus
  • If the package is unedited, please credit me as the author
  • If the package is edited, please credit me as the author of the original package and include in your documentation the version number of the package that you used as a template for your modified package