FOR MODDERS AND HACKERS

SAVED.GAM byte map

This describes the DOS SAVED.GAM block and companion SAVED.OOL object lists. Offsets are hexadecimal and sizes decimal. Multibyte quantities are little-endian. Allocation boundaries are substantially established; not every saved working field has a complete portable interpretation or a verified malformed-input contract. Redux native snapshots use a separate schema and must not use these offsets.

File boundary and roster addressing

SAVE-0001Original: EstablishedRedux: Matches

The standard saved block is 4,192 bytes (0x1060), covering offsets 0x0000 through 0x105F. The initial two bytes are an allocated boundary field, not a verified magic signature. The excluded ending boundary begins at 0x1060. This establishes the written block length, not every historical loader's response to truncation or trailing bytes.

Sixteen character records begin at 0x0002, each 32 bytes:

character_offset(index) = 0x0002 + index * 32       # index 0..15

Redux's decoder requires the standard block length. Normal numeric values are interpreted by field; little-endian storage does not make every field unsigned.

Character record and party membership

SAVE-0002Original: EstablishedRedux: Matches
Relative offsetBytesMeaning
009Name storage
091Sex
0A1Class
0B1Status
0C, 0D, 0E1 eachStrength, Dexterity, Intelligence
0F1Magic points
10, 12, 142 eachCurrent HP, maximum HP, experience
161Level
171Inn time
181Stored armor value
19, 1A1 eachHelmet, body armor
1B, 1C1 eachFirst and second hand
1D, 1E1 eachRing and neck accessory
1F1Party/location marker

The three two-byte character quantities are signed 16-bit fields in the reviewed layout; normal HP and experience are nonnegative. Negative/corrupt interpretation is not inferred here. Empty equipment is 0xFF; item zero remains valid.

Active members occupy a packed prefix. Recruitment marks a companion active and swaps its record into that prefix. Inn separation records the location and moves the character out of the prefix. Common marker values are zero for active, a small-map location for inn residence, 0x7F for execution, and 0xFF for unrecruited. The stored armor byte is real data, not padding; its complete relationship to effective protection is a separate equipment question.

Inventory and party allocation

SAVE-0003Original: EstablishedRedux: Matches
OffsetBytesMeaning
0202, 02042 eachFood, gold
02061Keys
02071Gems
02081Torches
02091Grapples
020A1Carpets
020B1Skull Keys
020C1Skull Key search/reveal day
020D, 020E, 020F1 eachAmulet, Crown, Sceptre possession
02104Shard allocation; only three named counters established
0214, 0215, 02161 eachSpyglass, plans, Sextant
0217, 0218, 02191 eachWatch, Badge, wooden box
021A48Unequipped equipment quantities
024A48Prepared spell quantities
027A, 02828 eachScrolls, potions
028A, 0292, 029A, 02A28 eachMoonstone X, Y, map, level
02AA8Reagent quantities
02B23Reagent collection days
02B51Active party size
02B624Hidden-object discovery bits

Food and gold are signed 16-bit storage fields in this layout. Normal mutation limits are gameplay rules, not consequences of their storage widths. The fourth shard byte's meaning remains unresolved; preserve it rather than inventing a fourth named shard or assuming it can never be addressed.

This is the canonical inventory offset table; other topics should refer here. The day marker is committed by successful reveal, not later pickup; see Skull Key commitment.

Calendar, action, and position allocation

SAVE-0004Original: IncompleteRedux: Unverified
OffsetBytesMeaning or retained working-state role
02CE2Year
02D0, 02D22 eachTemporary X, Y
02D41Shared global active effect/item slot
02D5, 02D61 eachActive player, party display shape
02D7, 02D8, 02D91 eachMonth, day, hour
02DA, 02DB1 eachPrevious hour, minute
02DC, 02DD, 02DE1 eachCombat cadence, update counter, gong state
02DF, 02E0, 02E11 eachMoon states and gate stage
02E21Karma
02E3, 02E41 eachEating/food-update state
02E51Beggar reward counter
02E6, 02E71 eachLast-camping and Wanderer markers
02E81Global effect duration
02E9, 02EA1 eachCurrent-action spell and magic flags
02EB, 02EC1 eachMotion and wind state
02ED, 02EE, 02EF1 eachCurrent map, prior map, level
02F0, 02F11 eachParty X, Y
02F2, 02F3, 02F41 eachCrosshair enable/X/Y
02F5, 02F61 eachDisplay offsets
02F71Current weapon
02F8, 02F9, 02FA1 eachTurn, turn-light, exit direction
02FB, 02FC, 02FD1 eachScenario, wound type, victory
02FE, 02FF1 eachUpdate flag, sight
0300, 03011 eachMagic-light and torch-light counters

The offsets are established. Their complete reload semantics are not: a contiguous memory save can contain temporary process state as well as durable gameplay. Do not infer native snapshot fields from these names or silently discard unknown bytes when preservation is required.

World, dungeon, and NPC allocation

SAVE-0005Original: IncompleteRedux: Unverified
OffsetBytesMeaning or retained region
030232Enemy state
0322, 03253, 1Shadowlord state and last-call marker
0326, 03282 eachActive and completed shrine quest bits
032A, 03328 eachDungeon entrances, shrine closure state
033A14Dungeon room state
0348, 0368, 038832 eachDrawbridge X, Y, saved terrain
03A81Drawbridge count/state
03A9, 03AA, 03AB, 03AC1 eachDoor type, X, Y, closing counter
03AD, 03AE, 03AF1 eachShip X, Y, sailing state
03B0, 03B1, 03B2, 03B31 eachPrompt, intoxication, Shadowlord, opening-encounter flag
03B4512Dungeon cells: 8 x 8 x 8 bytes
05B4, 0634128 eachNPC absence and met-party data: 32 four-byte entries each
06B4256Active object list: 32 eight-byte entries
07B4, 07B62 eachRetained coordinate working values
07B851232 schedules, 16 bytes each
09B851232 NPC statuses, 16 bytes each
0BB8102432 paths, 32 bytes each
0FB86432 signed 16-bit path indexes
0FF832NPC shape bytes
1018, 10191 eachPending NPC command and actor
101A2Current level working value
101C6432 signed 16-bit pause values
105C, 105D, 105E, 105F1 eachLast direction, facing, dungeon type, skiff count

Each schedule has three action bytes, three X, three Y, three level, and four time bytes. Each NPC status has eight 16-bit values, including an explicit object-list association. Path indexes are signed integer indexes, not saved machine pointers; the pause region is 64 bytes, not 64 integer elements. The complete interpretation of every bit and transient status remains incomplete.

Object records and the companion object-list file

SAVE-0006Original: EstablishedRedux: Matches

An object record's eight bytes are base identity, displayed shape, X, Y, level, contextual number, animation state, and miscellaneous state. Identity and display frame are distinct. The contextual number can represent contents, quantity, durability, or another category-specific value; it is not universally HP. Outside combat, slot zero represents the party, including a boarded vehicle. Ordinary NPC association is stored separately in NPC status data.

SAVED.OOL contains two 256-byte lists: Britannia, then Underworld. When one large world is active, its current list in SAVED.GAM supersedes the potentially stale matching companion half. The other half remains the inactive world's list. Town and dungeon saves retain both halves. Redux requires the exact 512-byte companion for player-facing legacy import and explicitly resolves this ownership boundary.

Effect slots and initialization boundaries

SAVE-0007Original: EstablishedRedux: Unverified

The shared global effect/item slot can hold Protection, Negate Magic, Time Stop, Quickness, charm, or the Amulet/Crown/Badge item codes. Duration 255 is exempt from ordinary countdown. Magic-light and torch-light counters are separate. Action spell/magic flags are not extra global active-effect slots. This is not a claim that every persistent magical condition uses one slot.

Character creation loads INIT.GAM, changes selected Avatar fields, and writes the standard block. Allocation alone does not establish a default value for every field or every shipped template. Redux's native state deliberately has its own semantic schema; only explicitly converted legacy fields become authoritative, with preservation/default warnings handled by the import boundary.