game design perceived randomness audit

The problem

Game mechanics that are mathematically fair often feel rigged to players. When independent events produce streaks or loot drops don't match expectations, players feel sabotaged, leading to frustration and negative reviews.

What it does

• Analyzes whether randomness occurs before player choice (input) or after commitment (output) to ensure agency.
• Identifies Gambler's Fallacy risks where players will expect "pity" hits that the math doesn't provide.
• Evaluates if combat or reward systems undermine player competence by making deliberate actions feel unpredictable.
• Pinpoints specific streak patterns that will cause players to invent "the game knows what I need" conspiracy theories.
• Recommends UX and presentation tweaks to make statistical entropy feel authored and fair.

Why this beats prompting it yourself

Generic LLMs tend to focus on statistical balance and probability tables. This skill applies specialized game design heuristics to the psychology of uncertainty, distinguishing between formal fairness and perceived fairness.

Use cases

• Auditing hit-chance or crit-proc mechanics in tactical combat.
• Evaluating gacha, loot boxes, and reward pools for streak frustration.
• Reviewing procedural generation to ensure difficulty spikes feel earned rather than random.
• Designing pity systems and weighted drops that feel fair without being exploitable.

Known limitations

This does not perform heavy Monte Carlo simulations or formal statistical proofs. It focuses on the player experience and design logic rather than raw data crunching.