[QUEST] Dress To Impress🖤

Loop

[QUEST] Dress To Impress runs a creation-to-judgment loop: players build outfits, parade them on a runway, and receive peer votes. The 0.48 vibe score (quest; create; friends) confirms the engine is social validation, not competition in the traditional PvP sense. At 91,039 CCU across a two-minute snapshot window with negligible drop (-375), the audience is stable and not spiking — this is a retention plateau, not a growth wave. The 3,687,188 upvotes against 386,346 down (90.5% approval) signal the loop resolves satisfyingly for most players.

---

Mechanic

The stickiness lives in the pose layer. Runway poses are a micro-expression tool layered on top of the outfit itself — they convert a static display into a performance, adding a timing and presentation variable that pure dress-up games lack. This extends the judgment window: voters aren't just rating the outfit, they're rating the execution. That secondary signal keeps the creation loop from collapsing into a simple asset-comparison mechanic. With 91K concurrent players sustaining that loop in near-real-time, the pose interaction is doing meaningful retention work.

---

Spin

The current loop is peer-vote validation gated by runway access — players create, perform, and receive a binary crowd score. The reframe: replace crowd voting with a structured judge rotation, where players cycle between creator and judge roles on a fixed timer. This converts the 0.48 vibe score's latent "quest" signal into an explicit role-based progression loop. Judges accumulate a scoring reputation; creators chase specific judge archetypes rather than anonymous crowd approval. The social graph tightens, session length extends, and the approval rate — currently a blunt 90.5% aggregate — becomes a legible, personalized metric rather than a vanity number.