LTX CLI

LTX commands inspect, format, and verify .ltx and .ini config files. Use them for standalone config projects or when you need the lower-level tool behind the engine repository’s format ltx and verify ltx commands.

Formatting

ltx format formats selected loose config files. --check writes nothing and exits 3 when any selected file needs formatting, including when the input is a single file. From a project containing gamedata/configs:

xrf-cli ltx format --path ./gamedata/configs
xrf-cli ltx format --path ./gamedata/configs --check

Example output — check an unformatted LTX file:

Checking 1 ltx file(s) from 1 provided path(s)
Checking 1 file(s)
Not formatted: ./ltx-unformatted/spacing.ltx

Stderr:

Format issues with 1/1 files in 2 ms
Check failed: 1 finding(s)

Exit code: 3.

When the input resolves through an installation, archived configs are listed as declined because they cannot be rewritten in place. Review that list before treating a formatting run as coverage of the whole config set.

Verifying

ltx verify checks an LTX project folder, including schemes and case-sensitive include paths. Supply a directory; include, inheritance, section-field, and scheme errors fail verification.

xrf-cli ltx verify --path ./gamedata/configs

Only sections that declare $scheme are checked against a scheme. Other sections, including array-style sections, are valid without one. A scheme can use $strict = true when its own section shape is fully known.

Scheme definitions are documented in Script config schemes.

Inspecting configs

Use ltx list to list config files and their includers. Use ltx inspect to see a resolved section’s values and where each value was written:

xrf-cli ltx list --path ./gamedata/configs
xrf-cli ltx inspect wpn_ak74 --path ./gamedata/configs

Example output — inspect a DLTX override:

Inspect path: ./gamedata-dltx/configs
[wpn_ak74] resolved from system.ltx (dltx)
  declared in items\w_ak74.ltx
  inherits wpn_base
  $scheme    = $wpn_patched          set by w_ak74.ltx (depth 1)
  ammo_class = ammo_a,ammo_b,ammo_c  set by mod_system_aaa.ltx ('>', depth -200)
  cost       = 9000                  set by mod_system_xxx.ltx (depth -400)
  patched_by = mod_system_xxx.ltx    set by mod_system_xxx.ltx (depth -400)
4 field(s), 0 diagnostic(s)

Exit code: 0. The later patch supplies cost = 9000; the output names the file that supplied each value.

Use the resolved values and their source locations to distinguish a wrong declaration from a later override. If several entry points declare the section, select one with --entry system.ltx. Both commands accept --dltx for patched installations.

The DLTX patch dialect

Anomaly and its Monolith-based descendants let an addon patch a config without editing it, by dropping a mod_<base>_*.ltx beside it. --dltx reads configs under those rules; without it, a patch file is refused and the error names the flag.

xrf-cli ltx verify --path "C:/games/anomaly" --dltx
xrf-cli gamedata verify "C:/games/anomaly" --dltx

DLTX is not vanilla LTX with patches applied on top. It changes how base data resolves even when no patch file exists:

Patch operations, all Monolith-specific:

When several patch files touch the same field, the alphabetically last one wins, and a patch file always outranks the base tree.

Command reference

xrf-cli ltx format

Command to format ltx and ini files

xrf-cli ltx format [OPTIONS] --path <path>...

xrf-cli ltx inspect

Explain one resolved section: its fields, and where each value is written

xrf-cli ltx inspect [OPTIONS] --path <path> <section>

xrf-cli ltx list

List the LTX configs a project holds, and the role each one plays

xrf-cli ltx list [OPTIONS] --path <path>

xrf-cli ltx verify

Command for verification of ltx and ini files

xrf-cli ltx verify [OPTIONS] --path <path>