CommonLibSSE VS CommonLibSSE-NG

Because SkyrimSE.exe has a Steam-related code inside. There's a solution though, you can use Steamless to disable it. This is safe even for SKSE DLL plugins and SKSE itself, more to say - many authors use this solution for develop purposes because it allows to attach VS debugger. Ryan aka Fudgyduff also mentions it in his CommonLibSSE Getting Started guide.

Since this small class is used by a lot of things (including the ones I mentioned), a lot of classes have also have their size / layout changed. This may be useful to check: https://github.com/Ryan-rsm-McKenzie/CommonLibSSE/commit/84070934c639a4c1eb074a29124387f5c29b600e

SKSE plugin development doesn't get any easier than CommonLibSSE. The NG fork has significantly more documentation and lets you compile SKSE plugins that support Skyrim SE, AE, and VR simultaneously.

That's not correct anymore. CommonLibSSE-NG is a fork of CommonLibSSE that allows plugin developers to build SKSE plugins that support Skyrim SE, AE, and VR¹ simultaneously. No need for separate builds or separate downloads. Plugins that were already built on CommonLibSSE need very few changes, and the vcpkg-centric workflow vastly simplifies building projects.

If you're looking to go for an SKSE DLL plugin in C++, I'd recommend basing it on CommonLibSSE which abstracts the SKSE API pretty nicely.

Are there any resources to get started with SKSE plugin development? I watched this video but it was mostly about setting up the development environment. I also read this from the Creation Kit wiki which led me here but the docs in this tutorial are a little advanced. As far as I can tell, the example plugin doesn't interact with the game itself so I still have no idea where to start 😔

SKSE DLL plugins that base themselves on CommonLibSSE as opposed to basically fully custom reverse engineered don't tend to have nearly as many issues porting to newer builds of the game, FWIW.

My error log looks like this. I have also tried to follow this tutorial, but I assume it is outdated. I got stuck in it in the build phase as well, and the errors were mostly about missing "common_v14".

If you want to try it out, download the SKSE source and try making something with it. SKSE has a decent amount of the game reversed, commonlibsse has a lot more (alandtse also has a version of it for VR). A huge amount of the game is still unexplored, but a lot of it has been figured out. The VR-specific things less-so, because the RE scene for the vr game is very very small. My mods are all open source, but they are probably pretty hard to get to build as they require things like headers that have the havok object definitions.

If I were to set out to do this, I'd find the github repo for a plugin that got upgraded to the NG variation of CommonLibSE, and read the commit history to see how the modder went about doing it. I took a look at one of these a while back, and it's mostly pulling in the NG library, telling cmake about the new library, then walking through all the places where the APIs changed. You might want to find a Discord where the plugin authors hang out to get some head starts on dealing with the API changes.

You can technically write an SKSE plugin in any language (see PluginAPI.h for the minimum requirements your DLL must provide), but all of the interesting middleware that makes writing a plugin easier is in C++. I would highly suggest looking at https://github.com/CharmedBaryon/CommonLibSSE-NG. It wraps many gameplay objects with a modern interface, and does a lot to help abstract over the differences between different patches of the game.

Next Gen. It's a term used for mods that utilize the CommonLibSSE-NG which makes this NG DLL mods work on any Skyrim SE version.

Ask them if they would be willing to move it over to the CLIB-NG framework, it only requires building one plugin, and maintaining updates for future SKSE versions only requires editing one line

Please note that I am NOT trying to ask this in a sarcastic way. I've seen some SKSE plugin authors say in their descriptions that their plugin works with all game versions due to being build with CommonLibSSE-NG. Given that there was only a 5 hour gap between the release of POISE - Stagger Overhaul SKSE and POISE - Stagger Overhaul - NG, it seems like its a relatively quick process. Is this just not something that can be done with any plugin?

I know nothing of developing plugins, so this probably isnt even useful for you, but someone made a fork of CommonLibSSE for it to be able to support multiple versions of the game with a single .dll, its is what mods like True Directional Movement uses. It should make the port more straight forward and the documentation seems pretty good.

SKSE plugin development doesn't get any easier than CommonLibSSE. The NG fork has significantly more documentation and lets you compile SKSE plugins that support Skyrim SE, AE, and VR simultaneously.

It means the plugin was built using the CommonLibSSE-NG framework, NG stands for Next Gen