Proudly independent Powered by spite & questionable spells
The Tower/Blog/Designing a 31-day world boss where the best reward can't be bought
Blog · Crownfall: Kingdoms

Designing a 31-day world boss where the best reward can't be bought

Why we capped hits instead of damage in Crownfall: Kingdoms, and what that trade-off costs

By Cinder (dev), Angry Old Wizards · November 18, 2026
Crownfall: Kingdoms key art

By Cinder, developer at Angry Old Wizards. Disclosure: this is about our own game, Crownfall: Kingdoms, a free iPhone kingdom strategy game with optional gem purchases.

On November 17 we started our first live event: The Eclipse King Rises, a world boss that every kingdom in Crownfall fights together for 31 days. We're a tiny studio. Our audience is small and new, and we really didn't want the first event to tell players "the people with the biggest wallets win."

This post covers the one decision that shaped everything else: we capped hits, not damage. I'll explain why, what it costs, and the numbers, so you can steal the idea or avoid our mistakes.

The problem with "most damage wins"

Most world boss events in mobile strategy games pay out by damage. That's simple, readable, and fits the fantasy. It also means the leaderboard is mostly a power ranking. In a game where purchases speed up growth, a power ranking is also partly a spending ranking.

That's fine for a leaderboard. People expect the strongest kingdoms at the top, and you can't tell a strategy-game player their power doesn't count. It's a bad fit for the reward most players actually want: a cosmetic that says "I was there for the first event."

So we split the event into two tracks:

  1. Damage: shown on a worldwide top-10 leaderboard, with your own rank under it. Power matters here, as it should.
  2. Hits: the number of successful attacks you land. This is what unlocks the event's exclusive reward, two Founder avatar skins at 1,600 hits.

Why a hit cap is the fairness lever

A hit count alone doesn't solve anything. If hits were unlimited, the player who refills forces fastest would hit 1,600 on day two. The fairness comes from the cap: each player can land at most 10 successful hits per hour. The server enforces it, and nothing in the store raises it.

That one rule changes what the event rewards:

  • The pace is the same for everyone. The most hits anyone can land in 31 days is 31 × 24 × 10 = 7,440, and nobody can go faster.
  • 1,600 hits is about 160 capped hours out of 744. That's roughly 21% of the theoretical maximum. In practice it's about 52 hits a day, or five or six check-ins a day. Players who show up regularly get it; no single session can.
  • Late joiners can still make it. Someone who starts a week in still has around 24 days, which works out to about 67 hits a day. That's harder, but possible, and we wanted it possible.

The reward is basically a measure of showing up, the one thing in a free-to-play game that money doesn't buy.

The trade-offs (so you don't think it's free)

It can feel like a chore. Capped, hourly resources can become "log in or lose out." We tried to soften this in three ways:

  • The cap is generous enough that you don't need to play every hour.
  • The target is well under the maximum, so skipping nights is fine.
  • Every hit pays out on its own, so a short session never feels wasted (more on that below).

Strong players get less to chase. A high-power kingdom can't turn its power into the cosmetic any faster. We accepted that and gave them the damage leaderboard instead. It's visible, it's competitive, and it's where power is supposed to show.

It's more server work. A per-player rate limit on a shared, contested resource is the kind of thing that breaks under retries and flaky mobile connections. If a phone sends an attack, loses signal, and sends it again, you must not count it twice or charge the player's hourly budget twice. We gave every attack request a unique ID so a retry is safe. The app also says "Attack not confirmed. Retry safely." instead of failing silently. Getting that one message right was worth the effort.

Making every hit worth something

A long event with a far-off reward needs short-term rewards, or people stop by day four. So every successful hit pays:

  • Gold, every time. We tuned it so that Fight (with soldiers) and Assassinate (with spies) pay the same gold at the same kingdom investment. We didn't want one army type to be the obviously correct choice.
  • A small chance at a rare drop: 1–100 gems or 1–10 health crystals. Never both on one hit. These are the same gems people can buy, so a free player who keeps showing up gets some premium currency without paying.

We describe the rare drop in the app as a chance, not as something that happens every hit, and we did the same in the App Store event copy. If you run a drop like this, be careful about that wording. Players notice when "win gems!" really means "occasionally win gems."

One shared bar, many phases

Everyone hits the same Eclipse King. The health bar is huge on purpose (998 billion HP at launch): the community-scale number is part of the fantasy. When the server empties the bar, the phase counter goes up and the fight continues. The event runs its full 31 days either way. It doesn't end early just because a few strong kingdoms burned through it, which would have killed the hit track for everyone else.

The app shows the live HP, the worldwide attack total, the current phase, and your own hit and damage totals in one panel. In an event this long, "you've done 412 of 1,600" is the most motivating number on screen. Don't hide it behind a menu.

What we'd tell another small team

  • Pick which reward has to be fair, and protect that one. Not every reward has to be equal. Ours: damage can follow power; the cosmetic can't follow spending.
  • Cap the action, not the outcome. A hits-per-hour limit is easy to explain and easy to check on the server.
  • Set the target well under the cap. About 20% of the max worked out to "regular, not obsessive" for us. Check your own retention data before copying that number.
  • Pay out every action. A 31-day goal needs a reason to show up today.
  • Make retries safe before launch. Players will tap Fight twice on a train.
  • Say "chance" when it's a chance.

We'll write a follow-up after the event ends on December 18 with what actually happened: how many players reached 1,600, where they dropped off, and whether the cap felt fair or felt like a chore. If you've run a capped event and have opinions, I'd genuinely like to hear them.


Crownfall: Kingdoms is free on iPhone (iOS 16.4+), no ads, with optional gem purchases. The Eclipse King Rises runs until December 18, 2026, 9:00 AM ET. App Store · Angry Old Wizards