GAME MECHANICS HOARD

RETIREMENT/AGING

Units and characters aging out of service — veterans retiring after campaigns, heroes whose stats decline with years, generational succession where the founder's death passes play to an heir.

Crusader Kings is the concept as genre (your character will die; the game is what you built for the successor), Massive Chalice and Wildermyth run generational tactics where heroes age, retire into governance, and pass traits to descendants, sports management sims price every contract against decline curves, and Darkest Dungeon-likes let maxed heroes exit with legacy bonuses. Designers age their characters because mortality converts optimization into stewardship: an immortal roster converges on one solved team forever, but aging forces perpetual renewal — scouting successors, timing retirements, extracting value from a veteran's final seasons — and gives every character a complete arc (promising, prime, declining, gone) that immortals never earn. Aging also unlocks legacy systems: retired units become trainers, ancestors, or bloodlines, letting attachment compound across generations instead of dying with the individual. Time pressure changes too — a hero's prime is a spending window, so campaigns acquire urgency no doom clock has to impose. Key decisions: decline visibility and rate (stat erosion the player can plan around versus sudden cliffs), what retirement returns (legacy traits, mentor bonuses, narrative cameos — retirement as reward, not deletion), and inheritance fidelity — how much of what you loved about the veteran carries to the heir. Pitfall: aging as pure loss — if decline strips units of value and retirement is a tombstone with paperwork, players savescum against time itself; the design works when the generational turn is a trade (lose the veteran, gain the legacy) rather than a tax, because players will embrace mortality exactly as far as it gives something back.

SEEN IN

VIEW “RETIREMENT/AGING” IN THE MAP ▶