Field-pack Confirmed

At a glance

What it really is

One DATA_FIELD chunk wrapping one container-formats::pack - two formats this site already documents

Where

Raw-TOC offset +4 of a scene's CDNAME block (extraction index #define + 2). 23 blocks carry one; the rest reserve the slot with a pochi filler

The "magic"

0x01059B84 = (TIM_LIST << 24) | 0x059B84. The low 24 bits are that carrier's payload length, so the word differs per file - it occurs exactly once in the whole archive

Two forms

18 carriers lead with the chunk header; 5 carry the bare pack at offset 0. The bundle's Flag descriptor picks which

Parser

legaia_scene_formats::field_pack::scene_pack (corrected reader); detect / CANONICAL_SCHEMA kept for the classifier and the asset field-pack CLI

Confidence

Confirmed - loader disassembly plus a whole-archive byte sweep (how we know)

Used by

scene bundles, asset loader

Layout

Grey = the optional DATA_FIELD chunk header (offsets shown with it present; the five bare carriers start at count). Everything after it is a plain container-formats::pack: word offsets are × 4 from the count word, and member 0 starts exactly where the table ends.

The type byte agrees with the members' own magic in every carrier: all-TIM (0x00000010) under 0x01, all-TMD (0x80000002) under 0x02. Eight carriers are TIM packs and ten TMD packs; the five bare ones hold TIMs but for monster_data.

What each old claim really was

Where a carrier sits

Every scene's CDNAME block seats the same slots at the same offsets from its #define, in raw-TOC space:

The first three names come from the loader's own path literals; the +4 position is what the loader's by-index branch computes directly, FUN_8003EB98(scene_index + 4, …) with the scene index equal to the block's #define value.

How it reaches RAM

FUN_800255B8 loads one streamed file into the scene asset buffer and returns its sector count, choosing the path by a mode argument; FUN_8002541C then reads the buffer with the reader that mode selects.

Nothing else picks the mode: it comes out of the scene's own asset table. The dispatcher handles type bytes 0x0A / 0x0F / 0x14 by returning (case << 8) and nothing else; the descriptor walker ORs every return into one status word, and the field init shifts that right by 8 and hands it to FUN_8002541C. So a Flag descriptor in the bundle is a request to stream the block's +4 entry.

Two blocks break the pattern in the harmless direction - opurud and other7 carry a pack with no Flag descriptor to reach it. Flag(0x0F) appears in no retail bundle, consistent with the move table being a descriptor inside the bundle rather than a streamed file.

How we know

Deep dive

asset field-pack <PATH>                # legacy view: chunk header + pack table
asset field-pack <PATH> --all-slots    # every member offset/size
asset field-pack <PATH> --groups       # cluster members by size
asset field-pack-scan <DIR>            # find the chunk-headered carriers

use legaia_scene_formats::field_pack;

// Handles both forms: chunk_header is None for the bare carriers.
if let Some(p) = field_pack::scene_pack(&entry_bytes) {
    println!("{} members, type {:?}", p.members.len(), p.asset_type());
    for r in &p.members { /* a PSX TIM or a Legaia TMD */ }
}

Source of record: docs/formats/field-pack.md.

See also