A season content server, from design to live
I designed the whole server side of a seasonal boss mode: battles, season settlement, daily rankings and time-limited rewards. After release, I kept handling its live issues.
Situation
A new mode where, each season, players clear boss stages in order and earn rewards from season and daily rankings. It shares the main stage deck and the idle reward settlement, but it must not affect records or stats in other content. Battles, settlement, time-limited rewards and analytics logs all had to ship together within a fixed release schedule.
Decisions
Stage numbers: I numbered stages relative to the season. With global numbers, a mission condition like “Clear stage 30” would be met by a single first clear in the next season.
Season settlement: I made it pay out synchronously at query time, the same way as the existing PvP season rewards. I rejected deferred settlement with delivery by mail, because a query right after a new season starts could see a state that was not settled yet.
Shared deck: I only read the main stage deck and left its “last used” record untouched, because several features read that value, including combat power rankings and analytics logs.
Rewards and battles: Time-limited rewards are equipped in two layers, a base slot and a time-limited slot, and their validity conditions are fixed at grant time. For battles, as agreed with the team, I reused the structure of the existing boss battles to reduce the risk a new structure would bring.
Result
The same change included validation rules that catch game design data mistakes at server boot and about 500 lines of domain spec tests. Before release, I also changed the reward validation rules to work per season, so data that grants the same limited reward again each season is accepted. The content shipped in the September 2026 season update.
After release, I fixed a bug where the server's combat power calculation did not match the client display, and added validation that prevents the same mistake.