Joust

Partial
Completion13%

Williams1983williams.joust.1983 Updated 2026-08-30

OPDB IPDB williams/joust-1983.mdwilliams/joust-1983.json

Wire it up

what an authoring tool needs first
Bind this ROM
jst_l2

2 ROM sets 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
16–61 (20)
Solenoids
3–17 (4)

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.

20 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
49–56
57–64
Hover or tap an address to identify it.
20 shown
# Name Device ID Evidence
16
Switch16
switch.switch16 candidate
19
Switch19
switch.switch19 candidate
20
Switch20
switch.switch20 candidate
21
Switch21
switch.switch21 candidate
22
Switch22
switch.switch22 candidate
29
Left Sling Shot
switch.left-sling-shot candidate
30
Right Sling Shot
switch.right-sling-shot candidate
31
Switch31
switch.switch31 candidate
40
Switch40
switch.switch40 candidate
43
Switch43
switch.switch43 candidate
44
Switch44
switch.switch44 candidate
45
Switch45
switch.switch45 candidate
46
Switch46
switch.switch46 candidate
53
Left Sling Shot1
switch.left-sling-shot1 candidate
54
Right Sling Shot1
switch.right-sling-shot1 candidate
55
Switch55
switch.switch55 candidate
58
Flip L
switch.flip-l candidate
59
Flip R
switch.flip-r candidate
60
Flip2 L
switch.flip2-l candidate
61
Flip2 R
switch.flip2-r candidate

Controlled devices

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

Coils, magnets & motors

4
4 shown
# Name Device ID Evidence
3
Sol P1 Trough
coil.sol-p1-trough candidate
4
Sol P2 Trough
coil.sol-p2-trough candidate
16
CLO
coil.clo candidate
17
Flipper Relay
coil.flipper-relay 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.jst_l2 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 jst_l2, description "Joust (L-2)", manufacturer "Williams", catalog year "1983".
  • OPDB record G4den-MLRYK (IPDB 1316) names this machine "Joust" (Williams, manufacture date 1983-01-04); 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 jst_l2; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • jst_l1 (1983, Williams, clone of jst_l2).
  • jst_l2 (1983, Williams).

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 24 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
jst_l2Joust (L-2) 1983——
jst_l1Joust (L-1) 1983jst_l2—

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

Pinball memory maps

External source LGPL-3.0-only1 map

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.

generic-10KB.map.json

williams-system7-10Kv4format 0.8

maps/williams/system7/generic-10KB.map.json

Applies to ROMs
jst_l2
Also covers
barra_l1bk_l4csmic_l1fpwr2_l2jngld_l2pharo_l2solar_l2tmfnt_l5vrkon_l1wrlok_l3
Sections
adjustmentsauditsgame_statehigh_scores
Map JSONMap sourcePlatform JSONPlatform source

williams-system7-10K 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

  • VPX script

    vpx-script.ab181f58e32427de

    vpxtable-scripts: Joust (Williams 1983)1.0.vbs

    0c036bb61b4b
    by
    Authors credited in Joust (Williams 1983)1.0.vbs and repository contributors
    rev
    0c036bb61b4b
    sha256
    ab181f58e324…

Something wrong or missing?

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

  • 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 · 24