Getting Started with SKSE Plugin Development: Difference between revisions

Jump to navigation Jump to search
m
Added skse version target. The include strings error has been fixed (Yeah!!!). Added comment for post build event.
imported>Scrivener07
m (Added categories.)
imported>3Nd R1m
m (Added skse version target. The include strings error has been fixed (Yeah!!!). Added comment for post build event.)
Line 1: Line 1:
[SKSE64 2.0.0.16 Revision]
The Skyrim Script Extender (SKSE) is a tool that expands scriptings capabilities and adds additional functionality to the game, as well as allowing modders to create plugins to further extend Skyrim's scripting capacities. SKSE plugins take form as DLLs files that implement new functions into Papyrus, Creation Kit's scripting language. As you may guess, making an SKSE plugin is more difficult than a standard mod but the benefits of doing one are far greater. This guide focus on implementing new functions into Papyrus Scripting and debugging them.
The Skyrim Script Extender (SKSE) is a tool that expands scriptings capabilities and adds additional functionality to the game, as well as allowing modders to create plugins to further extend Skyrim's scripting capacities. SKSE plugins take form as DLLs files that implement new functions into Papyrus, Creation Kit's scripting language. As you may guess, making an SKSE plugin is more difficult than a standard mod but the benefits of doing one are far greater. This guide focus on implementing new functions into Papyrus Scripting and debugging them.


This page is actually in progress and doesn't provide a complete tutorial on how to make an SKSE plugin project. With any progression on our side will come further upgrade. Until then, be assured that everything that has already been laid out is correct and up-to-date.
This page is actually in progress and doesn't provide a complete tutorial on how to make an SKSE plugin project. Any progression on our side will be reflected in this guide. Until then, be assured that everything that has already been laid out is correct.


== Sources ==
== Sources ==
Line 15: Line 17:
== Requirements ==
== Requirements ==
* Skyrim Special Edition
* Skyrim Special Edition
* [https://skse.silverlock.org/ SKSE for Skyrim SE] (Also referred as SKSE64), which you should already have installed.
* [https://skse.silverlock.org/ SKSE for Skyrim SE] (Also referred to as SKSE64), which you should already have installed.
* SKSE64 source code which is included in the SKSE64 distribution (In the '''src/''' folder)
* SKSE64 source code which is included in the SKSE64 distribution (In the '''src/''' folder)
* A template SKSE Plugin.  [https://github.com/Ryan-rsm-McKenzie/CommonLibSSE/wiki Ryan's Tutorial] provide one.
* A template SKSE Plugin.  [https://github.com/Ryan-rsm-McKenzie/CommonLibSSE/wiki Ryan's Tutorial] provide one.
Line 50: Line 52:
##: The project files include post-build events that we don't want (Such as automatically moving files into Skyrim's directory).
##: The project files include post-build events that we don't want (Such as automatically moving files into Skyrim's directory).
##: To disable post-build events, navigate to '''Build Events => Post-Build Event''' and change the '''Use in build''' field to '''No'''.
##: To disable post-build events, navigate to '''Build Events => Post-Build Event''' and change the '''Use in build''' field to '''No'''.
##: This step is not necessary and having post-build events can actually be very helpful but I would recommend to either disable the feature or re-write the event according to fit your environment
## Set the C++ Language Standard
## Set the C++ Language Standard
##: Navigate to '''C/C++ => Language''' and set '''C++ Language Standard''' to '''ISO C++17 Standard (/std:c++17)'''.
##: Navigate to '''C/C++ => Language''' and set '''C++ Language Standard''' to '''ISO C++17 Standard (/std:c++17)'''.
## Force-include <string>
##: At this point, any attempt to build the solution will fail and there will be many errors [https://imgur.com/9jpNjtK (image)], with the most predominant one being <q>C2039: 'string' is not a member of 'std'</q>. In other words, many files are using the 'string' class without including the required header to do so.
##: You can fix this without manually adding #include directives by instead navigating to '''C/C++ => Advanced''' and adding "string" (without quotation) in the '''Force Include File''' field. This will automatically include the string header whenever it's required.
## Click "Apply" and then "Ok". [https://imgur.com/4DWpnzP (Image)]
## Click "Apply" and then "Ok". [https://imgur.com/4DWpnzP (Image)]


Anonymous user

Navigation menu