How to Mod Fallout 4 with Universal Modder

To mod Fallout 4 with AI, install Universal Modder, read your actual Fallout4.exe version, and have the agent plan a small data plugin that you test on a separate save. The agent inspects the installation, identifies the record to change and reviews the package. Use FO4Edit or Bethesda's Creation Kit for the authoring task, then confirm the result in the game.

Start with a data plugin; add F4SE only when you need its interfaces.

Can Universal Modder mod Fallout 4?

Fallout 4's Creation Engine exposes several routes. Data plugins cover records such as items and quests; Papyrus covers scripted behavior; F4SE native plugins serve changes that need additional engine interfaces. Start with the least complex route that expresses your feature, and move up only when it cannot.

Bethesda distributes the Fallout 4 Creation Kit on Steam as a free PC editor. FO4Edit is xEdit's Fallout 4 mode; the xEdit documentation covers record inspection and conflict resolution. The tools provide a development route, while a Universal Modder plan keeps dependencies, changed files and verification explicit.

This guide covers a local PC test setup. Fallout 4 VR has a distinct runtime and extender build. A console's mod distribution route does not make desktop native plugin DLLs usable there.

If you are comparing RPG authoring tools, Baldur's Gate 3 starts with one resource override in its official Toolkit. The Elden Ring guide covers a separate offline route with stricter native-code version boundaries. Use the game guide directory to choose a first project before taking on an extender-dependent feature.

What you need

• Your own PC installation, its storefront and the actual Fallout4.exe runtime version.
• A list of installed DLC and other masters required by the intended plugin.
• An agent with Universal Modder installed, plus a project folder and change log.
• FO4Edit for a small record patch, or the Creation Kit for the editor workflows your feature needs.
• A separate manager profile and test save, with backups of the active save and configuration folders.

Use the mod manager already responsible for the installation. A Vortex-managed deployment and an MO2 virtual profile expose files differently; establish what the editor and game will actually see. Avoid mixing an agent's manual edits with an unexplained manager deployment.

F4SE versions are runtime-specific

F4SE is optional for the proposed data-only first step. If another dependency requires it, the F4SE page pairs each build with a game runtime:

Pick the build that matches your runtime rather than changing your game's version. F4SE lists Steam and GOG versions separately and does not support the Windows Store release. Check the page for newer pairs before downloading, and inspect each native plugin's requirements separately.

Step-by-step

1. Read the runtime and deployment state

In the agent's terminal:

um kb search "Fallout 4"
um scan "Fallout 4" --json

Read the actual scan rather than assuming it found the right installation. It identifies a route and installed tools; check their compatibility yourself. See the scan command reference.

In PowerShell on the machine with the game, replace the path with your actual executable:

(Get-Item "C:\PATH_TO_YOUR_INSTALL\Fallout4.exe").VersionInfo.FileVersion

Record the output, storefront, manager profile, masters and launch command in MODDING_PLAN.md. If using F4SE, compare the game runtime with the installed f4se_<runtime>.dll; do not infer the former from the latter.

2. Establish a baseline and backup

Use a separate practice save in the intended profile. Record whether it starts before adding your patch. Close the game, locate the active saves and configuration—commonly under Documents/My Games/Fallout4, but verify redirected or profile-specific paths—and back them up. The backup reference explains how to preview a restore without applying it.

Preserve the manager's enabled-plugin list and deployment state alongside the save backup. Define the baseline item or behavior you will compare. A before-and-after test is useful only when the profile and other active mods remain known.

3. Plan one record change

A suitable first request is one existing item's displayed name in a test profile. Have the agent identify its actual record and source plugin before proposing the edit. Choose an item whose result you can inspect directly and avoid quests, save-dependent scripts and large world changes for this first pass.

Write down the record identity, current value, intended value, required masters, output plugin name and the exact game check. A displayed name and an internal identifier are different facts; preserve both in the log. Do not invent a FormID from memory.

4. Author your own patch

Launch FO4Edit in Fallout 4 mode with the manager's intended files and required masters available. Find the selected record and compare any existing overrides. Use Copy as override into to create a separately named patch, then make the agreed change in that patch. Keep source masters unchanged and let the tool maintain the patch's references. The xEdit manual's patch workflow explains the operation.

Review the new plugin before saving: it should contain only the intended override and required metadata. For a larger content or world-editing task, choose the Creation Kit's matching workflow instead of making the agent synthesize binary records. The first patch does not need custom textures, archive merging or a native DLL.

Keep the initial plugin format straightforward. An .esl filename or light flag has record-format constraints; changing an extension is not a general conversion method. Revisit light plugins only after understanding the project's records and downstream dependencies.

5. Activate and verify the patch

Add your own plugin through the manager, enable it in the test profile and inspect the resulting active order. Confirm that the intended override wins for the selected record. Then launch the practice setup and inspect the exact item or behavior from the plan.

For the name-change exercise, obtain a fresh instance of the identified item where practical, check its displayed text and confirm unrelated properties remain unchanged. Restart the practice session and repeat. Record the actual plugin version, profile and observations in MODLOG.md; a saved plugin or a successful menu launch is not the behavior check.

If the selected feature needs F4SE, also inspect extender and plugin diagnostics for that launch. A data-only patch does not acquire an F4SE requirement merely because an extender exists in the installation.

6. Package and recover deliberately

Keep a clean staging directory with your patch and its installation, dependency and removal notes. Check it with the package-review command, and inspect the files yourself. Do not include game executables, masters, extracted assets or private logs as convenient dependencies.

For a removal test, close the game and disable only your experiment through the manager. Compare with the pre-change practice save. Important saves that used custom or scripted content need their original compatible environment; do not use them to discover whether removal is safe.

Example prompts

More variants are in the prompt library.

Use Universal Modder to investigate my Fallout 4 test profile read-only.
Record Fallout4.exe FileVersion, storefront, manager deployment, masters,
F4SE target version and the requirements of installed native plugins.
Separate confirmed facts from unknowns. Do not upgrade or remove anything
until the proposed compatible group and recovery plan are reviewable.

Plan one item-name override in a new FO4Edit patch for this profile.
Identify the exact record and source plugin, show the current winning value,
and list required masters. Keep the original master unchanged.
Define a fresh-item check, reload check and pre-change-save recovery step.

My patch is enabled but the item still has its old name.
Compare the actual deployed plugin, selected profile, record identity,
winning override and the item being inspected. Propose one focused check
at a time and keep the rest of the load order unchanged.

Mods people built for Fallout 4

Universal Modder's Fallout 4 work so far is investigation, not a finished mod. Its most useful finding is a mismatch worth checking on your own install: f4se_1_11_221.dll sitting beside Address Library files named for 1.10.x. Read Fallout4.exe's version and find out which installed plugins use that library before changing either one; installing a single database file is not a fix on its own.

To understand records and light-module constraints before your first patch, read the plugin record-format notes on GitHub. For finished projects in other games, browse the case studies.

Known issues and fixes

F4SE reports an unsupported runtime. Read the executable version and compare it with the extender build actually launched. Keep storefront and VR status in the report. Choose the supported pair, then recheck dependent plugins as well; replacing the extender alone leaves them unchanged.

An Address Library database is missing. First establish whether the failing plugin uses it. CommonLibF4's ID database loader looks for Data/F4SE/Plugins/version-<runtime>.bin for the non-VR runtime and fails if it cannot open the file. Install a compatible database only when its release and plugin requirements support your runtime. Do not rename an old file to the requested name or delete older databases merely because they differ.

The editor reports a missing master. Compare the patch's master list with the profile's installed DLC and plugins. Supply the required legitimate dependency or choose a different first record. Do not remove a master declaration to silence the error while its references remain.

The patch loads but its effect disappears. Reopen the active files in FO4Edit and inspect the winning override. Another plugin or a different deployment profile may explain the result. A conflict color alone does not identify an unwanted change; compare the actual field values and retain intentional overrides.

An agent suggests merging archives or compacting records immediately. Keep that separate from the one-record exercise. Archive packing rules and size thresholds still need case-by-case checks, so do not treat merging or compacting as an automatic repair for every missing texture or load-order problem.

If you still cannot identify the failed stage, collect the runtime, profile, relevant error and smallest reproducible change using the troubleshooting guide. Mark any result you have not seen in the game as unconfirmed.