How to play
Fill in the unfinished template with your own commands, then run it. COMMIT releases a reservation to the railway. Watch after Run starts the clock automatically for new committed departures. Turn it off to use Play or Step +1 manually. If a train already has a reservation, choose Watch trains instead of dispatching it again. Editing code alone never moves a train.
The control desk
SQL queries run in Oracle. An id or train_id column highlights matching trains on the map. Run one SQL statement, anonymous block, or package definition at a time. / on its own final line is optional.
Run does not automatically commit. Oracle DDL, such as CREATE PACKAGE, does implicitly commit. Rollback cancels only uncommitted proposals; it never moves time backward.
Campaign & records
Discovery mode opens districts in order. All language syntax works from the start. Expert mode opens every contract for practice and preserves your records. Retrying restores the same tide and keeps code, discoveries, and best schedules.
Gold requires every delivery with zero delay and zero conflicts. Records prefer fewer conflicts, then lower maximum delay, then energy, then ticks. Equipment stays identical for each contract. Translucent trains show your best timetable.
Runtime
Programs execute in a private cloud Oracle database, in a restricted game schema. Calls are bounded and Stop cancels execution. Each visit reserves the railway for about 20 minutes. Your campaign is saved for this browser. End your session when you finish so another dispatcher can play. No replacement PL/SQL interpreter is used.