Roderick Tron — terminal version
The second version, alongside web/ (browser). Runs on the
magmacrunch.engine terminal backend.
A clockwork gentleman crossing the rooftops of an 1810s Dutch city: three hand-authored levels, a roll that carries further than a run, a chimney draught, a bell cannon and a coal trolley.
pip install magmacrunch-roderick-tron
roderick-tron
It also appears in the arcade menu automatically — pip install magmacrunch
brings it along with every other cabinet.
The screen
Sixty columns, which is the widest floor of any cabinet in the arcade and is not arbitrary: the browser's viewport is thirty tiles, a tile is drawn two cells wide so that it comes out square at a terminal's aspect, and thirty times two is sixty. Below that the camera would show less of the level than the browser does, and the levels were authored against what the browser shows — a gap you cannot see the far side of is a leap of faith rather than a jump.
Controls
← → |
walk; hold to build speed |
Space W ↑ |
jump |
X |
roll |
Z |
fire a note |
P |
pause |
R |
restart the level |
Esc |
back to the title |
Two verbs from the browser are missing, and both because a terminal reports
key presses and never releases. There is no variable jump height, and the run
is earned by travelling rather than selected with Shift. Neither costs any
level its solution — tests/test_reachable.py searches all three with the
smaller move set and agrees with the browser's own search, surface for surface.
Tests
pip install -e ".[dev]"
python -m pytest -q
Most of it needs nothing but pytest: tron/ imports no engine, and
test_physics.py proves it in a subprocess. Two suites want node as well,
and skip themselves without it — test_oracle.py runs the shipped browser
modules in a vm and compares the port frame by frame, and
test_reachable.py compares the two level searches. CI makes a skip fatal.
The level art in tron/levels.py is generated from web/js/levels.js by
tools/gen_levels.py and checked in CI, so the two versions cannot drift.
Metadata
Release files for magmacrunch-roderick-tron 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| magmacrunch_roderick_tron-0.1.0.tar.gz | 71.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| magmacrunch_roderick_tron-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 115.7 kB
Release files / magmacrunch_roderick_tron-0.1.0.tar.gz
| Download URL | magmacrunch_roderick_tron-0.1.0.tar.gz |
|---|---|
| Size | 71.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbb1beb59cf64ba48056e849ade24248b49016c458574c3e7f0fa00d670c2b8c
|
|
BLAKE2b-256 checksum How to use checksums |
03250db89c0190987df7a220a59603ba53a02506fb228be3585bf28d3ff762db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / magmacrunch_roderick_tron-0.1.0-py3-none-any.whl
| Download URL | magmacrunch_roderick_tron-0.1.0-py3-none-any.whl |
|---|---|
| Size | 44.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84d84f4ec945546b43b1fb3345833a1152f7875d51273a24e3408fbf382d8f3c
|
|
BLAKE2b-256 checksum How to use checksums |
5d79cf5cf0dc182bf8a3425c1eb25984adec5346214668c00862c1b67cb6a9e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency log