Video unavailable. Open the source below.
NewTypeSafe Mario
Jev chooses controller inputs for Super Mario Bros.
Added to Jevfast
How it uses Jev
The harness parses emulator telemetry and RAM into structured state about Mario, terrain, projected hazards, reaction timing, recent control outcomes, and level progress; the README says screenshots are not sent. Each request asks a Choice for the next legal controller macro, a Noul for whether to jump, and a Score for immediate danger. The controller applies the chosen macro, while the Noul and Score values are returned for logging and visualization.
What Jev decides
Illustrative Jev decisionExample answers · not a recorded Jev response · Source ↗
Question 1 · next action
YOUR APP
INSTRUCTION
Which controller macro should Mario commit to next? Advance toward the stage flag while avoiding death.
STATE
Parsed emulator telemetry and RAM: Mario position and jump phase, terrain reliability, projected hazards, reaction timing, recent control, and stage progress.
JEV · CHOICE
- noop
- right
- right_jump
- right_run
- right_run_jump
- jump
- left
Question 2 · jump needed
YOUR APP
INSTRUCTION
Should a forward jump begin or remain held now, given terrain, projected hazards, trajectory, and jump phase?
STATE
Parsed emulator telemetry and RAM: Mario position and jump phase, terrain reliability, projected hazards, reaction timing, recent control, and stage progress.
JEV · NOUL
YesNo
Question 3 · danger
YOUR APP
INSTRUCTION
How dangerous is Mario’s immediate situation?
STATE
Parsed emulator telemetry and RAM: Mario position and jump phase, terrain reliability, projected hazards, reaction timing, recent control, and stage progress.
JEV · SCORE
0
App workflow
- Parse the game state
Read emulator telemetry and RAM and build the object-centric snapshot.
- Ask three typed questions
Send the snapshot and legal action criteria for Choice, jump Noul, and danger Score judgments.
- Build the decision
Convert Jev's selected action, probabilities, jump probability, and danger score into a Decision.
- Run the action
Advance the emulator using the active action while the next decision can be requested asynchronously.
- Record and display
Log the snapshot, decision, reward, and timing; expose decision telemetry in the dashboard.
Why it is interesting
The parser calculates timing and hazard facts in code, then gives Jev those facts to interpret while leaving the action choice to Jev. This keeps deterministic game mechanics separate from the typed decision.