The setup
You command a tank section on a fifty-kilometre demilitarized zone in a fictional 2032. It's the last unarmed border on Earth, and the treaty says you may not fire first. The campaign opens under Weapons Tight, and the rules of engagement loosen one step per operation: Block & Deter, Return Fire Only, Fire on Hostile, Cross the Line, Free Fire. Early on, the problem is how to hold a crest, escort a convoy or get out of an ambush without being the one who starts it.
How it plays
- You plan routes and pin orders (watch arcs, waits, ROE, smoke, formation) on a map, then hit GO. There is no pause and no rewind after that. You keep commanding in real time, but the plan does most of the work.
- Hits break systems, not health bars: mobility, gun and optics. A tank with a thrown track is a tow job, not a dead unit.
- Front armour is thicker than your gun, so flanks matter. Being seen is something you spend. Tanks slow on climbs and side slopes, and the route ETA counts it.
- Routes drive the line you drew unless the ground is impassable. If you want the router's fastest line, you ask for it explicitly and see the trade first.
- Six operations make up one campaign. Each has an ORDERS card, and a radio net that only tells you what your crews actually saw.
- Does the rules-of-engagement ladder feel like a real constraint, or like a trick to be gamed?
- Does the enemy AI behave like a section commander, or like a script?
- Order pinning: is planning a whole fight before GO satisfying, or does it take control away from you?
Treaty Ground: Corridor 2032 on Steam
Trailer (direct video, about 5 MB): https://chillnowllc.com/presskit/traile ... r-720p.mp4
I'll be in this thread through the week, and I'm happy to answer anything about the design, the model behind the hits, or why a tank game has a rule against shooting. Thanks for reading.