Skip to content

Raw / DataTables loader

Folder: RuneSchema/mods/<ModName>/raw/

Supported DataTable row creation and patching.

← Loader reference

/raw creates or patches supported DataTable rows.

{
  "DT_WearableEquipment": {
    "mymod_legs": {
      "Defense": 20.0,
      "MagicResistance": 5.0
    }
  }
}

The top-level key may be a unique short name or the exact cooked DataTable object path:

{
  "/Game/MyMod/Data/DT_Custom.DT_Custom": {
    "ExistingRow": {"SomeField": 10},
    "NewRow": {"SomeField": 20}
  }
}

Use the exact path for custom tables or whenever a short name could be ambiguous. A registry-patch document adds stricter ownership, preconditions, and all-or-nothing row operations. See schemas/registry-patch-v1.schema.json and examples/RegistryPatch.

Do not guess nested layouts from a USMAP alone. RuneSchema compares the target against live reflection before committing a row.

Simple rules

  • Use a unique DataTable short name or an exact cooked object path as the top-level key and the row name below it.
  • RuneSchema checks the target row's live reflected structure. Supplied fields that exist are written; unknown fields are reported.
  • Use a registry-patch document with target.objectPath when you need an exact cooked DataTable path or stricter ownership/precondition handling.

FAQ

FAQ-RAW-001 — Can /raw edit a DataTable that RuneSchema does not have a special loader for?

Usually yes, as long as RuneSchema can resolve the DataTable and the row/field layout matches live Unreal reflection. The classic raw editor is generic: it looks up each supplied property on the target row struct rather than requiring a hard-coded implementation for every DataTable.

FAQ-RAW-002 — Can I use a full cooked DataTable path as the top-level key?

Yes. Use /Game/.../DT_Name.DT_Name. Exact paths are recommended for modded tables and ambiguous short names.

FAQ-RAW-003 — What happens if I specify a field that does not exist on the row struct?

RuneSchema does not blindly write it. The loader checks the reflected row property; an unknown field is reported instead of being treated as a valid property.

FAQ-RAW-004 — Do I need to provide every field in an existing row?

No. For an existing row, provide the fields you intend to change. RuneSchema writes the matching reflected properties you supplied.

Working examples

← All loaders · Authoring guide