zone indexer

Generate offset tables required for Fallout 4 to help quickly locate areas.

Original address:

Prefix:

Holy Framework：

Cell Indexer

Generates the offset tables required for Fallout 4 to quickly position external units, even if the plugin does not contain pre-generated data.

In vanilla, some world spaces could be loaded without these index tables. When this happens, the game cannot always use the fastest local external unit to find the path. The Cell Indexer detects which loaded world spaces are actually missing required data and builds them automatically at runtime.

It does not rely on plugin names or hard-coded compatibility lists. Decisions are made based on the true state of the loaded world space.

Function

• Automatic external CELL indexing.
• Generate missing OFFSET_DATA table.
• Scan loaded plugins for external CELL records.
• Renewable index caching for faster subsequent loads.
• Validate cached data before reusing.
• Runtime patch to support native external unit lookup compatibility.
• Secure ownership and recovery of generated forms and patches.
• Fully automatic operation after match data is prepared.

User Advantages

• Automatic setup: Runs in the background without configuration.
• Faster subsequent loads: Reuse validated caches instead of rebuilding all caches each time.
• Better external unit indexing: Generate missing external unit index data when necessary.
• Compatibility improvements: Help the game more stably handle external unit data from loaded plug-ins.
• Low overhead: activated only when indexing service is requested.

For modders

This mod can be used to check if your mod contains invalid data. By looking at HolyFramework.log, you can determine whether your module has caused a conflict and what type of conflict it is.

Malformed data: The parser detected a truly malformed record.

Read failed: There was a problem reading/decompressing the data.

Inconsistent metadata: The reconstructed WRLD metadata does not match what was loaded natively in Fallout.

Incomplete metadata: Missing required data such as WRLD offsets, NAM0/NAM9 or boundaries.

Invalid offset: The offset is not possible or cannot be used.

Invalid bounds: Invalid table coordinates or dimensions.

Inconsistent data: Duplicate CELL coordinates.

Native mismatch: Our CELL rebuild did not match the existing native table.

Unsupported case: A structure that may be valid, but has not yet been processed by the Cell Indexer.

Running status: A status that changes during the planning process, or there is a concurrency situation.

Operation technology

• Query during game: native OFST.
• Generate: Only actual existing external CELLs are parsed.
• Indexed plugins: skipped before the scanner if all targets already have native OFST.
• Plug-in reading: Each plug-in only performs a structure scan once when actually needed.
• Multiple world spaces: All relevant world spaces in the plug-in are obtained at once.
• Cache: Each plugin contains a .cip5 bundle containing all world spaces.
• World space identity: FormID + actual association with TESFile.
• Plugin/Cache Identity: Volume + File ID + Size + Last Written + Change Time → Backup Fingerprint.
• Cache integrity: header CRC + payload CRC + structural invariants.
• Save: temporary file + atomic replacement.
• Cache corruption: Selective rejection, single-plugin rescan, and automatic rebuild.
• Threads: Engineless workers: filesystem, parser, zlib and cache.
• FormID parsing: after connection, in the main thread.
• Failed shutdown: Unresolved required targets == 0 mandatory before patching/installing.
• Incomplete metadata: not inventing boundaries or anchors: safe abort.
• Patches: Exactly 4 verified patch points.

compatibility

Not compatible with cell offset generator/faster cell lookup

Compatible with smooth unit loading

What is the difference between "incompatible" and this?

All three satisfy the same need. The difference lies in how they operate. I can definitely say th …