World LOD, content flags and priority

World LOD links placed entities across map files. An entity’s parentIndex indexes the parent map’s entity array; -1 means no LOD parent. numChildren, lodDist and childLodDist describe the linked hierarchy’s detail and distance relationships. Sourced · CodeWalker

The LOD and priority enum names and values in the tables are checked against the embedded enum descriptions in every YMAP and YTYP copy of the install, with no mismatch or refused file. This establishes their stored encoding, not the runtime distance or density decision. Proven · all map and archetype enum descriptions

lodLevel	Name	Confidence
0	HD	Proven
1	LOD	Proven
2	SLOD1	Proven
3	SLOD2	Proven
4	SLOD3	Proven
5	ORPHANHD	Proven
6	SLOD4	Proven

The distant city has authored SLOD models, separate from the high/medium/low/very-low lists inside individual drawables. These are two distinct levels of detail organization. Observed

A mesh name containing slod is not a sufficient definition of its placement role: SLOD-looking geometry also occurs in ordinary HD placements. On Del Perro pier, a section of m_sm_slod3sjm is placed as HD geometry 0.74 m above the deck. Observed Its name alone does not establish which runtime pass uses it. Inferred

Content flags

CodeWalker’s calculated meanings are useful descriptions, but the stored bits are not always derivable from the entities in a file. Observed

contentFlags bit	CodeWalker interpretation	Confidence
0	HD or ORPHANHD entities	Sourced · CodeWalker
1	LOD entities	Sourced · CodeWalker
2	SLOD2 or coarser	Sourced · CodeWalker
3	Interior instances	Sourced · CodeWalker
4	SLOD1 or coarser	Sourced · CodeWalker
5	Occluders	Sourced · CodeWalker
6	Physics dictionaries	Sourced · CodeWalker
7	LOD lights	Sourced · CodeWalker
8	Distant LOD lights	Sourced · CodeWalker
10	Grass instance batches	Sourced · CodeWalker
9, 11–31	Meaning not established	Unknown

Other readers name the bits differently: fivefury calls bit 4 BLOCKINFO and bit 2 container LOD, and fivefury and rage-formats call bit 9 critical. Neither states where its names come from. Sourced · fivefury, rage-formats

Real map listings include maps with SLOD entities and bit 4 unset, and maps with bit 4 set and no such entities. prologue05b_lod.ymap is an example that defeats treating bit 4 as a calculated function of entity LOD levels. Observed

Priority

priorityLevel	Name	Confidence
0	PRI_REQUIRED	Proven
1	PRI_OPTIONAL_HIGH	Proven
2	PRI_OPTIONAL_MEDIUM	Proven
3	PRI_OPTIONAL_LOW	Proven

At sampled settings with CityDensity=1.0 and SMC_AUTO, optional-low objects such as parking meters, bollards and small palms are absent while optional-medium objects such as news boxes and dumpsters are present. This observation does not establish the controlling setting or a universal priority cutoff. Observed

What selects optional-low entities?

The stored priorities and a runtime absence/presence comparison are known; the CPU decision and full settings matrix are not established. Unknown

What do stored content flags imply beyond their calculated descriptions?

Bit 4 contradicts a rule based solely on contained entity levels. Its full streaming role remains unresolved. Unknown