FOR MODDERS AND HACKERS

Combat maps

BRIT.CBT supplies fixed outdoor, town, camping, Shadowlord, and ship encounter layouts. It shares a record envelope with DUNGEON.CBT, but not all metadata semantics. Values below describe the DOS format; exact physical size and artwork for every distributed file are not established by the record consumers alone.

Record boundaries and addressing

CBT-0001Original: EstablishedRedux: Matches

Each addressed record occupies 352 bytes (0x160): eleven rows with a 32-byte stride. The battlefield occupies only columns 0-10 of those rows, yielding an 11 x 11 tile plane. All indexes are zero-based:

record_start = record_index * 352
cell_offset = record_start + row * 32 + column

Selectors address through index 15, requiring a span of at least 5,632 bytes (0x1600). That requirement is not proof that every physical file has exactly 16 records and no trailing data. Redux bounds record reads against actual file length and decodes the same tile plane.

Britannia formation metadata

CBT-0002Original: EstablishedRedux: Matches
MeaningRow and columnsRelative byte offsetsCount
TerrainRows 0-10, columns 0-10row*32+column121
Party XRow 3, columns 11-16006B-00706
Party YRow 3, columns 17-220071-00766
Encounter XRow 6, columns 11-2600CB-00DA16
Encounter YRow 7, columns 11-2600EB-00FA16

Coordinates are bytes, not tiles. Six party positions are copied even where the destination arrays have more capacity. Sixteen encounter positions are formation capacity, not a guaranteed monster count; population is determined separately. Other Britannia metadata bytes remain uninterpreted here. Zero does not prove that an unused byte is a disabled dungeon trigger.

Original layout selection

CBT-0003Original: IncompleteRedux: Unverified
IndexSelection
0Camping
1Swamp
2Grass and ordinary outdoor fallback
3Brush or thick brush
4Desert or either waste half
5Forest or tropical vegetation
6Hills, mountains, peaks, or split-hill halves
7Bridge families
8Floor and ordinary small-map fallback
9No selector established in the reviewed normal selection path
10Shadowlord encounter
11Ship versus sea creature
12Land party versus pirate ship
13Ship versus shore creature
14Ship versus pirate ship
15Land party versus water creature

Creature base families disregard their two low frame bits. The initial water classification accepts terrain below swamp, or river-family terrain that is not the excluded bridge pair. Sea-creature families force water classification. Shadowlord selection takes precedence; ship/shore combinations precede ordinary terrain selection. Index 9 must not acquire an original basement/dungeon meaning merely because a remake gives it a convenient label. The full original caller set and every authored record remain outside this verified selection scope.

Tactical bounds and dungeon-only metadata

CBT-0004Original: EstablishedRedux: Matches

Combat coordinates are 0-10. An off-screen destination may be accepted by movement legality so a later escape path can process it; this does not enlarge the file's tile plane.

For a room loaded from DUNGEON.CBT, entry facing selects party rows 1-4; row 5 holds up to sixteen entity descriptors and rows 6-7 their coordinates. Eight terrain-replacement triggers use row-0 columns 11-18 and rows 8-10. A trigger can replace two in-bounds cells and disables itself after activation. These meanings do not apply to ordinary Britannia records solely because the buffer sizes match. Generated dungeon encounters synthesize their own terrain and metadata rather than selecting another Britannia record.

Redux separates dungeon entity/trigger handling from the Britannia plane and generates the corresponding dungeon encounter records. Exact original artwork, unused metadata, and all malformed records are not implied by that comparison.