Overview
Retention loops fail when they are isolated. The game has a daily quest loop, a crafting loop, and a social loop. Each loop retains the player independently — if the player stops doing daily quests, they lose daily quest rewards but their crafting and social progress are unaffected. The player can disengage from any loop without consequence to the others, which means each loop must be compelling on its own — and when one loop becomes boring, the player drops it entirely rather than being pulled back by their investment in the other loops.
The Retention Loop Engineering prompt builds retention systems with three properties: (1) interdependent loops — each loop's output is another loop's input, creating a network where disengaging from one loop creates a deficit in another (daily quest rewards include crafting materials; crafted items improve daily quest performance; guild events require crafted items), (2) cycle-time calibration — each loop has a defined cycle time (daily, weekly, monthly) that determines how often the player must re-engage, and the cycle times are staggered so that at least one loop is always due for a cycle, and (3) churn prediction signals — each loop has defined metrics that indicate when the player is at risk of disengaging, and the system specifies interventions for each signal.
What you get: - Interdependent loop network diagram (which loops feed which) - Cycle-time calibration per loop (daily/weekly/monthly with staggering) - Churn prediction signal definitions with interventions - Loop health metrics (engagement rate, cycle completion rate, cross-loop participation) - New loop integration protocol (how to add loops without breaking interdependencies) - Retention loop audit checklist
Built for: live ops teams, systems designers, and game designers who need players who stay — not players who leave one loop at a time until nothing remains.