Bounty Hunter

Partial

Gottlieb1985gottlieb.bounty-hunter.1985

OPDB IPDB gottlieb/bounty-hunter-1985.mdgottlieb/bounty-hunter-1985.json

Wire it up

what an authoring tool needs first
Bind this ROM
bountyh

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

Controller platform
Not determined
Displays

No display inventory recorded yet.

Address space
Switches
40–73 (19)
Solenoids
1–8 (4)
Lamps
6–47 (41)

Coverage

Partial

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

Completion13%

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 · 14
Driver MappingController PlatformInput EnumerationInput SemanticsOutput EnumerationOutput SemanticsDisplay InventoryMechanism InventoryMechanism BehaviorPolarityVariant DifferencesRecreation NotesProvenanceSpatial Placement

Switches

The addresses PinMAME reports as closed. Numbers are the public API values, not matrix hardware pins.

19 addresses

Switch map

Sequential addresses, grouped in columns of eight.

used unused
 
+0
+1
+2
+3
+4
+5
+6
+7
1–8
9–16
17–24
25–32
33–40
41–48
49–56
57–64
65–72
73–80
Hover or tap an address to identify it.
19 shown
# Name Device ID Evidence
40
Sw40
switch.sw40 candidate
41
Sw41
switch.sw41 candidate
42
Sw42
switch.sw42 candidate
43
Bumper1
switch.bumper1 candidate
44
Left Sling Shot
switch.left-sling-shot candidate
50
Tsw50
switch.tsw50 candidate
51
Tsw51
switch.tsw51 candidate
52
Sw52
switch.sw52 candidate
53
Sw53
switch.sw53 candidate
54
Sw54
switch.sw54 candidate
60
Tsw60
switch.tsw60 candidate
61
Tsw61
switch.tsw61 candidate
62
Sw62
switch.sw62 candidate
63
Sw63
switch.sw63 candidate
64
Sw64
switch.sw64 candidate
70
Tsw70
switch.tsw70 candidate
71
Tsw71
switch.tsw71 candidate
72
Sw72
switch.sw72 candidate
73
Kicker
switch.kicker candidate

Controlled devices

Everything the ROM can energise, grouped the way a table author builds it.

Coils, magnets & motors

4
4 shown
# Name Device ID Evidence
1
Soldtdrop
coil.soldtdrop candidate
2
Soltophole
coil.soltophole candidate
5
Soldtup
coil.soldtup candidate
8
Sol Knocker
coil.sol-knocker candidate

Lamps

41

Lamp map

Sequential addresses, grouped in columns of eight.

used unused
 
+0
+1
+2
+3
+4
+5
+6
+7
1–8
9–16
17–24
25–32
33–40
41–48
Hover or tap an address to identify it.
41 shown
# Name Device ID Evidence
6
L6a
lamp.l6a candidate
7
L7a
lamp.l7a candidate
8
L8a
lamp.l8a candidate
9
L9a
lamp.l9a candidate
10
L10
lamp.l10 candidate
11
L11
lamp.l11 candidate
12
L12
lamp.l12 candidate
13
L13
lamp.l13 candidate
14
L14
lamp.l14 candidate
15
L15
lamp.l15 candidate
16
L16
lamp.l16 candidate
17
L17
lamp.l17 candidate
18
L18
lamp.l18 candidate
19
L19
lamp.l19 candidate
20
L20
lamp.l20 candidate
21
L21
lamp.l21 candidate
22
L22
lamp.l22 candidate
23
L23
lamp.l23 candidate
24
L24
lamp.l24 candidate
25
L25
lamp.l25 candidate
26
L26
lamp.l26 candidate
27
L27
lamp.l27 candidate
28
L28
lamp.l28 candidate
29
L29
lamp.l29 candidate
30
L30
lamp.l30 candidate
31
L31
lamp.l31 candidate
33
L33
lamp.l33 candidate
34
L34
lamp.l34 candidate
35
L35
lamp.l35 candidate
36
L36
lamp.l36 candidate
37
L37
lamp.l37 candidate
38
L38
lamp.l38 candidate
39
L39
lamp.l39 candidate
40
L40
lamp.l40 candidate
41
L41
lamp.l41 candidate
42
L42
lamp.l42 candidate
43
L43
lamp.l43 candidate
44
L44
lamp.l44 candidate
45
L45
lamp.l45 candidate
46
L46
lamp.l46 candidate
47
L47
lamp.l47 candidate

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.bountyh 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 bountyh, description "Bounty Hunter", manufacturer "Gottlieb", catalog year "1985".
  • OPDB record G5nO8-ME0Wo (IPDB 361) names this machine "Bounty Hunter" (Gottlieb, manufacture date 1985-07-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 bountyh; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • bountgfp (1985, Flipprojets, clone of bountyh).
  • bounthfp (1985, Flipprojets, clone of bountyh).
  • bountyh (1985, Gottlieb).
  • bountyhg (1985, Gottlieb, clone of bountyh).

VPX script candidates (candidate)

  • 1 retained community table script(s) declare this machine's driver; their extracted switch/lamp/solenoid/GI candidates are carried as 64 candidate devices. When curator work weighs sources, a retained script outranks emulator-derived candidates for runtime semantics, but every device here is still a candidate until a known-working table is verified against this exact physical machine.

What a curator must establish next

Controller platform from the pinned PinMAME driver source; 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
bountyhgBounty Hunter (German) 1985bountyh—
bountyhBounty Hunter 1985——
bounthfpBounty Hunter (Free Play) 1985bountyh—
bountgfpBounty Hunter (German Free Play) 1985bountyh—

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

Pinball memory maps

External source LGPL-3.0-only1 map

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.

Upstream
tomlogic/pinball-memory-maps
Commit
d8693b9

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

80b-7digit-8KB.map.json

gottlieb-system80b-8Kv4format 0.8

maps/gottlieb/system80b/80b-7digit-8KB.map.json

Applies to ROMs
bountgfpbounthfpbountyh
Also covers
rockrockfprockgfprock_encrock_efprockegfptriplaytriplyfptriplyf1triplgfp
Sections
adjustmentsauditsdip_switchesgame_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

gottlieb-system80b-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

    8371478a7640
    by
    PinMAME contributors
    rev
    8371478a7640

  • VPX script

    vpx-script.b9d6c5c4e37312d6

    vpx-standalone-scripts: Bounty Hunter (Gottlieb 1985)/Bounty Hunter (Gottlieb 1985).vbs

    15d112648a1b
    by
    Authors credited in Bounty Hunter (Gottlieb 1985)/Bounty Hunter (Gottlieb 1985).vbs and repository contributors
    rev
    15d112648a1b
    sha256
    b9d6c5c4e373…

Something wrong or missing?

This definition still has 14 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.

Edit the definition Edit the note Report a problem
Before you startCONTRIBUTING.mdschemas/machine.schema.jsondocs/MACHINE_DEFINITIONS_PLAN.md How to read a definition