Back to the town ↗

FATE DAT modding

Change items, catalogs, textures, and assets. Start with a small content mod.

Reborn 0.3.0 early alphaModAPI 2.0.0Updated 18 November 2026

Before you begin

Change items, spells, monsters, textures, and models without writing a script. This guide starts with a small price change, then explains how to package and test it in Reborn 0.3.0.

DAT files come from classic FATE. The mod.json file, partial-record updates, and core targets described here are Reborn features. Original FATE uses a different installation process.

Start with data and assets#

Open DAT files in a plain-text editor and save as UTF-8. Make sure mod.json and items.dat don't have a hidden .txt extension. Keep the tags and field names intact, and change one thing at a time.

For models, choose Legacy 3D modelling to work with FATE formats, or Blender and GLB modelling to use Reborn's exporter. Use Reborn script modding when your mod needs new behavior.

Make a small DAT mod#

This example changes the Fishing Pole's base value. Create these folders and files:

text
FishingPolePrice/
  mod.json
  Data/
    ITEMS/
      items.dat

Save this as mod.json. Replace the example ID and author before sharing your mod.

json
{
  "schema": 1,
  "id": "example.fishing_pole_price",
  "name": "Fishing Pole Price",
  "author": "Your name",
  "version": "1.0.0",
  "kind": "reborn",
  "api": ">=2.0.0 <3.0.0",
  "game": ">=0.3.0 <0.4.0",
  "content": "Data",
  "targets": ["fate"],
  "description": "Changes the base Fishing Pole value."
}

Save this as Data/ITEMS/items.dat:

text
[ITEM]
<NAME>:Fishing Pole
<VALUE>:150
[/ITEM]

Reborn keeps the Fishing Pole's other fields, so you don't need to copy its whole record, model, or icon. Vendor prices can still differ from the base value. Check a newly generated Fishing Pole; an item already in a save may keep its old definition.

This package was checked in the released 0.3.0 build: the combined item record kept its other fields and used a base value of 150.

How DAT composition works#

Reborn loads enabled mods in order. A later asset file replaces an earlier one at the same path. For the catalogs below, it combines records with the same NAME, ignoring letter case. Fields you leave out keep their earlier values.

FileRecord group
ITEMS/items.datITEM
SPELLS/spells.datSPELL
MONSTERS/monsters.datMONSTER
PARTICLES/particles.datPARTICLE
PARTICLES/glows.datGLOW

Repeated or nested fields can replace a whole group of earlier fields. REQUIRES merges by statistic. Other DAT files may use different rules. Give records clear, unique names: duplicate or ambiguous names can prevent a patch from loading.

Use data_mode replace only when you want to replace an entire catalog. This can remove expansion records. Use catalog_replacements to limit replacement to specific supported lowercase catalog paths.

To remove a field or record, create a JSON file and put its package-relative path in the manifest's patches field:

json
[
  {"file":"items/items.dat", "record":"Example Item",
   "remove_fields":["EFFECT"]},
  {"file":"items/items.dat", "record":"Another Example Item",
   "delete_record":true}
]

Replace the example names with real records. These removals run after your mod's DAT changes and before later mods. You cannot remove NAME.

Target FATE and expansion content deliberately#

A core is the set of content for one game. FATE is always active. Undiscovered Realms must be installed, located, and enabled in Mods. Apply core changes and restart the game.

To use one content folder for both games:

json
"targets": ["fate", "undiscovered_realms"]

To give each game different files:

json
"targets": {
  "fate": "Data/FATE",
  "undiscovered_realms": "Data/UR"
}

An array of targets uses the folder named by content. An object selects a folder for each core. Asset mounts and GLB paths start inside that selected folder. If you share a model_overrides map, include its GLB in each target folder. Use separate packages if the maps need to differ.

Listing both games allows the mod to run with either; it doesn't require UR unless you also declare that requirement. UR-only content needs the UR core. Package dependencies, requires_installations, and source_edition requirements still apply. TS and TCK core names are reserved for future support.

UR combines its root and realm catalogs, including Goldshare, before applying mods. Assets resolve within their core and texture context. Check UR variants separately, even when their filenames match FATE's. Enabling UR also doesn't add every UR item to FATE's loot or shops.

The Apply across all cores option extends eligible legacy mods with one shared folder to other supported cores after a restart. It doesn't change script scope or packages with separate target folders.

Add textures icons and models#

For a replacement, keep the original game-relative path inside your content folder. Add a DAT change if a record needs to point to a newly named asset.

Reborn supports PNG transparency on supported icon paths. Keep the existing ICON fields and image dimensions, then check the inventory and tooltip. Classic FATE still uses its separate alpha-mask conventions.

For a color image with a separate alpha mask, follow Make a transparent icon in PhotoCraft.

Some legacy data uses virtual paths such as MODS/Name or REALMS/Name. Map those to a folder inside your content directory with asset_mounts:

json
"asset_mounts": {"MODS/MyPack": "Assets"}

Static GLB overrides#

To replace the Buckler's model with a GLB, add this mapping to mod.json:

json
"model_overrides": {
  "items/shieldround2.mdl": "Models/my_shield.glb"
}

Models/my_shield.glb is relative to content. Include the file in every target folder that uses the mapping. See the Buckler walkthrough for the full example.

Keep the original origin, scale, and attachment alignment. For example, moving a weapon's origin can move its grip. The original model still supplies collision and attachment data, so changing its appearance won't change those.

Use embedded buffers and images, UV0 textures, and opaque, nonmetallic base-color materials. Morph targets, arbitrary Blender shaders, transparent scenery effects, and general animated-creature replacements aren't supported by this static workflow.

Declare identity dependencies and settings#

Keep your mod's id the same across updates and increase version for each release. IDs accept lowercase letters, digits, dots, underscores, and hyphens. A prefix based on your name helps avoid clashes. Versions use X.Y.Z.

The game and api fields set compatible version ranges. Widen them after testing the versions you want to support.

FieldUse it for
requiresRequired mods and their version ranges
optional_requiresVersion requirements when an optional mod is installed
load_after / load_beforeLoad order; these do not install a dependency
conflictsKnown incompatible mods
requires_installationsRequired original-game installations
website / contributors / source_metadataLinks, credits, and source information

Reborn rejects invalid dependencies and circular load orders. For settings and script configuration, see Reborn script modding.

Install diagnose and test#

  1. Keep your editable mod folder somewhere separate from the game.
  2. Extract any ZIP. In Mods, choose Open Mods folder and copy in the complete FishingPolePrice folder, with mod.json directly inside it.
  3. Return to Mods and choose Refresh. Enable the mod, check its dependencies and load order, then choose Apply changes and Restart now.
  4. Open Mods again and check that the mod is loaded before testing a disposable character or copied save. For this example, inspect a newly generated Fishing Pole.

Enlarge the game window if the top-row controls are hidden. Install folder is another way to copy a mod: select the folder containing mod.json, rather than its parent or the ZIP.

Portable installs store mods in Data/mods beside the launcher. After editing your working files, close the game, update the installed copy, and restart to see the changes.

Test each core you plan to support, first with your mod alone and then with other mods likely to affect the same files. Check save/reload and what happens when your mod is updated or removed. Removing content used by a save can make that save incompatible.

If something fails, open the Mods diagnostics and copy the report. Include the Reborn build, mod ID and version, active cores, load order, and steps to reproduce the problem.

Package and maintain your mod#

ZIP one folder with mod.json at its root and all referenced files inside. Include a short README with installation steps, supported versions and cores, settings, known conflicts, credits, and any save or removal risks.

Leave out Blender projects, editor caches, personal settings, test saves, and unrelated game files. Share only assets you have permission to distribute. Keep your editable source and backups separately, and give each release its own versioned archive.