Eight Ball

Partial

Bally1977bally.eight-ball.1977

OPDB IPDB bally/eight-ball-1977.mdbally/eight-ball-1977.json

Wire it up

what an authoring tool needs first
Bind this ROM
eightbll

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
1–40 (19)
Lamps
1–64 (64)

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
Hover or tap an address to identify it.
19 shown
# Name Device ID Evidence
1
Sw1
switch.sw1 candidate
2
Sw2
switch.sw2 candidate
3
Sw3
switch.sw3 candidate
17
Spinner1
switch.spinner1 candidate
25
Sw25
switch.sw25 candidate
26
Sw26
switch.sw26 candidate
27
Sw27
switch.sw27 candidate
28
Sw28
switch.sw28 candidate
29
Sw29
switch.sw29 candidate
30
Sw30
switch.sw30 candidate
31
Sw31
switch.sw31 candidate
32
Sw32
switch.sw32 candidate
33
Sw33
switch.sw33 candidate
34
Sw34
switch.sw34 candidate
36
Right Sling Shot
switch.right-sling-shot candidate
37
Left Sling Shot
switch.left-sling-shot candidate
38
Bumper1
switch.bumper1 candidate
39
Bumper2
switch.bumper2 candidate
40
Bumper3
switch.bumper3 candidate

Controlled devices

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

Lamps

64

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
49–56
57–64
Hover or tap an address to identify it.
64 shown
# Name Device ID Evidence
1
Li1
lamp.li1 candidate
2
Li2
lamp.li2 candidate
3
Li3
lamp.li3 candidate
4
Li4
lamp.li4 candidate
5
Li5
lamp.li5 candidate
6
Li6
lamp.li6 candidate
7
Li7
lamp.li7 candidate
8
Li8
lamp.li8 candidate
9
Li9
lamp.li9 candidate
10
Li10
lamp.li10 candidate
11
Li11
lamp.li11 candidate
12
Li12
lamp.li12 candidate
13
Li13
lamp.li13 candidate
14
Li14
lamp.li14 candidate
15
Li15
lamp.li15 candidate
16
Li16
lamp.li16 candidate
17
Li17
lamp.li17 candidate
18
Li18
lamp.li18 candidate
19
Li19
lamp.li19 candidate
20
Li20
lamp.li20 candidate
21
Li21
lamp.li21 candidate
22
Li22
lamp.li22 candidate
23
Li23
lamp.li23 candidate
24
Li24
lamp.li24 candidate
25
Li25
lamp.li25 candidate
26
Li26
lamp.li26 candidate
27
Li27
lamp.li27 candidate
28
Li28
lamp.li28 candidate
29
Li29
lamp.li29 candidate
30
Li30
lamp.li30 candidate
31
Li31
lamp.li31 candidate
32
Li32
lamp.li32 candidate
33
Li33
lamp.li33 candidate
34
Li34
lamp.li34 candidate
35
Li35
lamp.li35 candidate
36
Li36
lamp.li36 candidate
37
Li37
lamp.li37 candidate
38
Li38
lamp.li38 candidate
39
Li39
lamp.li39 candidate
40
Li40
lamp.li40 candidate
41
Li41
lamp.li41 candidate
42
Li42
lamp.li42 candidate
43
Li43
lamp.li43 candidate
44
Li44
lamp.li44 candidate
45
Li45
lamp.li45 candidate
46
Li46
lamp.li46 candidate
47
Li47
lamp.li47 candidate
48
Li48
lamp.li48 candidate
49
Li49
lamp.li49 candidate
50
Li50
lamp.li50 candidate
51
Li51
lamp.li51 candidate
52
Li52
lamp.li52 candidate
53
Li53
lamp.li53 candidate
54
Li54
lamp.li54 candidate
55
Li55
lamp.li55 candidate
56
Li56
lamp.li56 candidate
57
Li57
lamp.li57 candidate
58
Li58
lamp.li58 candidate
59
Li59
lamp.li59 candidate
60
Li60
lamp.li60 candidate
61
Li61
lamp.li61 candidate
62
Li62
lamp.li62 candidate
63
Li63
lamp.li63 candidate
64
Li64
lamp.li64 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.eightbll 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 eightbll, description "Eight Ball", manufacturer "Bally", catalog year "1977".
  • OPDB record GrN7J-MJ78q (IPDB 760) names this machine "Eight Ball" (Bally, manufacture date 1977-01-17); 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 eightbll; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • eightblb (2008, Bally / Oliver, clone of eightbll).
  • eightblc (2018, Bally, clone of eightbll).
  • eightbll (1977, Bally).
  • eightblo (1977, Bally, clone of eightbll).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares eightbll at src/wpc/by35games.c:139 with machine module by35_mBY17; no platform is declared (no reviewed profile covers that module yet).

VPX script candidates (candidate)

  • 2 retained community table script(s) declare this machine's driver; their extracted switch/lamp/solenoid/GI candidates are carried as 83 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
eightblcEight Ball (Free Play+) 2018eightbll—
eightblbEight Ball (Free Play) 2008eightbll—
eightbloEight Ball (Old/Tilt Bug) 1977eightbll—
eightbllEight Ball 1977——

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

Pinball memory maps

External source LGPL-3.0-only3 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.

Upstream
tomlogic/pinball-memory-maps
Commit
d8693b9

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

system-rom-20-freeplay1.map.json

bally-17-8Kv2format 0.8

maps/bally/as-2518-17/system-rom-20-freeplay1.map.json

Applies to ROMs
eightblb
Also covers
evelknibnightrdbblackjcbpwerplabmataharbstk_sprb
Sections
adjustmentsauditsgame_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

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

system-rom-20-freeplay2.map.json

bally-17-4Kv3format 0.8

maps/bally/as-2518-17/system-rom-20-freeplay2.map.json

Applies to ROMs
eightblc
Also covers
evelknicfreedombnightrdcblackjcdpwerplacmataharcstk_sprc
Sections
adjustmentsauditsgame_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

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

system-rom-20.map.json

bally-17-4Kv2format 0.8

maps/bally/as-2518-17/system-rom-20.map.json

Applies to ROMs
eightbll
Also covers
evelknienightr20nightrdrblackjckpwerplaymataharistk_sprs
Sections
adjustmentsauditsgame_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

bally-17-4K 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.b4b6860523214100

    vpxtable-scripts: Eight Ball (Bally 1977) v600.vbs

    0c036bb61b4b
    by
    Authors credited in Eight Ball (Bally 1977) v600.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    b4b686052321…

  • VPX script

    vpx-script.74a4bc3047a1fa30

    vpxtable-scripts: Eight Ball 1.0.0.vbs

    0c036bb61b4b
    by
    Authors credited in Eight Ball 1.0.0.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    74a4bc3047a1…

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