Given that Bethesda has released newer updates (1.6.659 and 1.6.1170), why would anyone deliberately stay on 1.6.640?
While the DLLs go in the root folder, the scripts belong in your mod manager:
This keeps your game directory clean and helps with troubleshooting. skyrim skse 1.6.640
Versions after 1.6.640 introduced more aggressive Steam-integrated Creations Club updates, which added unwanted "mods" to your load order. Staying on 1.6.640 allows you to use the Downgrade Patcher to remove the Creations menu bloat while keeping AE content.
This critical stability mod (by aers) requires a DLL compiled specifically for the game version. Version 6.0.0 of Engine Fixes was the first to formally support SKSE 1.6.640, addressing the SaveGame max file size bug and tree LOD memory leaks. Downgrading to 1.5.97 was common until this release. Given that Bethesda has released newer updates ( 1
Unlike earlier SE versions where offsets were hardcoded, SKSE 1.6.640 works in tandem with the Address Library for SKSE Plugins (version AE). This library maps IDA-style signatures to actual memory addresses, allowing a single plugin compiled for 1.6.640 to work across minor AE updates (e.g., 1.6.640 → 1.6.659) without recompilation—provided the vtable layout remains unchanged.
1.6.640 works seamlessly with .NET Script Framework’s various replacements (like Crash Logger and Scrambled Bugs). Newer versions may lack support for certain backend tools. This keeps your game directory clean and helps
Before you launch your game, verify each box:
If all of these are true, you now have one of the most stable, powerful, and well-supported versions of modded Skyrim in existence. Version 1.6.640 might be a middle child in Bethesda’s update timeline, but for the savvy modder, it is the Gold Standard.