Playboy

Partial
Completion19%

Bally1978BY35bally.playboy.1978 Updated 2026-08-30

Wire it up

what an authoring tool needs first
Bind this ROM
playboy

5 ROM sets resolve to this machine. Clones share the definition unless a hardware difference is listed.

Controller platform
pinmame.by35

PinMAME already reports logical active state. Do not invert again in the table — normally-closed is a physical fact recorded per switch, not a runtime transform.

Displays

No display inventory recorded yet.

Address space
Switches
1–40 (27)
Solenoids
13–13 (1)

Coverage

Partial

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

Completion19%

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 · 13
Driver MappingInput 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.

27 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.
27 shown
# Name Device ID Evidence
1
Target7
switch.target7 candidate
2
Target8
switch.target8 candidate
3
Target9
switch.target9 candidate
4
Target10
switch.target10 candidate
5
Target11
switch.target11 candidate
8
Drain
switch.drain candidate
17
Target6
switch.target6 candidate
18
Trigger3
switch.trigger3 candidate
19
Trigger4
switch.trigger4 candidate
20
Trigger5
switch.trigger5 candidate
21
Trigger6
switch.trigger6 candidate
22
Trigger12
switch.trigger12 candidate
23
Trigger9
switch.trigger9 candidate
24
Trigger10
switch.trigger10 candidate
25
Target5
switch.target5 candidate
26
Target4
switch.target4 candidate
27
Target3
switch.target3 candidate
28
Target2
switch.target2 candidate
29
Target1
switch.target1 candidate
30
Trigger2
switch.trigger2 candidate
31
Trigger8
switch.trigger8 candidate
33
Wall6
switch.wall6 candidate
36
Right Sling Shot
switch.right-sling-shot candidate
37
Left Sling Shot
switch.left-sling-shot candidate
38
Bumper3
switch.bumper3 candidate
39
Bumper2
switch.bumper2 candidate
40
Bumper1
switch.bumper1 candidate

Controlled devices

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

Coils, magnets & motors

1
1 shown
# Name Device ID Evidence
13
Dt Drop Sol Drop Up
coil.dt-drop-sol-drop-up 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.playboy 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 playboy, description "Playboy", manufacturer "Bally", catalog year "1978".
  • OPDB record GrkOB-MJVvl (IPDB 1823) names this machine "Playboy" (Bally, manufacture date 1978-12-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 playboy; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • playboy (1978, Bally).
  • playboyb (2004, Bally / Oliver, clone of playboy).
  • playboyc (2008, Bally / Oliver, clone of playboy).
  • playboyd (2008, Bally / Oliver, clone of playboy).
  • sexygirl (1980, Arkon (Germany), clone of playboy).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares playboy at src/wpc/by35games.c:390 with machine module by35_mBY35_32S; the definition declares controller platform pinmame.by35 from it.

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

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
playboydPlayboy (/10 Scoring Free Play) 2008playboy—
playboycPlayboy (Free Play rev. 3) 2008playboy—
playboybPlayboy (7-digit conversion rev. 20) 2004playboy—
sexygirlSexy Girl 1980playboy—
playboyPlayboy 1978——

Parent set: playboy — 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.

Commit
d8693b9

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

system-rom-30-7digit.map.json

bally-35-8Kv3format 0.8

maps/bally/as-2518-35/system-rom-30-7digit.map.json

Applies to ROMs
playboyb
Also covers
kissbkisseparagonbsstbstartrebvoltanb
Sections
adjustmentsauditsgame_statehigh_scores

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

system-rom-30-freeplay.map.json

bally-35-8Kv4format 0.8

maps/bally/as-2518-35/system-rom-30-freeplay.map.json

Applies to ROMs
playboycplayboyd
Also covers
paragoncparagondsstcsstdstartrecstartredvoltancvoltand
Sections
adjustmentsauditsgame_statehigh_scores

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

system-rom-30.map.json

bally-35-6Kv4format 0.8

maps/bally/as-2518-35/system-rom-30.map.json

Applies to ROMs
playboysexygirl
Also covers
kissparagonsststartrekvoltan
Sections
adjustmentsauditsgame_statehigh_scores

bally-35-6K 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

    by
    PinMAME contributors
    rev
    8371478a7640
  • PinMAME source

    BSD-3-Clause

    pinmame.core.8371478a7640

    src/wpc/by35games.c:390 (machine module by35_mBY35_32S)

    by
    PinMAME contributors
    rev
    8371478a7640
  • VPX script

    vpx-script.63e49618cb20b36a

    vpx-standalone-scripts: Playboy (Bally 1978)/Playboy (Bally 1978).vbs

    by
    Authors credited in Playboy (Bally 1978)/Playboy (Bally 1978).vbs and repository contributors
    rev
    15d112648a1b
    sha256
    63e49618cb20…
  • VPX script

    vpx-script.bf3817f43e25a607

    vpxtable-scripts: Playboy (Bally 1978).vbs

    by
    Authors credited in Playboy (Bally 1978).vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    bf3817f43e25…

Something wrong or missing?

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

Same platform

Missing data

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

  • ROM compatibility

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

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