- 01Read occupancy
- 02Reserve a route
- 03Enter and leave
- 04Release and recheck
Rail blocks and reservations
Trains check occupancy/reservations before shared track. Sections prevent collisions, but bad waiting positions can block junctions.
The player's decision
Enter an empty junction now or wait until its exit is available?
Original scenario
Original: two timber trains cross; waiting in the junction for a full platform blocks another otherwise free route.
Start with this prototype
Build a crossing, two trains and four signal positions. Label occupancy/reservations with colors and IDs; step ten ticks without collisions and deliver with both trains. Reset signals.
Change one variable
Vary unloading time and inspect which signal layouts deadlock.
What to observe in a playtest
Only one conflicting reservation may win; departures and reset must release locks.
Take the full design card
Includes rules, scope, tuning questions and sources for further planning. It does not create a project automatically.
Original analysis · version 1
Common pitfall
Red/green lights without section boundaries make problems hard to diagnose.
Observations and sources
Cases refer to public documentation. Developers and community wikis are credited separately; document review is not a claim of hands-on testing.
Brief for the studio
Opens the AI studio with the brief below in the input. You can edit it. Nothing starts automatically.
Build a crossing, two trains and four signal positions. Label occupancy/reservations with colors and IDs; step ten ticks without collisions and deliver with both trains. Reset signals.
Covers are original AI-generated style illustrations. Game names reference publicly visible design choices and remain the property of their owners. This atlas does not supply screenshots or assets from those games. Prompts and combinations are original drafts for new games.