Engine guides
ENGINE PLAYBOOK

Creation Engine / Gamebryo

For Bethesda single-player games, begin with records and a separate mod profile. Native plugins come later.

Read the original playbook
RECOMMENDED ROUTE

Separate profile → record or asset edit → conflict check

Identification clues in a local game install:

Data/*.esm*.bsa or *.ba2 archivesSkyrimSE.exe / Fallout4.exe
FROM IDEA TO TEST

A practical first workflow

STEP 01

Create an isolated profile

Use Mod Organizer 2 or a suitable mod manager with a new profile. Back up saves and record the game edition, runtime, and installed master files.

STEP 02

Choose the smallest tool

Use xEdit for record changes and the Creation Kit for supported world or quest editing. Add Papyrus or the game-specific script extender only when the idea requires it.

STEP 03

Inspect conflicts and test

Check load order and conflicting records. Test on a disposable save. Confirm the changed item or quest in game before adding more content.

What can trip you up

  • Runtime updates can break script-extender plugins; verify the exact supported version.
  • Removing scripted mods mid-save can damage that save. Fallout 76’s online client is excluded.
MAKE IT YOURS

Start with this prompt

Adapt the game and idea to your own copy. This is a planning prompt, not a promise that a mod will work on every version.

Use universal-modder to plan a small single-player Skyrim Special Edition mod. Verify my runtime and master files, then choose a simple record edit in xEdit or the Creation Kit. Use an isolated mod-manager profile and a disposable save. Explain conflicts and ask before changing game files. Avoid a script extender unless the idea needs it.
READY FOR YOUR CODING AGENT
Set up your agent

Games in this family

Unofficial guide · universal-modder by rehan-remade, MIT · Reviewed October 4, 2026. Source: upstream engine playbook.