Rocky

Partial

Gottlieb1982gottlieb.rocky.1982

OPDB IPDB gottlieb/rocky-1982.mdgottlieb/rocky-1982.json

Wire it up

what an authoring tool needs first
Bind this ROM
rockyrockyf

2 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
3–65 (16)
Solenoids
2–9 (5)

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.

16 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
Hover or tap an address to identify it.
16 shown
# Name Device ID Evidence
3
Bumper1
switch.bumper1 candidate
5
Sw5
switch.sw5 candidate
13
Bumper2
switch.bumper2 candidate
14
Sw14
switch.sw14 candidate
15
Sw15
switch.sw15 candidate
16
Left Sling Shot
switch.left-sling-shot candidate
23
Bumper4
switch.bumper4 candidate
25
Sw25
switch.sw25 candidate
51
Sw51
switch.sw51 candidate
52
Sw52
switch.sw52 candidate
54
Sw54
switch.sw54 candidate
55
Sw55
switch.sw55 candidate
61
Sol RFlipper
switch.sol-rflipper candidate
63
Bumper3
switch.bumper3 candidate
64
Sw64
switch.sw64 candidate
65
Sw65
switch.sw65 candidate

Controlled devices

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

Coils, magnets & motors

5
5 shown
# Name Device ID Evidence
2
DTBank TReset
coil.dtbank-treset candidate
3
Sol Kicker
coil.sol-kicker candidate
5
DTBank RReset
coil.dtbank-rreset candidate
6
DTBank LReset
coil.dtbank-lreset candidate
9
Sol Ball Release
coil.sol-ball-release 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.rocky 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 rocky, description "Rocky", manufacturer "Gottlieb", catalog year "1982".
  • OPDB record GrJvk-MDekx (IPDB 1993) names this machine "Rocky" (Gottlieb, manufacture date 1982-01-09); 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 rocky; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • rocky (1982, Gottlieb, clone of gts80a).
  • rockyf (1982, Gottlieb, clone of rocky).

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 21 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
rockyfRocky (French Speech) 1982rocky—
rockyRocky 1982gts80a—

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.0a501544205ecdd7

    vpxtable-scripts: Rocky (Gottlieb 1982) Physics Sound Hybrid MOD.vbs

    0c036bb61b4b
    by
    Authors credited in Rocky (Gottlieb 1982) Physics Sound Hybrid MOD.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    0a501544205e…

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