Iron Balls

Partial

Stargame1987stargame.iron-balls.1987

Wire it up

what an authoring tool needs first
Bind this ROM
ironball

1 ROM set 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
11–56 (28)

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

Switches

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

28 addresses

Switch map

Column × row matrix — the address is column·row.

used unused
 
1
2
3
4
5
6
7
8
1
2
3
4
5
Hover or tap an address to identify it.
28 shown
# Name Device ID Evidence
11
Sw11
switch.sw11 candidate
12
Sw12
switch.sw12 candidate
13
Sw13
switch.sw13 candidate
14
Sw14
switch.sw14 candidate
15
Sw15
switch.sw15 candidate
16
Sw16
switch.sw16 candidate
17
Sw17
switch.sw17 candidate
18
Rubber1
switch.rubber1 candidate
21
Sw21
switch.sw21 candidate
22
Sw22
switch.sw22 candidate
23
Sw23
switch.sw23 candidate
24
Sw24
switch.sw24 candidate
25
Sw25
switch.sw25 candidate
26
Sw26
switch.sw26 candidate
27
Sw27
switch.sw27 candidate
28
Rubber3
switch.rubber3 candidate
33
Sw33
switch.sw33 candidate
35
Left Bumper
switch.left-bumper candidate
36
Right Bumper
switch.right-bumper candidate
37
Middle Bumper
switch.middle-bumper candidate
38
Rubber2
switch.rubber2 candidate
41
Sw41
switch.sw41 candidate
45
Sw45
switch.sw45 candidate
47
Left Sling Shot
switch.left-sling-shot candidate
48
Right Sling Shot
switch.right-sling-shot candidate
51
Sw51
switch.sw51 candidate
55
Sw55
switch.sw55 candidate
56
Sw56
switch.sw56 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.ironball 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 ironball, description "Iron Balls", manufacturer "Stargame", catalog year "1987".
  • No OPDB record is mapped for this driver in machines/opdb_id.csv, so the name above comes from the PinMAME catalog alone and is unverified.
  • The definition's driver list is exactly the clone tree PinMAME declares under ironball; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • ironball (1987, Stargame).

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 28 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
ironballIron Balls 1987

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

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
  • VPX script

    vpx-script.bd463419852b6d95

    vpxtable-scripts: Iron Balls (Unidesa 1987) 1.1.vbs

    by
    Authors credited in Iron Balls (Unidesa 1987) 1.1.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    bd463419852b…

Something wrong or missing?

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