Overview
Reward schedules fail when they are either too predictable or too random. The fixed-ratio schedule (every 10 kills, a reward) is predictable — the player knows exactly when the reward will come and optimizes for it, turning gameplay into a transaction. The random schedule (any kill might drop a reward) is unpredictable — the player cannot anticipate the reward and experiences each drop as a surprise rather than a culmination. Both schedules produce engagement but neither produces anticipation — the feeling that a reward is approaching, which is more motivating than the reward itself.
The Reward Schedule Design prompt builds reward systems with three properties: (1) anticipation engineering — rewards are structured so the player can feel them approaching (a progress bar that fills toward a reward, a streak counter that builds toward a bonus, a luck meter that increases with each failure) without knowing exactly when they will arrive, (2) satiation prevention — repeated exposure to the same reward type reduces its motivational impact (the 100th loot drop is less exciting than the 1st), and the system rotates reward types, introduces novelty, and scales reward magnitude to prevent satiation, and (3) reward category management — different reward categories (functional, cosmetic, social, narrative) have different satiation rates and different anticipation mechanisms, and the system manages each category independently.
What you get: - Anticipation mechanism catalog (progress bars, streak counters, luck meters, escalating probability) - Satiation prevention protocol (rotation, novelty injection, magnitude scaling) - Reward category management (functional/cosmetic/social/novelty with different schedules) - Reward schedule audit checklist - Ethical reward boundary (distinguishing engagement from exploitation)
Built for: systems designers, live ops teams, and monetization designers who need reward systems that sustain motivation — not reward systems that burn it out.