Nudge It

Partial
Completion6%

Gottlieb1990gottlieb.nudge-it.1990 Updated 2026-08-30

gottlieb/nudge-it-1990.mdgottlieb/nudge-it-1990.json

Wire it up

what an authoring tool needs first
Bind this ROM
nudgeit

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
3–17 (9)
Solenoids
28–30 (2)
Lamps
10–54 (25)

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.

9 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
Hover or tap an address to identify it.
9 shown
# Name Device ID Evidence
3
Start Button
switch.start-button candidate
7
Sw7
switch.sw7 candidate
11
Sw1
switch.sw1 candidate
12
Sw2
switch.sw2 candidate
13
Sw3
switch.sw3 candidate
14
Sw4
switch.sw4 candidate
15
Sw5
switch.sw5 candidate
16
Sw6
switch.sw6 candidate
17
Sw17
switch.sw17 candidate

Controlled devices

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

Coils, magnets & motors

2
2 shown
# Name Device ID Evidence
28
Solpin
coil.solpin candidate
30
Sol Knocker
coil.sol-knocker candidate

Lamps

25

Lamp 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
49–56
Hover or tap an address to identify it.
25 shown
# Name Device ID Evidence
10
L10
lamp.l10 candidate
11
L11
lamp.l11 candidate
12
L12
lamp.l12 candidate
13
L13
lamp.l13 candidate
14
L14
lamp.l14 candidate
20
L20
lamp.l20 candidate
21
L21
lamp.l21 candidate
22
L22
lamp.l22 candidate
23
L23
lamp.l23 candidate
24
L24
lamp.l24 candidate
30
L30
lamp.l30 candidate
31
L31
lamp.l31 candidate
32
L32
lamp.l32 candidate
33
L33
lamp.l33 candidate
34
L34
lamp.l34 candidate
40
L40
lamp.l40 candidate
41
L41
lamp.l41 candidate
42
L42
lamp.l42 candidate
43
L43
lamp.l43 candidate
44
L44
lamp.l44 candidate
50
L50
lamp.l50 candidate
51
L51
lamp.l51 candidate
52
L52
lamp.l52 candidate
53
L53
lamp.l53 candidate
54
L54
lamp.l54 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.nudgeit 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 nudgeit, description "Nudge It", manufacturer "Gottlieb", catalog year "1990".
  • 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 nudgeit; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • nudgeit (1990, Gottlieb).

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 36 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
nudgeitNudge It 1990——

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

    vpxtable-scripts: Nudge-It (Gottlieb 1990).vbs

    0c036bb61b4b
    by
    Authors credited in Nudge-It (Gottlieb 1990).vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    7f678ba9df8d…

Something wrong or missing?

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

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

Missing data

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

  • Machine identity

    Verify the physical title, manufacturer, year and edition against attributable sources.

  • ROM compatibility

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

  • Controller hardware

    Identify the controller platform and validate its public address and routing rules.

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

Missing locations · 36