Repository navigation
Research Brief Dlc Primary
LopeKinz edited this page Sep 26, 2026
·
1 revision
Goal: Determine clearly whether a dedicated DLC-/Patch container can be mounted as the primary source for a map/asset group, instead of merely existing as a refchunk alongside a Base Chunk.
Context:
- Custom
dlc_4is recognized by the game (found dlc id 4,SearchDLC: found 4 dlcs). - An additional Base
refchunk26 was successfully mounted but lost against Basechunk_1due to identical(type,name). - This refutes only this Refchunk path, not necessarily a primary DLC-/Patch path.
- Do not start; do not modify Steam files.
Investigate: Existing packagemapspec.json, packagechunklist.json, DLC layouts, patch_N structures, and local tools/documentation. Search for specific fields (basechunkid, layer, patchlevel, Mapspec entries, Chunk IDs) and derive possible, testable primary paths.
Acceptance:
- Exact examples from Retail files with paths/fields.
- Statement of what is thereby secure and what requires a controlled single test.
- No changes except an optional custom report
re_probes/agent_reports/dlc_primary.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