Kidnap

Partial

CICPlay1986cicplay.kidnap.1986

Wire it up

what an authoring tool needs first
Bind this ROM
kidnap

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
7–47 (29)
Solenoids
10–10 (1)

Coverage

Partial

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

Completion6%

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 · 15
IdentityDriver 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.

29 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.
29 shown
# Name Device ID Evidence
7
ROutlane
switch.routlane candidate
10
Bumper1
switch.bumper1 candidate
11
Bumper2
switch.bumper2 candidate
12
Right Sling Shot
switch.right-sling-shot candidate
13
Left Sling Shot
switch.left-sling-shot candidate
14
Rubber SW1
switch.rubber-sw1 candidate
15
Rubber SW2
switch.rubber-sw2 candidate
17
Rubber SW3
switch.rubber-sw3 candidate
18
Rubber SW4
switch.rubber-sw4 candidate
19
Rubber SW5
switch.rubber-sw5 candidate
20
Rubber SW6
switch.rubber-sw6 candidate
21
Rubber SW7
switch.rubber-sw7 candidate
22
LInlane
switch.linlane candidate
23
LOutlane
switch.loutlane candidate
25
RInlane
switch.rinlane candidate
26
W26
switch.w26 candidate
27
W27
switch.w27 candidate
28
W28
switch.w28 candidate
29
W29
switch.w29 candidate
30
W30
switch.w30 candidate
31
W31
switch.w31 candidate
33
W33
switch.w33 candidate
34
Target34
switch.target34 candidate
35
Target35
switch.target35 candidate
36
Target36
switch.target36 candidate
37
Target37
switch.target37 candidate
38
Target38
switch.target38 candidate
39
Target39
switch.target39 candidate
47
Target47
switch.target47 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
10
Sol Game On
coil.sol-game-on 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.kidnap 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 kidnap, description "Kidnap", manufacturer "CICPlay", catalog year "1986".
  • No OPDB record is mapped for this driver in machines/opdb_id.csv, so the name above comes from the PinMAME catalog alone and is unverified.
  • The definition's driver list is exactly the clone tree PinMAME declares under kidnap; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • kidnap (1986, CICPlay).

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 30 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
kidnapKidnap 1986

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

    by
    PinMAME contributors
    rev
    8371478a7640
  • VPX script

    vpx-script.2c7f8f4d9eca3e9a

    vpxtable-scripts: Kidnap_VPX_1_0.vbs

    by
    Authors credited in Kidnap_VPX_1_0.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    2c7f8f4d9eca…

Something wrong or missing?

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