.DAT -- Asset Mappings & AI Nav Graphs

1. Scope and evidence

The extension .dat is used by different data files, so the suffix alone does not identify a format. This guide documents the graphs.dat research recorded in this repository. It does not claim that every file named .dat uses this structure.

The source research reports the byte signature CC DD EE FF and ten tagged node fields. It describes locating a field value at signature offset + 8, with values read according to the listed type. This is a research procedure, not a complete file grammar or a claim about a pathfinding algorithm.

2. Tagged-field diagram

IGI graph tagged field representationResearch describes a two-byte signature followed eight bytes later by a typed value. The documentation does not establish a complete flat-file record sequence.RESEARCHED GRAPH FIELD: SIGNATURE → TAGGED VALUESignature (2 bytes)e.g. 04E68-byte gapresearch offset ruleTyped valuewidth depends on field type

For example, the documented Max Nodes tag is 04E6. The notes give a four-byte integer value in the example byte sequence, while other fields use other widths. The available research does not specify a complete header/table layout or a universal node-record stride.

3. Fields recorded by the research

FieldTagReported value typeRuntime reader named in notes
Max Nodes04E6IntegerSUB_004FAEE0()
Node ID04CEIntegerSUB_004FAF50()
Node Position0495Real64 × 3SUB_004FAF80()
Node Gamma049CSingleSUB_004FAFA0()
Node Radius0423SingleSUB_004FAFC0()
Node Material0429IntegerSUB_004FAFE0()
Node Criteria04E5String × 18SUB_004FB030()
Node Edge / Link 1044AIntegerSUB_004FB080()
Node Edge / Link 204F6IntegerSUB_004FB0B0()
Node Edge / Link Type0423IntegerSUB_004FB0D0()

Tag collision: 0423 is listed for both Node Radius and Node Edge/Link Type. Do not identify a field by this tag without context. The source notes report Node Criteria values as an 18-character string and identify criteria constants DOOR=1, VIEW=2, and STAIR=4.

4. Limits and source

The research identifies node position as three 64-bit real values and names runtime reader routines by address. It does not establish Floyd–Warshall, an APSP matrix, path cost units, file paths for all builds, or the full serialization order. Those claims have been omitted pending primary evidence.

Source: Research/GRAPH. Cross-game equivalence with IGI 2 is not assumed.