Mystic

Partial

Bally1980BY35bally.mystic.1980

OPDB IPDB bally/mystic-1980.mdbally/mystic-1980.json

Wire it up

what an authoring tool needs first
Bind this ROM
mystic

2 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
2–40 (15)

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.

15 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.
15 shown
# Name Device ID Evidence
2
Sw2
switch.sw2 candidate
3
Sw3
switch.sw3 candidate
4
Sw4
switch.sw4 candidate
5
Sw5
switch.sw5 candidate
12
Rlband004
switch.rlband004 candidate
17
Sw17
switch.sw17 candidate
18
Sw18
switch.sw18 candidate
19
Sw19
switch.sw19 candidate
20
Sw20
switch.sw20 candidate
32
Sw32
switch.sw32 candidate
36
Right Sling Shot
switch.right-sling-shot candidate
37
Left Sling Shot
switch.left-sling-shot candidate
38
Bumper001
switch.bumper001 candidate
39
Bumper002
switch.bumper002 candidate
40
Bumper003
switch.bumper003 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.mystic 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 mystic, description "Mystic", manufacturer "Bally", catalog year "1980".
  • OPDB record G5Bnl-MLnw6 (IPDB 1650) names this machine "Mystic" (Bally, manufacture date 1980-06-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 mystic; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • mystic (1980, Bally).
  • mysticb (2004, Bally / Oliver, clone of mystic).

PinMAME source contract (candidate)

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

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 15 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
mysticbMystic (7-digit conversion) 2004mystic—
mysticMystic 1980——

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

Pinball memory maps

External source LGPL-3.0-only2 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-35-7digit.map.json

bally-35-8Kv2format 0.8

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

Applies to ROMs
mysticb
Also covers
dollyptbfuturspbhglbtrtbhotdoggbngndshkbrollstobslbmanibspaceinbvikingb
Sections
adjustmentsauditsgame_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

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

system-rom-35.map.json

bally-35-6Kv2format 0.8

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

Applies to ROMs
mystic
Also covers
dollyptnfuturspahglbtrtrhotdoggnngndshkrrollstonslbmaniaslbmanicslbmanidspaceinvviking
Sections
adjustmentsauditsgame_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

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

    8371478a7640
    by
    PinMAME contributors
    rev
    8371478a7640

  • PinMAME source

    BSD-3-Clause

    pinmame.core.8371478a7640

    src/wpc/by35games.c:816 (machine module by35_mBY35_51S)

    src/wpc/by35games.c
    by
    PinMAME contributors
    rev
    8371478a7640

  • VPX script

    vpx-script.40af231e3e88ccbd

    vpxtable-scripts: Mystic (Bally 1980) v600.vbs

    0c036bb61b4b
    by
    Authors credited in Mystic (Bally 1980) v600.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    40af231e3e88…

Something wrong or missing?

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

Same platform

KissBally · 1979Fireball IIBally · 1980Flash GordonBally · 1980FrontierBally · 1980Nitro Ground ShakerBally · 1980Space InvadersBally · 1980