ORDA
The city doesn’t open up. It gets worse
- In development
- Game
- Unity 6.3 · URP · in development
- Unity 6.3 · URP 17 · RevFramework · AI Navigation
A small-map, fully-open horde survival game where the whole city is available from the first second and the only thing that changes is what is in it.
Released, dated, or taking wishlists. It is in development and there is a playtest build, which is a different thing from a game.
The premise
You are not expected to clear the map at the end of a wave.
Zombies are persistent inhabitants of the world. One that enters during wave 1 and survives can still be there in wave 10. Each wave brings its full scheduled assault regardless of how many are already standing — existing enemies do not reduce the next allocation. If a hundred remain when a wave bringing another hundred begins, you now have two hundred.
Which produces one trade-off, repeated for as long as you last:
Kill them now and spend resources, health and time. Leave them alive and carry the danger forward.
Avoiding a fight is completely legitimate. It also creates population debt. Streets and routes that were manageable earlier stop being manageable, not because the game decided to escalate, but because of how your run went.
Why the tagline is the design
Open-world games train you to treat the map as a reward. Districts unlock, the world expands as you get stronger, progress is measured in territory gained.
ORDA hands you the whole city at second zero, so the map can never be a reward. All 46 sectors are live from the first frame — no keys, no unlock flags, no gating logic anywhere in the scene or the code. A hundred residents are seeded across the map before you take a step.
The only variable left is what is in the city. And that moves one way.
Built on RevFramework, as an ordinary consumer
ORDA uses RevFramework the way a customer would: the same package, the same public API, no privileged access and no modifications.
Every system it adopts is written up against what it actually cost — which game code had to change, what adapters were needed, what worked through the public API for nothing, what failed silently, and where the framework’s assumptions and the game’s design disagreed. Including the times the framework came off worse.
That record is the point. A framework nobody has shipped anything with is a hypothesis.
Where it is
There is a playtest build and a long development record. There is no release date, no store page and no wishlist link, and there will not be any of those until there is something worth putting behind them.
The development log is kept honestly — reversed decisions get a new entry explaining the change rather than a quiet edit, and the marketing lines are held to a higher standard than the design notes. One of them currently carries a banner saying two of its claims stopped being true, with the measurements that showed it, and an instruction not to put either in front of anybody until they are true again.