ModSafe

Games › Fallout 4

Fallout 4 key art

Is it safe to update Fallout 4?

Safe for Update 2026-08-18

Bethesda's recent Fallout 4 updates (next-gen, Anniversary Edition and follow-up patches) break F4SE and DLL plugins until they are rebuilt.

Verdict for Update 2026-08-18

Safe

Every patch-sensitive framework has explicit support for Update 2026-08-18. Also check Address Lib, Buffout 4 manually (Nexus-only, not counted).

Latest patch
Update 2026-08-18
Released
2026-08-18
Source
Fallout 4 Update - August 18th
Data refreshed
2026-10-15 (UTC)

Core frameworks & loaders

FrameworkStatusLatest releaseReleasedLink
Fallout 4 Script Extender (F4SE) Safe v0.7.9 2026-08-16 Source
Address Library for F4SE Plugins Check manually — — Source
Buffout 4 / Buffout 4 NG Check manually — — Source
Why these statuses?
  • F4SE: Official page (https://f4se.silverlock.org/) lists build 0.7.9 for runtime 1.11.240, matching the latest tag (Bethesda often ships updates to a beta branch first). Latest release predates patch Update 2026-08-18; compatibility is unverified — check the project page. (Date is the tagged commit on GitHub; builds are published on the official site.)
  • Address Lib: Distributed on Nexus Mods only; ModSafe does not scrape Nexus. Check the mod page.
  • Buffout 4: Original Buffout 4 is unmaintained; the NG fork is distributed on Nexus Mods only. Check the mod page.

Statuses are inferred from public release data (Steam news, GitHub, Thunderstore, Mojang/Fabric/Forge/NeoForge/Modrinth APIs). They are not guarantees — verify on each project's page before updating. Items marked “Check manually” are not counted in the verdict.

Patch-day alerts

Get patch-day alerts: know if your mods survived before you update.

Form not loading? Subscribe on beehiiv →

Fallout 4 modding FAQ

Is it safe to update Fallout 4 with mods?

Current verdict: Safe. Every patch-sensitive framework has explicit support for Update 2026-08-18. Also check Address Lib, Buffout 4 manually (Nexus-only, not counted). Latest patch tracked: Update 2026-08-18 (2026-08-18).

Why do Fallout 4 mods break after a patch?

Bethesda's recent Fallout 4 updates (next-gen, Anniversary Edition and follow-up patches) break F4SE and DLL plugins until they are rebuilt.

Which Fallout 4 frameworks does ModSafe track?

Automatically: Fallout 4 Script Extender (F4SE). Linked for manual checks (no public release API): Address Library for F4SE Plugins, Buffout 4 / Buffout 4 NG.

What do the status labels mean?

Safe: a release explicitly supports the current patch (release notes, the maintainer's official page, or a stable build for that game version). Likely safe: a release is dated after the patch but doesn't name it, or the patch is over a week old with no breakage reports on the project's issue tracker. Just patched, wait: the patch is under 7 days old and the framework hasn't updated. Breakage reported: open issues report the framework broke after the patch. Not ported yet (Minecraft): no build exists for that version. Not affected by patches: version-agnostic tools such as mod managers or generic loaders; they don't count toward the verdict.

Where does the data come from?

Game patches come from official Steam announcements (app 377160). Framework data comes from public release APIs (GitHub, Thunderstore, Fabric/Forge/NeoForge meta, Modrinth). ModSafe does not scrape Nexus Mods or SteamDB.

Patch history → · JSON → · Modding resources →