
By Cinder, developer at Angry Old Wizards. Disclosure: this is about our own game, Crownfall: Kingdoms, a free iPhone kingdom strategy game.
Alliances are the heart of a persistent kingdom game. They're why people come back on day 30, and they're the scariest system for a tiny studio to build. Alliance play is social, concurrent, and full of edge cases, and when it breaks, it breaks in front of twenty people at once.
We launched Crownfall: Kingdoms on iPhone on November 10, 2026, with alliances, rallies, and Epic Battles: timed, multi-phase co-op fights that a whole alliance takes on together. Here's what we'd tell another small team, ordered by how much pain each lesson would have saved us.
1. Decide what "co-op" means before writing any code
"Alliance features" can mean twenty different things. We narrowed it to three verbs and built only what supported them:
- Talk. Alliance chat, roles, and recruitment. Without a place to coordinate, the other features don't matter.
- Gather. Rallies, where members pool effort against a target that's too strong for one kingdom.
- Endure. Epic Battles: enemies with several phases and a timer, designed so that preparation and sustained contribution beat one lucky strike.
Everything else (alliance tech trees, shared buildings, territory) went on the "later, maybe" list. A small team that ships three solid alliance verbs beats one that ships eight broken ones.
2. Make the server the only source of truth
In a solo game you can trust the client a bit. In co-op you can't trust it at all. Every attack, every point of damage, and every reward in an Epic Battle is decided on the server. The phone sends what it wants to do and shows what the server says happened.
This costs some responsiveness. There's a small wait between tapping and seeing the result. It saves you from the problem that ends small multiplayer games: two players' phones disagreeing about whether the boss is dead. Pick server authority on day one. Retrofitting it later is a rewrite.
3. Assume every request will be sent twice
Mobile networks drop requests constantly. A player taps Attack in an elevator. The request reaches the server, the response doesn't reach the phone, the app retries, and now the attack has happened twice.
The fix is simple, and we wish we'd started with it:
- Every action gets a unique ID made on the client. The server stores it. A repeated ID returns the original result instead of running the action again.
- The app tells the truth about uncertainty. If we don't know whether an attack landed, the app says so ("Attack not confirmed. Retry safely.") and the retry is safe by design.
This one pattern removed a whole category of "I got charged twice" and "my damage vanished" reports before they happened.
4. Realtime updates should mean "go check," not "here's the new state"
Co-op screens want to feel live. When an alliance-mate lands a hit, your health bar should move. The tempting design is to broadcast the new state (HP, phase, rankings) to everyone watching.
We do the reverse. A realtime message is just a signal to re-fetch from the server. Broadcasts can arrive late, twice, or out of order. If they carry state, an old message can overwrite a newer one, and the bar jumps backwards. If they only say "something changed," the worst case is an extra fetch.
We also number our own requests, so a slow, older response can't overwrite a newer one that already came back. It's a small detail, and it prevents the most visible kind of co-op bug: a health bar that jumps backwards when several people attack at once.
5. Time-box everything, and show the clock
Epic Battles are timed, and so is our world boss. Timers do three jobs for a small studio:
- They create the "now" that co-op needs. "Tonight, before the timer runs out" coordinates people better than "whenever."
- They limit the damage from bugs. A mistake in a timed encounter ends when the encounter does.
- They make content last. A multi-phase fight with a deadline can be replayed and tuned. A permanent one just gets solved.
Show the clock everywhere the encounter appears. Our event cards show the start time in a fixed zone ("9:00 AM ET") and a live countdown, because "starts at 9" means nothing to a player in another time zone.
6. Don't make solo players second-class
The biggest design call for our first live event: the world boss is open to every kingdom, including players with no alliance. Alliance play is our core, but a brand-new player who hasn't found an alliance yet shouldn't be locked out of the one thing everyone is talking about.
The event becomes a lobby. Solo players fight the same boss as the big alliances, see the same worldwide attack count, and get a reason to look for an alliance afterwards. Recruiting happens naturally instead of being forced.
7. Test the co-op flow with fewer people than you expect
Small studios rarely have twenty testers on call. You can find most co-op bugs with three accounts and a script:
- two players attacking the same target in the same second;
- one player leaving the alliance during a rally;
- a phone going offline mid-attack;
- a phase changing while a request is still in flight.
Give every ugly case a repeatable database test, then run them on every change. You don't need a big QA team. You need the four or five races that matter, written down and automated.
8. Ship it, then listen to the chat
We're a week past launch. Our alliances are small, our Epic Battles are still being tuned, and our first live event has just started. Analytics tell you where players stop. Alliance chat is where they explain why, in their own words. If you build chat first (lesson 1), you get a free, honest, always-on playtest. Read it.
The short version
- Three alliance verbs, done well: talk, gather, endure.
- The server decides everything.
- Every action has an ID; retries are safe.
- Realtime means "re-fetch," not "here's the state."
- Timers and fixed time zones on everything.
- Let solo players into the big moments.
- Automate the four or five races that matter.
If you're building co-op on a tiny team and want to compare notes, I'm happy to. Reach me at crownfall@angryoldwizards.com.
Crownfall: Kingdoms is free on iPhone (iOS 16.4+), no ads, with optional gem purchases. App Store · Angry Old Wizards