Bobby Orr's Power Play

Partial

Bally1977bally.bobby-orr-s-power-play.1977

OPDB IPDB bally/bobby-orr-s-power-play-1977.mdbally/bobby-orr-s-power-play-1977.json

Wire it up

what an authoring tool needs first
Bind this ROM
pwerplay

3 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.

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

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.pwerplay 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 pwerplay, description "Power Play", manufacturer "Bally", catalog year "1978".
  • OPDB record G4en0-MJ5vB (IPDB 1858) names this machine "Bobby Orr's Power Play" (Bally, manufacture date 1977-02-24); 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 pwerplay; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • pwerplab (2008, Bally / Oliver, clone of pwerplay).
  • pwerplac (2018, Bally, clone of pwerplay).
  • pwerplay (1978, Bally).

PinMAME source contract (candidate)

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

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
pwerplacPower Play (Free Play+) 2018pwerplay—
pwerplabPower Play (Free Play) 2008pwerplay—
pwerplayPower Play 1978——

Parent set: pwerplay — 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
pwerplab
Also covers
eightblbevelknibnightrdbblackjcbmataharbstk_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
pwerplac
Also covers
eightblcevelknicfreedombnightrdcblackjcdmataharcstk_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
pwerplay
Also covers
eightbllevelknienightr20nightrdrblackjckmataharistk_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

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