Page contents

Offline copy of Creation Kit editor and first plugin.

Fallout 4 Creation Kit: editor, forms and first plugin

Source status: The editor interface and initial load procedure were checked against the maintained Sim Settlements Creation Kit 101 tutorial and Bethesda's Creation Kit availability notice on 2026-11-11. The local steps below have not been executed by ModDocs. Sim Settlements uses its own framework in later lessons; this chapter uses only the general Fallout 4 Creation Kit concepts from its introductory lesson.

What the editor changes

Fallout 4's game data consists of forms in master and plugin files. The Creation Kit displays those forms in the Object Window. A form represents a definition such as an item, actor, quest, door or static object. A placed reference is an instance of a form in a cell. Editing an existing form creates an override in your plugin; duplicating or creating one gives you a new form. Keeping that distinction in mind prevents two common mistakes: editing a base-game item when you intended a separate variant, and creating a new item but never placing or distributing it so that it can appear in play.

The plugin records the form edits and dependencies. A model, texture, compiled script or other external file may be a separate asset that the plugin references. The assets chapter covers staging those files. A plugin that loads in the editor can still fail in game when a required asset is absent from the release.

Prepare the game and editor

Record the installed Fallout 4 version, Creation Kit version, DLC, and active mod profile. Bethesda's August 2026 update notes include Creation Kit and archive changes, so do not use an old tool build as an unlabelled baseline. Preserve a copy of the current plugin and a disposable test save. Keep the editable project, release staging folder and installed test copy distinct.

In the Creation Kit choose File > Data, select Fallout4.esm and only the additional masters needed for the intended change, then load them. The Sim Settlements tutorial documents Fallout4.esm as the initial master and explains that loading may take time. Before editing, save a uniquely named plugin and reopen it as the active file. If you cannot reopen and save it, resolve the editor or file-path problem before authoring content. Never save changes into a game master.

Learn the working windows

The Object Window has a category tree and a filtered form list. Search for a known item or world object and inspect its Editor ID and form type. The Cell View selects a worldspace and a cell; interiors are separate cells, while exterior worldspaces contain connected areas. Double-clicking a cell loads it into the Render Window. The Render Window is for placed references and visual layout. The Sim Settlements lesson documents camera orbit, pan and zoom, selection, and transform helpers. Work slowly with an isolated test cell: accidental movement of an existing reference is an actual plugin change, even if your intended task was only to look around.

An editor preview answers a narrow question: what the current editor has loaded. It does not prove that the plugin was enabled in the game, that the target cell is reachable, or that packaged resources resolve. For a change to an existing form, the Object Window and a record comparison in FO4Edit are usually better first checks than opening a random cell.

Create one controlled form change

Choose a form with a visible, repeatable result. Decide in advance whether you need a new form or an override of an existing one. If you need a new form, duplicate a suitable form in the relevant Object Window category, give it a distinctive Editor ID, and change one property. If you need to alter an existing item globally, edit that form deliberately and note its Form ID, the field changed, and the intended outcome. A unique Editor ID helps you locate your authored form; the Form ID identifies the record in plugin comparisons. Do not assume a renamed Editor ID creates a separate record if the editor is offering to rename the existing one.

Save the plugin, close and reopen it, and inspect your changed form. Open the plugin in FO4Edit, check the required masters and compare its record with earlier columns. The records and conflicts chapter explains how to distinguish an intentional override from a conflict needing a patch. At this point, record the exact plugin filename, Form ID, Editor ID, changed fields and whether the form is an override or new definition.

Make the result reachable and test it

A new form does not automatically appear in the player's inventory or world. Give the test an explicit route: for example, place a reference in a disposable test cell, add the item to a controlled distribution mechanism, or use a version-checked test command. Record the route so another person can reproduce it without guessing. For a placed reference, inspect the selected cell and reference after saving; for an item, verify the acquisition path and its actual in-game behavior.

Enable the staged plugin in a clean test profile with its masters. Check the intended result in game, then save, reload and repeat. Compare against a fresh test save when initialization may matter. A failed result should be narrowed in this order: plugin activation, missing masters, wrong record or cell, unreachable content, later override, missing asset, then script/runtime behavior. Do not keep adding changes to a plugin whose first small test is still unexplained.

Release boundary and remaining work

Copy only the plugin and its authored dependencies into release staging. Test that staged copy with development files removed from the load path. Preserve source files, an unmodified prior release and the pre-test save. Publish the game/tool builds, master requirements, changed records, installation instructions, and removal limits. The BA2 release chapter covers asset packaging; Papyrus activation covers scripts. A complete field-by-field item, NPC or settlement object tutorial still needs its own source audit and recorded in-game run.