Objects: shrines, chests, barrels and the rest
Every room the game activates for the first time gets its objects: the ones placed by hand in the room’s map pieces, and a random set chosen from the level’s object groups. This page explains how those objects are chosen and placed, the dice they roll when they are created (is this chest trapped? locked? which shrine is this?), what happens when a player clicks a chest, urn or barrel, and where the chest hands over to the drop tables. It also names the timer events and the quest objects. It restates the reviewed objects spec, plus the short part of the treasure class spec that picks a chest’s drop table. What a shrine, a well or a trap actually does to the player is game simulation and is out of scope: the spec only names it.
The big picture
Section titled “The big picture”Objects are made on the server, in a fixed window of the room’s first activation, just before the room’s monster population pass. The window has three steps:
- the hand-placed objects of the room’s map pieces;
- a restore of objects saved when the room was last deactivated (nothing on a first visit);
- the random object population, which walks the eight object-group slots of the level and places members of the groups that pass their roll.
Every object made in any of these ways then runs the same creation rolls. Later, a player may operate it.
Four seeds feed these decisions, and which one a roll uses matters, because each is a separate stream of draws:
| Seed | What it decides |
|---|---|
| the room’s own seed | the eight slot rolls, the member picks, the shrine and well handlers, and the trap handler’s first roll |
| the object-region seed, one per game | every other placement, the room-theme roll, the InitFn and PreOperate creation rolls, the operate rolls, the timer events |
| the game seed | one step for each object created |
| the object’s own unit seed | its animation start and, later, its drop |
For the object-region seed there is one stream for the whole game, not one per room or per level. It starts from the game seed’s second draw when the game is created, and it advances with every room’s objects in the order rooms are activated, every operate and every timer event. So the order in which players walk into rooms and click things changes every object rolled afterwards, including what the next chest holds and whether it is locked.
Which rooms get random objects: the gate
Section titled “Which rooms get random objects: the gate”Before any random object is placed, a gate decides whether this room takes part at all. A room is skipped when it holds a waypoint, when it has no population level, when a preset test on the room says no, or when it is in a town, tested in that order. The recorded games confirm the order: in all 1265 recorded windows the tests ran one after the other and the window closed at the first that failed (46 waypoint rooms, 315 rooms with no population level, 35 by the preset test, 110 in towns; 759 passed). The tests’ inputs come from the level generator; in the test runs they were taken from the recording rather than modelled. The code behind them has since been read, and the end-to-end run checked the recorded values against that reading at every gate, but the values are still taken from the recording there. Town rooms drew nothing in all 222 recorded town activations.
Each gated room increments a “rooms visited” counter of its population level. That counter counts gated rooms, not rooms that actually got objects, and among other things it drives the theme roll below and two later rules: the late-level health shrine (a shrine of code 2) and the forced-slot rule below.
Then comes the room-theme roll, for the 39 levels whose Themes column is set. It costs one or two draws on the
object-region seed: a roll against 12 (raised by 5 past half the level’s rooms and by 5 more past three quarters) and,
if that passes, a pick of a theme number. On the game’s stock data no theme ever runs: every listed theme number
falls outside the range the code accepts, except one that has no handler. That one, theme 3, was drawn four times in
a later recorded game, and nothing ran: its entry in the theme table is switched off. The draws are still made. The
theme handlers themselves (an empty room, a barrel grid, an item grid, bookshelf or weapon-rack rows) are only named
in the spec and were never reached.
The eight slots and the member pick
Section titled “The eight slots and the member pick”A level names up to eight object groups in its ObjGrp0..7 columns, each with a chance in
ObjPrb0..7. A group lists up to eight object classes with a PROB and a DENSITY each.
The details that matter for an exact copy:
- Every slot costs one room-seed draw, even an empty slot (group 0). A slot passes when the roll is at most
ObjPrb, so the chance is(ObjPrb + 1)/100. - A passing slot costs a second draw for the member pick.
PROBvalues are percentages against 100, added up as the walk goes, not weights over the members’ total. When they add up to no more than the roll, nothing is placed: that happened to 259 of 2307 passing slots in the test runs. - The forced-slot rule is a game bug, and the spec keeps it. Once more than 96/128 (75 %) of a level’s rooms have
been gated and no health shrine stands, a slot is made to fail when the Objects record whose index equals the
group number has a non-zero
SubClass. It reads that record, not a member’s, so the slots it suppresses are those with group numbers 1–6, 50–53, 59, 60, 77, 109, 116, 119, 120, 123, 124 or 129. The run tracked this rule at every slot and it matched. - Groups 0, 30 and 72 (no members) and group 69 (whose first member slot is empty) cost their draws and place
nothing; a member with
PROB0 is never picked; and theGoretest never excludes anything on stock data. The recorded games confirm it: group 0 was drawn by 2364 slots, groups 30 and 69 by 124 and 156, and none of them led to a placement; group 72 was never drawn, but like group 30 it has no member. The gore limit is a fixed value (2) that no code changes: its address is read at one place in the whole program.
Placement handlers
Section titled “Placement handlers”The picked member’s PopulateFn column chooses one of nine placement handlers. Each gets the member’s DENSITY, and most turn
it into a count with ((room width × room height >> 7) × DENSITY) >> 8. Each also makes one roll against 100
that always passes but still costs a draw.
| Handler | Places | Seed used |
|---|---|---|
| 1 | clusters of urns, caskets, baskets, sarcophagi | object-region |
| 2 | shrines | room |
| 3 | scattered single objects | object-region |
| 4 | barrel clusters | object-region |
| 5 | crate clusters | object-region |
| 6 | corpses, then maybe flies | object-region |
| 7 | rogues on sticks | object-region |
| 8 | wells | room |
| 9 | traps | room, then object-region |
What a player may notice:
- Barrels come in clusters of at most 8 in total. The first barrel of a cluster is an exploding barrel with chance 1/3, each follower with chance 1/4.
- Flies (object 103) join each rogue on a stick, and the last corpse placed by the corpse handler, with chance 29/100.
- Shrines are placed with up to 3 tries per call, and a new shrine must be at least 50 subtiles away from every
earlier shrine of the level on each axis (not just by distance). Wells use 100. A shrine with
Orientation1 always lands one subtile in from the room’s first row (y), withxin the middle half of the room. Orientation 2 is the mirror case on the other axis, read from the code only, and the stock data never uses it: no shrine that the random population places has orientation 2. - The late health shrine. Once more than 75 % of a level’s rooms have been gated and no health shrine stands, the
shrine handler gets 30 tries instead of 3, and a shrine it places that is not a health shrine is converted into one
(its class becomes the row’s
Parm1). A recorded game in the City of the Damned met both: two calls with the rule due, 30 tries each, and the second placed a shrine and converted it. The conversion makes a shrine-type pick whose draws are spent and whose result is thrown away; that game matched it draw for draw. - Caps. A level stops getting shrines once it has more than one shrine per eight rooms; a recorded game met this twice (a 15-room Catacombs level with two shrines). The other half of that cap (10 shrines) and the well cap (4 wells, or more than one per eight rooms) are read from the code and were never reached in a run.
The urn-and-casket cluster handler (1) tests every spot with the size of the group’s member class, even when the list draw picked a different, larger object: in a recorded game, 32 follower spots after a casket or sarcophagus of another size were each tested with the member’s size. The crate handler (5) is read from the code only: no stock level uses it.
Finding a spot
Section titled “Finding a spot”Placement draws a position inside the room and tests it against the room’s collision grid, keeping a one-subtile margin from the room edge and a box of six extra subtiles around the object. Each placer call makes at most five attempts, two draws each, and there is no fallback: if none is free, the object is simply not made. In the test run accepted spots fell at attempts 1 to 5 (153, 87, 67, 51 and 29 times), and 911 placer calls found no spot. An object already placed marks the grid when its mode has collision, so it blocks later objects; all 5859 position tests of the run were predicted.

One invented room of 48 by 40 subtiles on an invented level with three used slots, every number a toy input and the toy wall and pillar standing in for the collision grid. The eight slots each cost one draw on the room seed, group 0 included, and a slot passes when its roll is at most its chance. A passing slot costs a second draw for the member pick: the members’ PROB values are added up as the walk goes, and the first member whose running sum is above the roll is the pick; when the sum never rises above the roll nothing is placed (objects § D). The scatter handler turns the member’s DENSITY into a count, ((area >> 7) x DENSITY) >> 8, after a roll against 100 that always passes, and makes that many placer calls on the object-region seed (§ E). Each call makes at most five attempts of two draws; an attempt is kept only inside the one-subtile margin and with no marked cell in the box of the object’s size plus 6, and there is no fallback (§ F). A spot accepted marks the cells for the later calls (every toy object has collision). Where a box reaches past the room’s edge the toy reads the cells as free; the game reads them in the neighbouring room, and refuses a cell in no room (collision § E). Not shown: the gate, the theme roll, the unit creation (the toy objects make no draw on the object-region seed when created; real ones may) and the other handlers. Seed: illustrative, an input of our own. Every value shown is computed by our model, not observed in the game.
Hand-placed objects and the pseudo-objects
Section titled “Hand-placed objects and the pseudo-objects”Objects placed in a map piece go straight to creation in their stored mode, with no room-seed draw (unless the object spawns monsters when it is created). All hand-placed objects come before the hand-placed monsters.
A few map-piece ids are not objects but instructions, the pseudo-objects:
| Id | Makes |
|---|---|
| 581 | a random chest: one object-region draw picks a chest class from a per-act list (special lists for levels 74 and 83) |
| 580 | a sparkle chest: a 581 chest, then the sparkle flag |
| 582 | a quest object chosen from a quest’s state |
| 574–579 | a shrine of a fixed range of types |
The sparkle chest’s flag is set after all of the chest’s creation rolls. In Maggot Lair levels 1–3 one more roll skips the sparkle with chance about one half (a roll above 50 out of 0..99); two sparkle chests of the run stood in Maggot Lair 1 and drew in exactly that order. The closing mode reset of the 580 chest draws nothing: seven recorded super chests reproduce with it doing nothing. The level-25 variant (a fixed class, 371, with trap type 3) was met in Tower Cellar Level 5; whether the code writes the trap type over the whole state byte or only adds it is read from the code, since the byte was 0 before. The fixed shrines 574–579 (no stock map piece places them) and the 582 quest object are read from the code only.
Creation rolls
Section titled “Creation rolls”Every object, hand-placed or random, is created the same way, with its rolls in this order:
- one step of the game seed, which gives the object its own unit seed;
- an animation-start draw on that unit seed, unless the object’s
Synccolumn is set; - the draws of its
InitFn(the table below), on the object-region seed; - for a row with PreOperate, a 1-in-14 roll that creates the object already opened.
After that, the object marks the collision grid if its mode has collision, with a size of its own: an object with
collision but a size of 0 marks nothing, and a door that blocks neither sight nor missiles marks the plain object bit
(both met in a recorded game). The class used is the Objects record’s position in the table: the only code that reads
the table computes the record from that position, and the Id column is never read (a whole-program scan with a
second tool agrees). The two differ only at records 410–412.
The InitFn column selects what extra rolls an object makes when created:
| What | Rolls |
|---|---|
| urns, jars, baskets | trapped if a roll 0..99 is below MonLvl1 ÷ 8 + 5; then a trap type 1..8 |
| chests | the same trap roll; for a lockable chest, locked if a roll is below MonLvl1 ÷ 2 + 8; then a new unit seed for the chest |
| shrines | which shrine (below) |
| gold-pile dummy | 1 to 9 gold piles around it |
| goo pile, fires | one roll each for a state |
Two things here matter to a player:
- Trap and lock chances use the normal-difficulty monster level in every difficulty.
MonLvl1is read in Nightmare and Hell too, and every trap and lock roll of 212 chests and 397 containers in a recorded game matched that. In Lower Kurast (MonLvl122) a chest locks with chance 19 %. - A chest gets a fresh seed at creation. Its drop later draws from that seed, never from the object-region stream.
Shrine types. A shrine row’s Parm0 picks one of the shrine class lists (the Shrines effectclass
column): Parm0 1 gives list 2 (in the spec’s shrine example it holds codes 2 and 4), Parm0 2 gives list 3, and
otherwise one roll gives list 1 with chance 1/10 and list 4 otherwise. A code is then drawn uniformly from that
list; the rarity column is not read. The draw is retried up to 8 times until the code’s LevelMin is at most the
level’s Id (the level number, not a monster level). If all 8 fail, the eighth code is kept anyway: a recorded game
hit this once, a shrine in Cold Plains that kept a shrine type whose LevelMin is 5. Codes 4, 5 and 16 are rewritten
to 2, 3 and 18, so Health Exchange, Mana Exchange and the Shrine of Enirhs are never placed by the random population.
For the 13 other InitFns that the recorded games reached, “no draw” is confirmed: every seed matched after each with
no draw. For the ones never reached it is read from the code. The sparkle chest’s own InitFn (57: the chest’s rolls,
then the sparkle flag) and the fissure’s (58: one roll) were met in a later recorded game; the Zoo (79) was not.
Quest objects, the objects of nine more InitFns that a full scan of the code found, and the City of the Damned
spawn monsters when created. Where the recorded games met such an object,
it drew nothing from the object-region seed. The City of the Damned’s spawns, with their room, game and
object-region draws, are now modelled; for the other monster-spawning objects the rolls are still taken from the
recording. Each pile of the gold-pile dummy is now a modelled item, with its two game-seed steps and its mark on the
grid and no object-region draw (71 of 71 piles); where a pile lands is read from the code, and that reading placed 69
of the 71 (objects § H, rows 28 and 46).
Leaving and coming back
Section titled “Leaving and coming back”When a room goes inactive, the game saves its eligible objects (oldest first, confirmed: 392 of 392 recorded pairs
came back in their creation order), and when the room is activated again, it re-creates them. The re-creation makes
every creation roll again, including a fresh trap and lock roll, and then overwrites the result with the saved
state: a chest locked the first time stays locked, whatever the new roll said. A random or sparkle chest comes back
as its plain class, without the pseudo-object’s extra draws. The run reproduced 548 re-creations, and every object of
its 190 restores was saved or left out as the saving test says. A later run checked the saving test on 3 023 objects;
the flag it starts from is the level’s SaveMonsters column. Neither run met an
object refused for its sparkle flag, or one whose level flag and placed-by-preset flag were both clear, so those two
refusals are read from the code only. The room and game seeds at a revisit are still taken from the recording in the
objects model: the monster and item restores that come before the objects are described by the
room lifecycle spec.
Operating chests, urns and barrels
Section titled “Operating chests, urns and barrels”When a player operates an object, its OperateFn decides what happens; the operate rolls are on the object-region
seed.
For a chest:
- A locked chest needs a key (consumed), or a player of character class 6; then it drops twice.
- A plain chest is empty when its roll is at most 24: 25 % of plain chests are empty. Locked and sparkle chests never are.
- A sparkle chest first rolls its forced quality: rare with chance 5/100, magic otherwise, on every drop. If none of its items is magic or better, it drops up to 10 more times until one is.
- After the drops the chest changes mode and its trap fires.
In a recorded game 40 chests were operated: 11 were empty, 6 locked ones dropped twice, and 3 sparkle chests (all forced to magic) repeated their drop until one item was magic or better, taking 4, 4 and 6 drops.
Other containers:
| Object | What the operate does |
|---|---|
| urns, jars, baskets | one drop with chance 21/100, then the trap |
| barrels | an effect on the player; a monster with chance 18.08 % (a roll of 8192 or more out of 10000); then one drop with chance 21/100 |
| caskets, sarcophagi | one drop; only if it made an item, a monster with chance 18.08 %; then the trap |
| bookshelves | the book or scroll pick: a roll 0..19 (above 12 a book, else a scroll) and one more for which kind, then the item |
| trapped souls | a roll 0..99: under 90 a drop; 90 or more, a mode change and two timer events instead |
| the evil urn | one drop; only if it made an item, a special monster from the region, then the trap |
A recorded game operated 58 caskets: 44 made an item and then rolled for the monster (3 got one), and 14 made none and rolled nothing more. It also operated one bookshelf (which gave a book), nine trapped souls (all under 90, each with an item) and one evil urn (an item, then the monster). So those three handlers are confirmed on the branch they took; the scroll side of the bookshelf, the trapped soul’s 90-or-more branch and the urn’s no-item case are read from the code. When an operate does spawn a monster, the operate itself is a player’s action and so an input; the monster’s creation is not run by the composed model, and the end-to-end check counts such creations rather than predicting them. Class 397, a special chest with its own tiered drop table, was never operated in a run (a later game created it three times but never reached it), so its table is read from the code only. Of the 68 operate handlers, exactly seven roll the object-region seed directly and seven more (the quest scripts) the quest seed, as two independent scans of the code agree; the others reach the object-region seed only through an object they create, a trap fired later, or a room they activate (for example a portal), read from the code. The three other handlers operated in the run (an exploding barrel, a door and waypoints, 25 operates) left the stream untouched. A portal-like operate that activates a room runs that room’s object window inside the operate; this too is read from the code (the 19 recorded operates of the Arcane Sanctuary’s pads activated no room).
What a chest drops: the hand-off
Section titled “What a chest drops: the hand-off”The chest drop itself makes no roll. It chooses one of the act’s chest treasure classes (TC), named
Act N Chest A, B or C for the difficulty, and hands it to the drop resolver with the object as the
source unit and the player as the killer. From there the drop is the treasure class
resolution of the items page, drawing the object’s own unit seed (for a chest, the fresh seed of its
creation).
- Which of A, B or C: the level’s monster level (the same value the monster pages call the area level), compared
with the monster levels of the act’s two reference levels, the span between them cut into thirds: a third of the
span (plus one) rounded toward zero, tier A below the first third, C from the second on. Both specs check it against the 59
chest drops of a recorded objects run (three difficulties, classic and expansion, acts I, II, III and V, all three
tiers, both boundaries met). The shape of the drop (no roll of its own, one hand-off) is confirmed too; the 11
object drops of one test run (all
Act 1 Chest A) and the Jail chest of the worked example below reproduced. - The tier also goes to the resolver as the drop’s item level for the quality roll, so a chest drop rolls its quality at item level 0 to 2: its odds of magic and better are no better than those of a monster drop of the same base in the same area; the item’s own level still comes from the chest. The same 59 chest drops pass their tier as that item level.
- The forced quality: 0 from urns, caskets and barrels, the sparkle chest’s rare or magic quality code otherwise. A non-zero forced quality replaces the normal quality roll for every entry that is not a unique or set entry. A sparkle chest uses the same act chest TC as any other chest; only the quality is forced.
- When the TC entry is gold or a potion, the sparkle chest’s forced quality makes no difference: the item skips the quality roll, and then item creation’s always-normal rule builds it as normal quality anyway (elixirs excepted, which keep the forced quality). This is read from the code.
Traps and timer events
Section titled “Traps and timer events”A trap does not go off during the operate. Operating a trapped object only queues a timer event 35 frames later, and the trap goes off then, among the other timer events. A recorded game confirms it for ten traps of types 1 to 7: each was queued as the operate’s last step and ran 35 frames later. Which effect a trap gets depends on its type and the level: below level 40, a lightning or nova trap fires firebolts instead, and so does a poison trap outside the Tower Cellar’s level 25; from level 75 on a monster trap does too. The recorded game met the nova case (a casket in level 35 fired firebolts); the other remapped cases are read from the code. The lightning, firebolt, poison and nova traps create a trap monster; the six that went off in the game (lightning, firebolt and poison) left the object-region seed alone. The fire trap creates two fires (the second one subtile to the side, when that is still in the room), each one game-seed step, and both were predicted. The monster traps (types 8 and 9), the only ones that roll the object-region seed, were not reached, so their roll is read from the code.
Some objects also have periodic timer events that roll the object-region seed. One callback draws a new event time at every call (3042 such draws in one run); the spec gives the act-town fires as an example of such a periodic effect. When an event runs is game simulation, an input to the model; what each callback does is only named. A reimplementation that advances the object-region seed only during population and operates drifts as soon as such an object has run.
Quest objects
Section titled “Quest objects”Quest objects (the Hellforge, the quest chests, the altar that gives the viper amulet, Wirt’s body, the Inifuss tree, the Malus, the Horadric orifice) are operated like any object: the quest script is their own operate function. Their later steps (the forge’s gem waves, Wirt’s gold piles) run as a timer event that a quest dispatcher hands to the right script by object class. Their item creations roll the quest seed, not the object-region seed. That timer event is entry 7 of the object timer events. The objects spec only places them; their drops are explained on the other item paths page, and the quest scripts behind them, the waypoints and the portals on quests and travel.
What the recorded games confirm:
- The Hellforge, for one player in Normal, Nightmare and Hell: its click reaches its operate function and its waves come through the timer event, its 25 item creations in a test run left the quest seed unchanged on each entry and exit and drew nothing from the object-region seed, and in Hell its gems and rune took item level 85.
- The timer route for Wirt’s body and the Kurast sewer lever: 19 timer events went through entry 7 and the dispatcher to the right script by class. For the other quest objects it is read from the code.
- Wirt’s body, on its first click: it gives the leg, with no quest-seed roll, then 18 timer events give one gold pile each; the count, 10 to 19, is one quest-seed roll at the first event.
- The Act II quest chests (the scroll, the staff and the cube chest): the quest item when the player passes the chest’s test, then the ordinary chest drop, then 5 to 9 gold piles on the quest seed. A player who already holds a cube gets no new one, and the drop and the gold still come.
- The Khalim chests go the other way round: the gold piles first, then the part (for a player who holds neither that part nor Khalim’s Will), then the ordinary drop. Recorded games met this on all three chests, the heart, the eye and the brain, each with the gold count its quest seed gives. That a player who already holds the part or Khalim’s Will gets none is read from the code. The altar was not run.
- The Inifuss tree and the Lam Esen tome each give their item on the first click when the quest allows it, with no roll. Both items are asked for at normal quality and come out at quality 7; that the 7 comes from the item’s base is read from the code, as is the tome’s refusal once its quest bit is set. The Malus was not run.
- The orifice: placing the staff sets the two quest bits the code names. That it opens only for a player holding the staff is read from the code.
A worked example
Section titled “A worked example”These are copied from the spec’s worked example, taken from recorded games and reproduced with no mismatch.
One room in Cold Plains.
Game seed 2302, Normal, expansion. The room is 40 × 40 subtiles. The gate is open, Themes is 0 so there is no
theme roll, and the level has had 9 of its 71 rooms gated, so the forced rule does not apply (9·128 ÷ 71 = 16).
The slots are group 4 (ObjPrb 3), groups 38, 33 and 34 (ObjPrb 22 each), then four empty slots.
| Draw | Seed | Value | Meaning |
|---|---|---|---|
| S1 | room | 17 | slot 0: 17 > 3, fails |
| S2 | room | 5 | slot 1: 5 ≤ 22, passes |
| S3 | room | 41 | member pick in group 38: sums 34, 67, so member 1, class 174 (loose rock, handler 3, DENSITY 30) |
| — | — | — | count: ((40·40 >> 7)·30) >> 8 = (12·30) >> 8 = 1 |
| O1 | object-region | 40 | the handler’s roll against 100: passes |
| O2, O3 | object-region | 27, 36 | attempt 1 at (5107, 5636): blocked |
| O4, O5 | object-region | 20, 11 | attempt 2 at (5100, 5611): free, accepted |
| G1 | game | — | the rock is created; no other roll (no InitFn, no PreOperate, Sync set) |
| S4, S5 | room | 31, 99 | slots 2 and 3 fail |
| S6–S9 | room | 69, 88, 55, 36 | slots 4–7, group 0: drawn, nothing placed |
The room took 9 room-seed draws, 5 object-region draws and 1 game-seed step, as recorded.
A chest in Jail Level 1.
A hand-placed lockable chest, class 241, in level 29 with MonLvl1 10, so the trap chance is 10 ÷ 8 + 5 = 6 and
the lock chance 10 ÷ 2 + 8 = 13.
| Draw | Seed | Value | Meaning |
|---|---|---|---|
| G1 | game | — | the chest’s unit seed |
| O1 | object-region | 5 | trap roll: 5 < 6, trapped |
| O2 | object-region | 6 | trap type 1 + 6 = 7 |
| O3 | object-region | 74 | lock roll: 74 ≥ 13, not locked |
| O4 | object-region | 47047 | the chest is re-seeded from 47047 + 1 |
Later in the same game, after the object-region stream had moved through other rooms, operates and timer events, the
player opens it. The roll is 74 (> 24), so it drops once with no forced quality: tier 2, Act 1 Chest C. The
resolver draws the chest’s own seed and, in this case, makes no item. The chest opens and trap type 7 fires.
What is not known yet
Section titled “What is not known yet”From the spec’s open questions and its inputs list:
- Never reached in a run, so stated as read from the code: the crate handler; the class-397 chest table; the Zoo; the 10-shrine cap and the well cap; the fixed shrines 574–579 and the 582 quest object; the room-theme handlers.
- Read from the code, but no run told it apart: the branches of the bookshelf, trapped-soul and evil-urn operates that no click took, the monster traps (types 8 and 9) and most of the trap’s level remap, whether the level-25 sparkle chest’s trap is written over the whole state byte, and whether bookshelves test any quest state. No stock data reaches orientation-2 shrines, a door that blocks missiles but not sight, or a guard in the shrine pick.
- Still taken from the recording, not modelled: when timer events run; the room and game seeds at a revisit; a room activated inside a portal-like operate (never met).
- Not tried on the collision model: a gold pile placed off its room, and units that move between a room’s activation and its object window.
- Open leads: whether any code reads the Objects column
TrapProb: none of the functions that fetch an Objects record reads it, but code that keeps a record from elsewhere could. A whole-image scan finds no reader ofSpawnMaxorActeither, though a reader through a computed address is not ruled out. Also open: two contradictions with a community guide (aDENSITYof 128 and a shrine row withParm00) that only modified data could reach. - Who changes a chest’s state byte before it is opened. Seven chests of the end-to-end run reached their operate with a lock bit or state their creation had not left (set, cleared, or the whole byte cleared), and no recorded line wrote it; the check takes the byte at the operate.
- Multiplayer games were not recorded, and quest-state objects stay inputs.
Where to read more
Section titled “Where to read more”- The full rules, with exact draw order: objects spec, and its notes for a reimplementer.
- What happens after the hand-off: treasure class spec § J and the items page.
- How rooms and map pieces come to exist: levels. The monster pass that follows the object window: monsters. Seeds and draws: randomness. Quest scripts, waypoints and portals: quests and travel.
- Terms: the glossary.