Big Buck Hunter Pro

Recorded completion blockers

Missing locations · 73

• Unidentified switch 2
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 3
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 4
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 12
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 17
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 46
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 47
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 48
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 49
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 50
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 51
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 52
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 53
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 54
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 55
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 56
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 57
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 58
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 59
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 60
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 61
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 62
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 63
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Unidentified switch 64
  Device evidence and notes

  No retained source names or binds this address: the partial manual carries no switch matrix table, and the retained script defines no handler for it. The ROM may use it; failing to observe an address is never proof that it is unused.

• Left Post Save (UK Only) - not fitted; Buck home position in the retained table
  Device evidence and notes

  Read through sam.c's dedswitch_lower_r, which returns coreGlobals.swMatrix[9] as the low byte of the lower dedicated-switch word. Printed DED #7, a United Kingdom post-save cabinet switch this US-manufactured machine does not carry: no such switch or bracket appears in the retained manual's cabinet parts tables. The retained script writes Controller.Switch(71) = 1 whenever its animated Buck reaches the start of its travel, repurposing this always-readable dedicated address as the Buck's home-position feedback. The retained table drives the Buck from lamp events and animates the target itself, so these writes are the table author's substitute for the machine's own position feedback, not evidence that the physical sensor sits at this dedicated-switch position. The physical Buck feedback addresses the ROM actually reads are not settled by any retained source; the commented-out matrix writes on 37 and 45 are the table author's own record of where those optos belong. The address is live: the retained table writes it (see the label note), and the ROM's dedicated-switch handler reads the byte regardless of whether the optional hardware is fitted.

• Right Post Save (UK Only) - not fitted; Buck end-of-travel in the retained table
  Device evidence and notes

  Read through sam.c's dedswitch_lower_r, which returns coreGlobals.swMatrix[9] as the low byte of the lower dedicated-switch word. Printed DED #8, the second UK post-save address, not fitted for the same reason as D-7. The retained script writes Controller.Switch(72) while the Buck sits at the far end of its travel and reverses there. The retained table drives the Buck from lamp events and animates the target itself, so these writes are the table author's substitute for the machine's own position feedback, not evidence that the physical sensor sits at this dedicated-switch position. The physical Buck feedback addresses the ROM actually reads are not settled by any retained source; the commented-out matrix writes on 37 and 45 are the table author's own record of where those optos belong. The address is live: the retained table writes it (see the label note), and the ROM's dedicated-switch handler reads the byte regardless of whether the optional hardware is fitted.

• Unidentified extended-block switch (the v1.10 table's left-flipper write)
  Device evidence and notes

  Read through sam.c's strobed matrix word: the matrix read at 0x1100000 returns MAKE16BIT(swMatrix[2 + sw_stb*2], swMatrix[1 + sw_stb*2]), so strobe bit 4 returns swMatrix[9] (the coin block, 65-72) as the low byte and swMatrix[10] (this block, 73-80) as the high byte. The shared S.A.M. profile's declared input ranges do not cover this block; it is enumerated here because a second retained table demonstrably writes three of its addresses. This address sits in the 73-80 block between the dedicated coins (65-72) and the flipper column (81-88), which the shared S.A.M. profile's declared input ranges do not cover: sam.c reads it only through the strobed matrix word (sw_stb bit 4 returns swMatrix[9] as the low byte and swMatrix[10] as the high byte), so the block is reachable hardware that no retained manual names. The v1.10 modern-upgrade table maintains Controller.Switch(73) from the left-flipper key while core.vbs simultaneously drives the flipper column (81/83), so whether this machine's ROM reads its flipper buttons from the flipper column, from this block, or from both is an open question a switch-test or gameplay harness trace must settle. Recorded availability unknown; no placement is claimed.

• Unidentified extended-block switch
  Device evidence and notes

  Read through sam.c's strobed matrix word: the matrix read at 0x1100000 returns MAKE16BIT(swMatrix[2 + sw_stb*2], swMatrix[1 + sw_stb*2]), so strobe bit 4 returns swMatrix[9] (the coin block, 65-72) as the low byte and swMatrix[10] (this block, 73-80) as the high byte. The shared S.A.M. profile's declared input ranges do not cover this block; it is enumerated here because a second retained table demonstrably writes three of its addresses. See switch 73 for the block's structure. No retained table writes this address; the block is reachable hardware that no retained manual names.

• Unidentified extended-block switch (the v1.10 table's right-flipper write)
  Device evidence and notes

  Read through sam.c's strobed matrix word: the matrix read at 0x1100000 returns MAKE16BIT(swMatrix[2 + sw_stb*2], swMatrix[1 + sw_stb*2]), so strobe bit 4 returns swMatrix[9] (the coin block, 65-72) as the low byte and swMatrix[10] (this block, 73-80) as the high byte. The shared S.A.M. profile's declared input ranges do not cover this block; it is enumerated here because a second retained table demonstrably writes three of its addresses. See switch 73: the v1.10 table maintains Controller.Switch(75) from the right-flipper key. Availability unknown pending a runtime trace.

• Unidentified extended-block switch
  Device evidence and notes

  Read through sam.c's strobed matrix word: the matrix read at 0x1100000 returns MAKE16BIT(swMatrix[2 + sw_stb*2], swMatrix[1 + sw_stb*2]), so strobe bit 4 returns swMatrix[9] (the coin block, 65-72) as the low byte and swMatrix[10] (this block, 73-80) as the high byte. The shared S.A.M. profile's declared input ranges do not cover this block; it is enumerated here because a second retained table demonstrably writes three of its addresses. See switch 73 for the block's structure. No retained table writes this address; the block is reachable hardware that no retained manual names.

• Unidentified extended-block switch
  Device evidence and notes

  Read through sam.c's strobed matrix word: the matrix read at 0x1100000 returns MAKE16BIT(swMatrix[2 + sw_stb*2], swMatrix[1 + sw_stb*2]), so strobe bit 4 returns swMatrix[9] (the coin block, 65-72) as the low byte and swMatrix[10] (this block, 73-80) as the high byte. The shared S.A.M. profile's declared input ranges do not cover this block; it is enumerated here because a second retained table demonstrably writes three of its addresses. See switch 73 for the block's structure. No retained table writes this address; the block is reachable hardware that no retained manual names.

• Unidentified extended-block switch
  Device evidence and notes

  Read through sam.c's strobed matrix word: the matrix read at 0x1100000 returns MAKE16BIT(swMatrix[2 + sw_stb*2], swMatrix[1 + sw_stb*2]), so strobe bit 4 returns swMatrix[9] (the coin block, 65-72) as the low byte and swMatrix[10] (this block, 73-80) as the high byte. The shared S.A.M. profile's declared input ranges do not cover this block; it is enumerated here because a second retained table demonstrably writes three of its addresses. See switch 73 for the block's structure. No retained table writes this address; the block is reachable hardware that no retained manual names.

• Unidentified extended-block switch (the v1.10 table's front-key pulse)
  Device evidence and notes

  Read through sam.c's strobed matrix word: the matrix read at 0x1100000 returns MAKE16BIT(swMatrix[2 + sw_stb*2], swMatrix[1 + sw_stb*2]), so strobe bit 4 returns swMatrix[9] (the coin block, 65-72) as the low byte and swMatrix[10] (this block, 73-80) as the high byte. The shared S.A.M. profile's declared input ranges do not cover this block; it is enumerated here because a second retained table demonstrably writes three of its addresses. See switch 73: the v1.10 table pulses Controller.Switch 79 from its front key while also maintaining tournament start (15). Availability unknown pending a runtime trace.

• Unidentified extended-block switch
  Device evidence and notes

  Read through sam.c's strobed matrix word: the matrix read at 0x1100000 returns MAKE16BIT(swMatrix[2 + sw_stb*2], swMatrix[1 + sw_stb*2]), so strobe bit 4 returns swMatrix[9] (the coin block, 65-72) as the low byte and swMatrix[10] (this block, 73-80) as the high byte. The shared S.A.M. profile's declared input ranges do not cover this block; it is enumerated here because a second retained table demonstrably writes three of its addresses. See switch 73 for the block's structure. No retained table writes this address; the block is reachable hardware that no retained manual names.

• Unidentified output 6
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 8
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 9
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 10
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 11
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 13
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 17
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 18
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 24
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 28
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Unidentified output 30
  Device evidence and notes

  No retained source binds or names this address: the partial manual carries no coil table, and the retained script defines no callback. sam.c's bbh_ block additionally types addresses 19-22 and 25-32 as #89-bulb flasher strings under a comment acknowledging the typing was reconstructed from the community table rather than a manual, so even the emulator's own class metadata is ancestral to the table retained here and is recorded, not trusted. The device class below is the driver bank's generic coil record; the ROM may drive this address at runtime. Failing to observe an address is never proof that it is unused.

• Lamp 1
  Device evidence and notes

  Never observed driven: neither retained table binds it, and the ROM's attract lamp chase left it dark through the whole hash-pinned observation window. That is not proof the address is unused (the chase may not exercise every fitted bulb), so the address stays unknown rather than unused.

• Lamp 2
  Device evidence and notes

  Never observed driven: neither retained table binds it, and the ROM's attract lamp chase left it dark through the whole hash-pinned observation window. That is not proof the address is unused (the chase may not exercise every fitted bulb), so the address stays unknown rather than unused.

• Lamp 4
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 12
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 13
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 27
  Device evidence and notes

  Bound by the retained script's UpdateLamps fade loop. The retained table renders this address as a colored bulb Primitive (L27-L30) stacked with its three siblings at raw (401.3, 263.9, z 290), each paired with a Flash glow object (f27-f30) clustered around raw (352.5, 250-371). Four physical bulbs cannot share one point and the stack gives no basis for four distinct positions, so this record carries no spatial key; the stack is disclosed in the retained geometry dump.

• Lamp 28
  Device evidence and notes

  Bound by the retained script's UpdateLamps fade loop. The retained table renders this address as a colored bulb Primitive (L27-L30) stacked with its three siblings at raw (401.3, 263.9, z 290), each paired with a Flash glow object (f27-f30) clustered around raw (352.5, 250-371). Four physical bulbs cannot share one point and the stack gives no basis for four distinct positions, so this record carries no spatial key; the stack is disclosed in the retained geometry dump.

• Lamp 29
  Device evidence and notes

  Bound by the retained script's UpdateLamps fade loop. The retained table renders this address as a colored bulb Primitive (L27-L30) stacked with its three siblings at raw (401.3, 263.9, z 290), each paired with a Flash glow object (f27-f30) clustered around raw (352.5, 250-371). Four physical bulbs cannot share one point and the stack gives no basis for four distinct positions, so this record carries no spatial key; the stack is disclosed in the retained geometry dump.

• Lamp 30
  Device evidence and notes

  Bound by the retained script's UpdateLamps fade loop. The retained table renders this address as a colored bulb Primitive (L27-L30) stacked with its three siblings at raw (401.3, 263.9, z 290), each paired with a Flash glow object (f27-f30) clustered around raw (352.5, 250-371). Four physical bulbs cannot share one point and the stack gives no basis for four distinct positions, so this record carries no spatial key; the stack is disclosed in the retained geometry dump.

• Lamp 34
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 36
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 37
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 44
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 48
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 56
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 58
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 64
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 71
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 72
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 73
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 74
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 75
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 76
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 77
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 78
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 79
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• Lamp 80
  Device evidence and notes

  Observed driven by the ROM during the hash-pinned attract-mode harness run (see source runtime-scenario.bbh-attract-observe): the attract lamp chase drives every address except 1 and 2. A lamp-matrix bit lighting in attract proves the ROM drives the address, not that a physical bulb is fitted, so no construction or placement is claimed; the address is simply not the dead hole it would have to be to stay dark through a full attract cycle. Neither retained table renders it, so no placement exists.

• General Illumination
  Device evidence and notes

  Stern S.A.M. has exactly one general-illumination channel: sam.c sets coreGlobals.nGI and drives coreGlobals.gi[0] from its GI latch bit. The retained script matches that shape and then goes further: its UpdateGI ignores the string index entirely and switches one 27-member GI collection (GI_1..GI_27) plus an empty GI2 collection for any index, so a consumer cannot distinguish strings through this table. The partial manual prints no G.I. bulb inventory; its only related fact is the Back Panel Assembly's five clear socket & bulb assemblies (item 2, 518-5000-00-HF, qty 5), which it does not tie to any address. No bulb quantity and no placement set is asserted, so this record carries no spatial key; the 27 retained GI light positions are in the geometry dump.

Evidence needed to settle conflicts

• Elk button physical control

  a photograph of an unrestored machine's cabinet wiring where the D-9 to D-16 return harness is visible, or a continuity check of the left flipper button switch against the CPU board's flipper-column connector on real hardware.