Dungeons & Dragons

Partial

Bally1987bally.dungeons-dragons.1987

OPDB IPDB bally/dungeons-dragons-1987.mdbally/dungeons-dragons-1987.json

Wire it up

what an authoring tool needs first
Bind this ROM
dungdrag

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
1–48 (35)
Solenoids
7–20 (11)

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.

35 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
Hover or tap an address to identify it.
35 shown
# Name Device ID Evidence
1
Dust1
switch.dust1 candidate
2
Dust2
switch.dust2 candidate
3
Dust3
switch.dust3 candidate
4
Dust4
switch.dust4 candidate
8
Sol Drain
switch.sol-drain candidate
12
Sw12
switch.sw12 candidate
13
Sw13
switch.sw13 candidate
16
Rebound
switch.rebound candidate
17
Bumper1
switch.bumper1 candidate
18
Bumper2
switch.bumper2 candidate
19
Bumper3
switch.bumper3 candidate
20
Bumper4
switch.bumper4 candidate
21
Left Slingshot
switch.left-slingshot candidate
22
Right Slingshot
switch.right-slingshot candidate
23
Trigger23
switch.trigger23 candidate
24
Trigger24
switch.trigger24 candidate
25
Shield25
switch.shield25 candidate
26
Shield26
switch.shield26 candidate
27
Shield27
switch.shield27 candidate
28
Sword28
switch.sword28 candidate
29
Sword29
switch.sword29 candidate
30
Sword30
switch.sword30 candidate
33
Drop Target Bottom
switch.drop-target-bottom candidate
34
Drop Target Middle
switch.drop-target-middle candidate
35
Drop Target Top
switch.drop-target-top candidate
36
Skill36
switch.skill36 candidate
37
Skill37
switch.skill37 candidate
38
Skill38
switch.skill38 candidate
41
Trigger41
switch.trigger41 candidate
42
Trigger42
switch.trigger42 candidate
43
Trigger43
switch.trigger43 candidate
44
Trigger44
switch.trigger44 candidate
46
Sw46
switch.sw46 candidate
47
Sw47
switch.sw47 candidate
48
Sw48
switch.sw48 candidate

Controlled devices

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

Coils, magnets & motors

11
11 shown
# Name Device ID Evidence
7
Sol DTBank
coil.sol-dtbank candidate
8
Sol Left Kicker
coil.sol-left-kicker candidate
9
Sol Right Kicker
coil.sol-right-kicker candidate
10
Sol Left Teleporter
coil.sol-left-teleporter candidate
11
Sol Right Teleporter
coil.sol-right-teleporter candidate
12
Sol Release
coil.sol-release candidate
14
Sol Drain
coil.sol-drain candidate
15
Knocker Solenoid
coil.knocker-solenoid candidate
17
Sol Gi
coil.sol-gi candidate
18
Sol Flexsave Right
coil.sol-flexsave-right candidate
20
Sol Flexsave Left
coil.sol-flexsave-left 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.dungdrag 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 dungdrag, description "Dungeons & Dragons", manufacturer "Bally", catalog year "1987".
  • OPDB record G4JBP-MJ6jr (IPDB 743) names this machine "Dungeons & Dragons" (Bally, manufacture date 1987-01-01); 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 dungdrag; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • dungdrag (1987, Bally).

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 46 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
dungdragDungeons & Dragons 1987——

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

    8371478a7640
    by
    PinMAME contributors
    rev
    8371478a7640

  • VPX script

    vpx-script.3b4dee007c47816a

    vpxtable-scripts: Dungeons and Dragons (Bally 1987) v.2.3.1.vbs

    0c036bb61b4b
    by
    Authors credited in Dungeons and Dragons (Bally 1987) v.2.3.1.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    3b4dee007c47…

  • VPX script

    vpx-script.ea7bbfa742d3f71f

    vpxtable-scripts: Dungeons&Dragons (Bally 1987) v1.1.2.vbs

    0c036bb61b4b
    by
    Authors credited in Dungeons&Dragons (Bally 1987) v1.1.2.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    ea7bbfa742d3…

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