Skyrim Special Edition is a ten-year-old game that Bethesda patched twice within a single week this August. Bethesda’s update post is titled “The Elder Scrolls V: Skyrim Anniversary Edition - Update 1.7.99 (Updated Aug 27)”, and the independent MODLAG tracker records the build now public on Steam as 1.7.104, build 24914197, dated 27 August 2026. Two builds a week apart is the problem in miniature: the gap between a list that boots and one that crashes on the main menu is usually a single number.
What this covers: the live version triangle (game build, SKSE build, Address Library), what the August 2026 patches changed, both load-order budgets, and where Mod Organizer 2 and Vortex stand. Why it matters: SKSE is compiled for one exact game version, so a Steam patch invalidates the whole scripted layer at once — and the Anniversary-versus-1.5.97 choice decides which mods exist for you at all. Who should care: anyone starting a 2026 mod list, and anyone returning to a list that last booted before August.
The version triangle, as of 29 October 2026
Three numbers have to agree before a scripted mod loads. The game build is what Steam gives you; the SKSE build is compiled against exactly that; the Address Library is the version database most SKSE plugins need to find engine functions.
| Line | Game build | SKSE build | Who is on it |
|---|---|---|---|
| Current Steam build | 1.7.104 | 2.3.1 | Every install that took the August updates — the 2026 default |
| Previous Steam build | 1.7.99 | 2.3.0 | Installs that have not taken the 27 August hotfix |
| Legacy Special Edition | 1.5.97 | 2.0.20 | Deliberately downgraded or update-blocked installs |
| GOG Anniversary Edition | 1.6.1179 | 2.2.6 | GOG installs, which sit on a different build |
| Skyrim VR | 1.4.15 | 2.0.12 | VR, which has its own SKSE build and ecosystem |
Columns one to three come from the SKSE team’s download page, which lists “Current Anniversary Edition build 2.3.1 (game version 1.7.104)”, “Current Special Edition build 2.0.20 (game version 1.5.97)”, “Current GOG Anniversary Edition build 2.2.6 (game version 1.6.1179)” and “Current VR build 2.0.12 (game version 1.4.15)”. The 1.7.99 row comes from MODLAG’s patch log: “Aug 20, 2026 SKSE 2.3.0 released for game version 1.7.99”, then “Aug 27, 2026 SKSE 2.3.1 released for game version 1.7.104”.
Read the GOG row twice. A GOG copy of the Anniversary Edition is on 1.6.1179, not 1.7.104, so it needs SKSE 2.2.6 — a mismatch baked in at step one.
What the August 2026 patches changed
Bethesda’s summary: the update “increases console mod storage limits and brings more Creations improvements and fixes”. Most of the list is console-facing — mod storage at 15 GB on PlayStation 5 and Xbox, “expanded to approximately 16 GB” on PlayStation 4, Creations bundling to match Fallout and Starfield.
For PC the useful half is the Creation Kit list: Localization export support, “Search and Replace” aligned with Starfield, and a change aimed at large plugin trees — “Creation Kit will now allow multiple master loads by default.”
The crash list is where PC hardware appears: “Fixed a crash when the player opens the Virtual Keyboard on a Steam Deck device” and “Fixed a crash when the player transforms into a new race”. The second matters to modders, because race transformation is what a custom-race mod does.
What the PC notes do not contain is a gameplay overhaul. The meaningful effect on a modded install was the version bump itself. MODLAG puts SKSE 2.3.0 on the same day as 1.7.99 and 2.3.1 on the same day as 1.7.104 — faster than the norm it measures: across eight Steam updates since November 2017, a median wait of 0.5 days and a longest of 4 days. The SKSE page timestamped the run-up: “2026-08-14: After two and a half years, Bethesda has announced an incoming update to Skyrim. Please be prepared.”
Pin the version before you download anything
The SKSE team’s compatibility statement should drive your order of operations: “SKSE will support the latest version of Skyrim available on Steam, and only this version.” There is no build for a test branch you opted into, and none for last month’s patch once a new one ships.
The escape route is the one the page describes for the old line: “The older build supporting 1.5.97 is still around to support people who have downgraded their installation or otherwise prevented updates.” That is the whole justification for the legacy row above — and why some guides still present 1.5.97 as current.
Two hard limits: SKSE “does not support the Windows Store/Game Pass release of Skyrim”, because “Windows Store applications are locked down similarly to consoles”, and it “does not support the Epic Games Store release of Skyrim.” Steam lists the game on Windows only; on the other two storefronts you are limited to plugin-and-asset mods.
Take a copy of the game folder once a list works. Steam’s update delivery is not negotiable, and “Please be prepared” is the SKSE team acknowledging that the next patch restarts this clock.
The scripted layer fails in a fixed order
MODLAG states the mechanism plainly: “SKSE, the Skyrim Script Extender, works with the exact game version it was built for. When Bethesda updates Skyrim, SKSE and every SKSE plugin stop loading until the SKSE team releases a new build. After that, plugins built on Address Library usually work again as soon as Address Library is updated; others wait for their authors. Mods that are only plugins (.esp, .esm, .esl) and assets don’t use SKSE and keep working.”
That last sentence is the one people miss. A texture pack, a mesh replacer, a landscape overhaul — none of it cares which build you are on. When a patch lands, the blast radius is the scripted subset.
Diagnosis order, from the SKSE page’s troubleshooting text:
- Confirm the game launches without SKSE — “make sure that your game launches properly without SKSE first”. If it does not, the fault is plugins or assets.
- On a startup crash after a patch, “Remove the files from Data/SKSE/Plugins and try again. Mods using plugins probably need to be updated.”
- Read the logs:
skse.log,skse_loader.logandskse_steam_loader.loginMy Documents/My Games/Skyrim/SKSE/.
If the game boots but a feature is dead, the Address Library is the suspect before the mod. MODLAG records “Address Library v13 — Supports game version 1.7.104”, released 27 August 2026, the same day as the build. Since November 2021 its history shows a median of 0 days and a longest gap of 10 days.
Load order is two budgets, not one
Most load-order folklore is about 255. The real rule is a split budget: non-flagged ESM and ESP plugins allow “a maximum of 254 plugins”, while ESL — Elder Scrolls Light Master — files are separate, and “up to 4096 ESL plugins can exist in the load order”.
| Budget | Ceiling | Notes |
|---|---|---|
| Non-flagged ESM/ESP plugins | 254 | The classic ceiling; ESM files are pinned to the top |
| ESL (light) plugins | 4096 entries in the load order | A separate space, not carved out of the 254 |
| Records inside one ESL | 4096 since build 1.6.1130; 2048 before | The old cap reserved form IDs 0x0000–0x07FF |
| Hardcoded masters | 5, in fixed order | Skyrim.esm, Update.esm, Dawnguard.esm, HearthFires.esm, Dragonborn.esm |
Two rows are load-bearing for the Anniversary decision. ESL files “were introduced with the addition of Creation Club content known as Creations in update 1.5 of the Special Edition” — so a 1.5.97 install has the format under older rules: “Since v1.6.1130, ESL plugins can hold up to 4096 records. Before, the form ID range 0x0000 to range 0x07FF was reserved, resulting in a 2048 record limit.” An ESL built against the current build can use form IDs a 1.5.97 install cannot address, which surfaces as missing records rather than a clean refusal.
UESP also flags a subtler cost: “ESP files (which are not flagged as ESL) have a special behavior in which all references they contain are treated as permanent”, counting against the engine’s reference cap. Its own guidance is to prefer ESL or ESL-flagged ESP where possible — a mod-author decision, but it explains why a well-built list sits past 254 entries while a badly built one stutters.
The hardcoded masters and the sorting are LOOT’s job. LOOT builds a rule graph — “a real load order graph can contain thousands of vertices and over a hundred thousand edges” — and adds hard rules for hardcoded positions in “the various versions of Skyrim and Fallout 4”. LOOT 0.29.2 shipped on 16 August 2026.
Sorting does not resolve conflicts: two mods editing one record is a decision you make. For what a raised ceiling does and does not buy you, our Fallout 4 breakdown of the 1024-archive limit covers the same problem in the same engine family.
Anniversary versus Special is two questions
The phrase bundles two decisions with nothing in common, and separating them resolves most of the confusion.
Question one: which build? The current line, 1.7.104, or the frozen 1.5.97 line. This is a mod-availability question. The current line gets SKSE 2.3.1, Address Library v13 and everything still maintained; 1.5.97 gets SKSE 2.0.20, whatever was last updated before the Anniversary Edition shipped, and the 2048-record ESL ceiling.
Question two: do you own the Creation Club content? Steam’s description says the Anniversary Edition “includes a decade worth of content: the critically acclaimed core game and add-ons of Skyrim Special Edition, plus Creation Club content released on or prior to November 11, 2021 - including quests, dungeons, bosses, weapons, spells, and more.” Steam lists “The Elder Scrolls V: Skyrim Anniversary Upgrade” separately as content for the base game, and lists “The Elder Scrolls V: Skyrim Special Edition - Creations” as its own store item — so the 2021-vintage content and the newer Creations catalogue are separate things.
Here is the naming trap. SKSE calls its current build the “Anniversary Edition build”, and instructs: “If you are using the latest version on Steam, download the AE build.” That label tracks the 1.6-and-later version line, not a licence check. A Special Edition owner who never bought the upgrade, on 1.7.104, uses SKSE 2.3.1 exactly as an Anniversary owner does. The two diverge in their Data folder, not in their extender.
That divergence matters for load order, because the 2021 content arrives as plugin files. Light plugins occupy the 4096-entry ESL space rather than one of the 254 ESP slots, so the practical cost is smaller than the size of the drop suggests — but not zero, which is why two players comparing plugin counts can legitimately disagree.
Both managers are alive; their cadences are not alike
| Tool | Newest stable | Cadence note |
|---|---|---|
| Mod Organizer 2 | v2.5.2, 4 August 2024 | Stable but slow: 2.5.x is still the public release |
| Vortex | 2.9.1, 27 October 2026 | Fast: 2.10.0-beta.3 shipped the same day as stable |
| LOOT | 0.29.2, 16 August 2026 | Standalone sorter, newer than MO2’s bundled library |
MO2’s documentation says it “can be downloaded from GitHub or Nexus Mods”, that “the installer version is usually preferred for ease of installation”, and that the installer “can still be used to create a portable installation of MO2” — the portable route keeping a list out of your user profile. Its 2.5.2 notes record unchanged requirements: “Windows 10 1809+ or Windows 11 are now required due to the upgrade to Qt 6 and Python 3.11.” The same notes add “support for Creations parsing from ContentCatalog.txt” and state that “LOOT support is now automatically enabled with the addition of libloot 0.23.0.”
That libloot version is the catch. MO2’s built-in sorting is pinned to a library from its 2024 build, while standalone LOOT is on 0.29.2 as of August 2026. For current sorting metadata, run the standalone sorter and let it write the load order.
Vortex is the mirror image. Its 2.9.1 release, published 27 October 2026, lists two changes: “Restored the Manual apply (Deploy) button in the Mods page toolbar” and “Create support bundles as zip so they can go on GitHub issues” — what a mature tool’s changelog looks like. The 2.10.0 beta runs in parallel.
Neither manager changes the arithmetic above: both hand the same plugin list to the same engine, and the difference is where files sit.
A build order that survives the next patch
- Decide the version line first, before downloading mods. Current build (1.7.104) unless an abandoned mod forces 1.5.97.
- Install SKSE for that exact build — 2.3.1 for 1.7.104, 2.0.20 for 1.5.97, 2.2.6 for GOG’s 1.6.1179, 2.0.12 for VR.
- Install the matching Address Library (v13 for 1.7.104) and launch once on vanilla-plus-extender before adding anything scripted.
- Keep the scripted subset small and identifiable. It is the only part a patch can break; a list where you know your dozen SKSE-dependent mods is repairable in an afternoon.
- Sort with standalone LOOT, then hand-fix conflicts. Sorting produces an order; it does not decide which record should win.
- Snapshot the working folder, profile and
plugins.txt. The next patch restarts the clock, as the SKSE team has said in writing. - Check the tracker, not the forum thread. MODLAG reads Steam, skse.silverlock.org and Nexus every ten minutes and states: “Every loader supports build 1.7.104. Safe to update and launch through SKSE.”
That last line is dated 27 August 2026 and is the only status claim here worth re-checking before you act. Everything else is a mechanism that holds across patches.
What this guide does not claim
Bethesda did not print a version number in the August notes, so the link between the “Update 1.7.99 (Updated Aug 27)” post and build 1.7.104 rests on MODLAG, which dates the public Steam build to 27 August 2026 — the same date as the hotfix section of that post. Treat the build number as tracker-sourced, the notes as publisher-sourced.
Nor does this guide count the Creation Club items in the Anniversary Edition, quote prices (the store quotes local currency), or assert compatibility for any specific mod. MODLAG says as much about itself: “Not affiliated with Bethesda Softworks, ZeniMax Media, the SKSE team, meh321 or Nexus Mods.” For how another RPGRPG. Role-Playing Game — a game built around character progression, story, and player choices. handles a comparable ceiling, our Baldur’s Gate 3 mod primer covers vetting and console limits.