Repository navigation
Research Brief Map Selection
Goal: Investigate how TNC decides between Base and DLC Mapspecs when they share the same map name, and determine whether Savegame/Map metadata determines selection before the container mount.
Context: Retail DLCs primarily use chunkid 20/22/24; the custom dlc_4 spec for c02p0 is found. The Canary container is structurally valid, but the final real priority test failed due to the +0x08 Hash Gate or the unexecuted start command.
Scope: Read statically only: all Retail and Probe packagemapspec.json, Savegame game.details/checkpoint_mapstart.dat, Logs, Parser code, and existing Reports. No game starts, no installation changes.
Acceptance Criteria: Clear decision conditions for a single run, including an indication of whether refchunks/layer/basechunkid or Savegame data influences priority. Report exclusively to re_probes/agent_reports/map_selection.md.
English Wiki generated from the measured research notes in docs/. Evidence grades and uncertainty are preserved intentionally.
- WolfSDK Loader · DE
- WolfSDK Studio · DE
- FAQ · DE
- Mod format · DE
- Modding Guide
- Modding Surface
- CVar Catalog
- CVar Validation (old scrape)
- Texture Database
- Developer Mode
- Dev Menu
- Custom-Map Status