Spy Hunter

Partial

Bally1984BY35bally.spy-hunter.1984

Wire it up

what an authoring tool needs first
Bind this ROM
spyhuntr

4 ROM sets resolve to this machine. Clones share the definition unless a hardware difference is listed.

Controller platform
pinmame.by35

PinMAME already reports logical active state. Do not invert again in the table — normally-closed is a physical fact recorded per switch, not a runtime transform.

Displays

No display inventory recorded yet.

Address space

Coverage

Partial

Real evidence exists, but authoring requirements are still missing or in conflict. Verify before shipping a table.

Completion19%

Progress is derived from the fixed author-readiness requirements. It helps rank unfinished work, but only a 100% author-ready definition passes the publication gate.

Catalog Identity
validated
Address Enumeration
unknown
Semantic Naming
unknown
Physical Wiring
unknown
Mechanisms
unknown
Variant Coverage
candidate
Recreation Knowledge
unknown
Still missing · 13
Driver MappingInput EnumerationInput SemanticsOutput EnumerationOutput SemanticsDisplay InventoryMechanism InventoryMechanism BehaviorPolarityVariant DifferencesRecreation NotesProvenanceSpatial Placement

Recreation notes

Working knowledge that has no schema field yet — edition differences, tuning values, pitfalls.

Coverage: partial - machine identity plus candidate-only I/O attachments. Playfield devices, wiring, mechanisms, and behavior are evidenced only as unverified candidates.

This record was promoted from the generated catalog stub stub.pinmame.spyhuntr by the catalog-wide identity pass of 2026-08-29. The promotion resolves machine identity and carries the catalog's residual driver grouping over unchanged, the platform and device attachments below were added by the 2026-08-29/30 candidate passes and assert nothing beyond candidate provenance. Every requirement in the definition's coverage.missing is genuinely outstanding.

Identity

  • PinMAME catalog: root driver spyhuntr, description "Spy Hunter", manufacturer "Bally", catalog year "1984".
  • OPDB record GRwl7-MJ45o (IPDB 2328) names this machine "Spy Hunter" (Bally, manufacture date 1984-01-01); the resolved identity rests on the agreement of the PinMAME catalog and this reviewed mapping.
  • The definition's driver list is exactly the clone tree PinMAME declares under spyhuntr; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • saturn2 (1985, Bell Games, clone of spyhuntr).
  • saturnfp (2021, Bell Games / Quench, clone of spyhuntr).
  • spyhunta (2004, Bally / Oliver, clone of spyhuntr).
  • spyhuntr (1984, Bally).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares spyhuntr at src/wpc/by35games.c:1797 with machine module by35_mBY35_45S; the definition declares controller platform pinmame.by35 from it.

What a curator must establish next

Full input, output, and display enumeration with semantic names; physical wiring and polarity; mechanism inventory and behavior; variant differences across the clone tree; recreation knowledge from a manual, schematic, or known-working table; runtime provenance; and a normalized spatial placement for every physical device. No manual, schematic, or runtime-harness evidence is retained for this machine yet; the candidate sections above are the only retained I/O evidence so far.

ROM sets

Every driver that resolves to this physical machine.

ROM set Description Year Parent Hardware
saturnfpSaturn 2 (Free Play) 2021spyhuntr
spyhuntaSpy Hunter (Free Play) 2004spyhuntr
saturn2Saturn 2 1985spyhuntr
spyhuntrSpy Hunter 1984

Parent set: spyhuntr — clones share this definition unless a hardware difference is noted.

Pinball memory maps

External source LGPL-3.0-only2 maps

RAM layouts published by an independent project and mirrored here at a pinned commit. They are not part of this machine’s definition: nothing below was used as evidence for the definition, and none of it counts towards coverage. Check claims against the upstream project.

Commit
d8693b9

This program makes use of content from the Pinball Memory Maps project.

system-rom-53-freeplay.map.json

bally-35-8Kv3format 0.8

maps/bally/as-2518-35/system-rom-53-freeplay.map.json

Applies to ROMs
spyhunta
Also covers
bmxacybrnauaelektraafathomafbclassakosteelam_mpacamedusaavectoraxsandosa
Sections
adjustmentsauditsgame_statehigh_scores

bally-35-8K defines the RAM layout this map’s offsets are read against — the map is not interpretable without it.

system-rom-53.map.json

bally-35-8Kv4format 0.8

maps/bally/as-2518-35/system-rom-53.map.json

Applies to ROMs
spyhuntr
Also covers
bmxcybrnautelektrafathomfbclasskosteelm_mpacm_mpacbmedusamedusafvectorxsandos
Sections
adjustmentsauditsgame_statehigh_scores

bally-35-8K defines the RAM layout this map’s offsets are read against — the map is not interpretable without it.

Evidence

Every claim above traces to one of these. When they disagree: a known-working VPX script wins on controller addresses and causality, the manual wins on wiring and construction, pinned PinMAME wins on emulator routing and display layout.

  • PinMAME catalog

    BSD-3-Clause

    pinmame.catalog.8371478a7640

    PinmameGetGames

    by
    PinMAME contributors
    rev
    8371478a7640
  • PinMAME source

    BSD-3-Clause

    pinmame.core.8371478a7640

    src/wpc/by35games.c:1797 (machine module by35_mBY35_45S)

    by
    PinMAME contributors
    rev
    8371478a7640

Something wrong or missing?

This definition still has 13 unmet requirements, listed under Coverage above. Fixes belong in the definition itself — editing on GitHub forks it for you and opens the pull request.

Cite a source for anything you change — a manual page, a line in a working VPX script, PinMAME source, or a reading from the machine's own service menu. Claims without provenance cannot be validated.

Same platform