IN LAYMAN TERMS WHAT DOES WIRESHARK DO MOD
IN LAYMAN TERMS WHAT DOES WIRESHARK DO FULL
IN LAYMAN TERMS WHAT DOES WIRESHARK DO CODE

Other data is inlined and more difficult to hook, because you have no way of finding it, and the compiler can have done arbitrary transformations after inlineing (such as totally eliminating the code you wanted to hook!). Note that not all game functions are easy r/skyrimmods/comments/rxkp4q/in_laymans_terms_what_does_skse_do/# to hook, the easiest are when you want to hook a virtual function, those are very easy to find by looking at RTTI (runtime type information) data, and are basically never inlined).

The majority of the 'work' that goes into skse is probably reverse engineering the game's runtime data structures to allow hooking. Skse.dll (through a codepath that I haven't figured out yet, it's not via a call from DllMain) then goes through and patches game functions to add hooks, and loads skse plugins into the game (plugins just get loaded with LoadLibrary from skse, they don't need to do IAT hooking or copy shellcode to be executed by a remote thread). Then again you can just pass -forcesteam to skse and it works fine on non-steam executables. This is probably not to hard to fix once you understand both mo2's and skse's injection techniques completely. That said for whatever reason if skse is in the 'non-steam' mode mod-organizers filesystem hooks load after skse, meaning skse won't be redirected when loading plugins. From what I can tell it does IAT hooking so that it can load after the game has unpacked itself (the executable is encrypted with 'steam DRM' on steam, on other platforms skse won't do the IAT hooking and will load itself more directly. It contains loading and hooking mechanisms for skyrim's engine.įor loading it creates a remote thread, then hooks the IAT to load skse.dll. This means that the possibilities for modding are only limited by how well we can understand the game engine's inner workings (which is quite challenging there's a lot of code to understand). When we create these kinds of mods, we're basically working at the same level as the game itself: we can do anything that it (or any other program on your computer) can do. Our DLL can then make the same kinds of temporary changes to Skyrim as SKSE itself.

IN LAYMAN TERMS WHAT DOES WIRESHARK DO MOD

Mod authors can write program code and publish it as a DLL, and SKSE will then load that DLL and cooperate with it. However, SKSE also allows us to do the same thing.

The creators of SKSE know what parts of the game to overwrite as a result of intense, close study. (There are safety measures that prevent this, because it's almost never done on purpose, but a program can tell Windows, 'No, I really do want to be able to edit this part of my RAM.') This is basically what SKSE does to Skyrim: it wraps around Skyrim and then overwrites Skyrim's RAM directly.

IN LAYMAN TERMS WHAT DOES WIRESHARK DO FULL

When you run a program on your computer, the program's full code is copied into RAM and is run from there this means that in theory, programs can actually make temporary changes to their own code while they run. The basic idea is that it literally just overwrites Skyrim's code. In order to explain what that means, we need to talk a little bit about how SKSE works. For mod authors with very specific, very rare skills, SKSE can be used to change literally any part of the game engine. Other folks have provided great explanations of SKSE's main function - adding more script functions allowing mod authors to do more things - but there's another important feature to SKSE that I want to dive deeper into.

In layman terms what does wireshark do