UE DataTable Editor

Edit Unreal Engine DataTable configuration through JSON files — auto-discover projects, search, modify, validate, and import back to the engine.

Overview

UE projects commonly store DataTable data in .uasset files, with corresponding JSON source files that serve as the editable representation. This skill provides a complete workflow for discovering, modifying, and re-importing these data tables.

This skill works with any UE project — it automatically detects the project structure and locates DataTable JSON files. No hardcoded paths required.

Supported DataTable Format

The JSON file should be an array of objects, each with a Name field as the row key:

CODEBLOCK0

Important Notes

• - JSON files may be encoded in UTF-16 LE (with BOM), UTF-8 BOM, or UTF-8. All scripts handle encoding automatically.
• The .uasset files are binary and cannot be edited directly — always modify through JSON then import.

Workflow

Step 0: Discover UE Project and DataTable Files

ALWAYS run this step first when the user has not provided a specific JSON path. Use scripts/dt_discover.py to auto-detect UE projects and DataTable JSON files:

CODEBLOCK1

When the user provides a table name (e.g. "修改 AI_Skills 表"), use --table to locate the matching JSON file:

CODEBLOCK2

Once the JSON file is identified, store its absolute path for use in subsequent steps.

Step 1: Search for Target Rows

Use scripts/dt_search.py to locate the row(s) to modify. The --json parameter takes the path discovered in Step 0.

CODEBLOCK3

Present search results to the user before proceeding with modifications.

Step 2: Modify Data

Use scripts/dt_modify.py to modify fields. The script automatically:

• - Wraps plain text in NSLOCTEXT() format for localization fields
• Validates all data after modification
• Creates a timestamped backup before saving

CODEBLOCK4

NSLOCTEXT Format Rules

For localization fields (LOC_Name, LOC_Desc, LOC_AlertText, LOC_InterruptMessage, LOC_NoticeText):

• - When user provides plain text, the script auto-wraps it as: INLINECODE14
• When user provides a full NSLOCTEXT(...) or INVTEXT(...) string, it is used as-is
• Use --no-wrap flag to disable auto-wrapping

Field Modification via Direct File Edit

For complex modifications (nested objects, arrays, or bulk changes), directly edit the JSON file using replace_in_file or read_file + write_to_file tools. Always validate after editing:

CODEBLOCK5

Step 3: Import into UE Engine

After modifying and validating the JSON, generate the UE import command. The user must execute this command in the UE Editor Output Log:

CODEBLOCK6

Parameters:

• - --part 0 — Import Part0 (ID 200000–229999)
• INLINECODE22 — Import Part1 (ID 230000–239999)
• INLINECODE23 — Import Part2 (ID 240000–249999)
• INLINECODE24 — Import all Parts
• INLINECODE25 — Override the UE asset base path (default: /Game/SMG/Configs/DataTables/AISkills)

Determine the correct --part number from the row ID being modified. Always provide the full command with absolute paths for the user to copy-paste.

Step 4: Verify

After the user reports the UE import result, check the log output for:

• - Imported DataTable '...' - 0 Problems = Success
• Any Error lines = Investigation needed

Refer to references/field_schema.md for the complete field documentation when needed.

Quick Start Example

User says: "修改 AI_Skills 表中技能 230005 的描述"

1. 1. Discover: INLINECODE31

→ Found: INLINECODE32

1. 2. Search: INLINECODE33

→ Shows current skill data

1. 3. Modify: INLINECODE34

→ Modifies and validates

1. 4. Import: Provide UE command for the user to run in editor

Error Handling

Error	Cause	Solution
No UE project found	Project not in search paths	Use --root to specify project directory
No DataTable JSON found

JSON file not in Content directory | Check project structure, provide path manually | | UnicodeDecodeError | Wrong encoding detection | Scripts auto-detect; if issues persist, check file BOM bytes | | fill_data_table_from_json_string fails | JSON fields don't match RowStruct | Validate JSON, check for missing/extra fields | | DataTable not found | Wrong asset path | Use --asset-base to specify correct UE asset path | | P4 checkout failure | File locked by another user | Coordinate with team or force checkout |