Novelty Inside Familiarity
Recurring Event Refreshes
Refreshed Civil War, Winter, and Turtle events: familiar identity + new mechanics, stronger rewards, secrets, and special encounters.
Role
Game Designer · Live Events
Status
Shipped
Tools
Confluence, Jira, Analytics dashboards
Design Breakdown
Civil War 2023: Refresh Example
One named example of recurring-event refresh work: preserve what players recognize, then change enough to give veterans a new reason to care.
What stayed familiar
- Civil War's faction identity and recognizable event framing stayed intact.
- Returning players could still map the event to what they already knew.
What changed
- New reward shaping and optional peaks created stronger reasons to go deeper.
- Refresh elements gave the run a fresher payoff without rewriting the event's core identity.
Motivation targeted
- Veteran players needed novelty without having to relearn the whole event.
- The refresh aimed to turn familiarity from staleness into quick re-entry plus a sharper chase.
What refreshes have to protect
A refresh fails if returning players cannot tell what changed. Each one keeps the event identity readable at a glance, then adds the new layer on top of what players already know.
Context
- Recurring events are valuable because players recognise them, but that same familiarity can make them feel solved. My work on Civil War 2023, Winter Event 2024 and Revenge of the Turtle 2025 focused on preserving the event identity while giving players something meaningfully new to notice.
- The refreshes combined new mechanics, quest beats, reward structures, secret quests and special encounters so different player segments had a reason to come back.
Problem
- Recurring events can become predictable for veteran players.
- Refreshing them requires change without losing the structure that makes them efficient to run and easy to re-enter.
- Rewards and mechanics must give returning players a reason to care without destabilising the economy.
Constraints
- Events had to ship inside an ongoing live-service calendar.
- Existing event identities and player expectations needed to be preserved.
- New content had to be documented clearly enough for implementation and live support.
Design decisions
- Preserved recognisable event identities so players could re-enter quickly and spot the new layer without relearning the whole structure.
- Added secret quests and special encounters as optional peaks for engaged players.
- Reshaped reward structures to support different participation depths, from casual play to completion-focused runs.
- Documented new mechanics clearly enough for implementation, live support and tuning inside the event calendar.
Outcome
- Refreshed Civil War 2023, Winter Event 2024 and Revenge of the Turtle 2025.
- Added new mechanics, reward structures, secret quests and super admiral encounters.
- Kept each event recognisable so returning players could re-enter quickly and see what had changed.
What this shows
- These refreshes show the kind of live design work I want to keep doing: not replacing familiar content, but sharpening it so a veteran audience has a new reason to log in.
- The result was stronger event identity, clearer reasons to engage, and fresh peaks layered onto content players already understood.