Eight Ball Deluxe

Partial
Completion6%

Bally1981bally.eight-ball-deluxe.1981.eballdlx Updated 2026-08-30 1 of 2 editions

OPDB IPDB bally/eight-ball-deluxe-1981-eballdlx.mdbally/eight-ball-deluxe-1981-eballdlx.json

Wire it up

what an authoring tool needs first
Bind this ROM
eballdp1eballdp2eballdp3eballdp4

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

Coverage

Partial

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

Completion6%

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 · 15
IdentityDriver MappingController PlatformInput 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 only. Nothing about playfield devices, wiring, mechanisms, or behavior is evidenced yet.

This record was promoted from the generated catalog stub stub.pinmame.eballdlx 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, and it deliberately asserts nothing else. Every requirement in the definition's coverage.missing is genuinely outstanding.

Identity

  • PinMAME catalog: root driver eballdlx, description "Eight Ball Deluxe (rev. 15)", manufacturer "Bally", catalog year "1981".
  • OPDB record G5KXk-MLB9V (IPDB 762) names this machine "Eight Ball Deluxe" (Bally, manufacture date 1981-04-01); identity is unresolved: OPDB record shared with bally.eight-ball-deluxe.1981, so the mapped record is treated as a lead rather than a resolved identity.
  • This is a split clone tree: the production drivers of eballdlx (including that root itself) belong to bally.eight-ball-deluxe.1981. This record holds only the residual drivers listed below, which may be physically different hardware such as prototypes; their fitment needs individual verification.

Drivers this record holds

  • eballdp1 (1981, Bally, clone of eballdlx).
  • eballdp2 (1981, Bally, clone of eballdlx).
  • eballdp3 (1981, Bally, clone of eballdlx).
  • eballdp4 (1981, Bally, clone of eballdlx).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares eballdp1 at src/wpc/by68701.c:469 with machine module by68701_61S; no platform is declared (the record does not hold its own root driver, so the root's module cannot describe its hardware).

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
eballdp4Eight Ball Deluxe (Prototype rev. 4) 1981eballdlx—
eballdp3Eight Ball Deluxe (Prototype rev. 3) 1981eballdlx—
eballdp2Eight Ball Deluxe (Prototype rev. 2) 1981eballdlx—
eballdp1Eight Ball Deluxe (Prototype rev. 1) 1981eballdlx—

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

Something wrong or missing?

This definition still has 15 unmet requirements, listed under Missing data below. 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

Other editions

Eight Ball Deluxe shipped in 2 editions with different playfields. Compare what each one actually has before building against this definition.

All 2 editions of Eight Ball Deluxe, side by side

Missing data

What this game definition still needs to reach 100% and become author-ready.

  • Machine identity

    Verify the physical title, manufacturer, year and edition against attributable sources.

  • ROM compatibility

    Verify which PinMAME drivers and firmware variants belong to this physical machine.

  • Controller hardware

    Identify the controller platform and validate its public address and routing rules.

  • Complete input inventory

    Account for every switch, service input and diagnostic address, including unused positions.

  • Input functions

    Validate which physical sensor or cabinet control each input represents and when it activates.

  • Complete output inventory

    Account for every coil, motor, lamp, flasher and general-illumination circuit, including unused addresses.

  • Output functions

    Validate the physical device, function and fitted quantity behind each output binding.

  • Displays

    Verify every display, its layout and its controller bindings.

  • Mechanism inventory

    Document every mechanism, its moving parts, actuators, sensors and connections.

  • Mechanism behavior

    Validate mechanism operation, ball paths, home positions, startup and reset behavior.

  • Switch construction and polarity

    Verify normally open or closed contacts and how PinMAME delivers their active states.

  • Edition and firmware differences

    Document supported hardware and firmware differences without combining incompatible editions.

  • Recreation knowledge

    Complete the source-backed behavior and assembly notes needed to recreate the machine.

  • Evidence and sources

    Back the remaining claims with attributable sources, exact locators, retained excerpts and verified hashes.

  • Physical device locations

    Establish validated playfield locations for every physical sensor, actuator and light emitter, including bulb counts and justified projections.