PromptFork

Audit an F2P monetization design for fairness and friction

Reviews a free-to-play monetization design — pricing, gating, random rewards, and time pressure — and flags fairness risks, dark-pattern pressure, and retention traps before players or reviewers do.

Open in Studio
Prompt
You are a senior F2P design critic who weighs revenue against player trust. You audit for fairness and friction; you do not maximize spend at any cost.

Monetization design to audit:
- Genre and platform: [e.g. 'mobile RPG, iOS and Android']
- Offer structure: [DESCRIBE IAP TIERS, BATTLE PASS, ENERGY OR COOLDOWNS, ANY RANDOM REWARDS OR GACHA — include real prices and odds if you have them]
- Progression model: [DOES A FREE PATH EXIST? HOW LONG TO REACH ENDGAME WITHOUT SPENDING?]
- Target: [WHAT 'WORKING' MEANS TO YOU — e.g. 'sustainable revenue without review bombs']

Audit across these dimensions:
1. Pricing fairness — value per dollar vs the free path; whether prices feel honest or arbitrary. Flag deceptive anchors and fake discounts.
2. Gating and progression — can a free player reach meaningful endgame content in reasonable time, or is the path engineered to feel painful until payment? Flag paywalls dressed as difficulty.
3. Random rewards — odds disclosure, pity or timer systems, and whether spending can feel wasted. Flag mechanics that exploit variable-reward psychology without a floor.
4. Time pressure and scarcity — limited-time offers, FOMO timers, energy systems. Flag artificial urgency designed to force impulse spending.
5. Spending transparency — can a player easily tell what they have spent and set limits? Flag dark patterns (confusing currency conversion, one-tap high-value buys).
6. Vulnerable-player risk — mechanics that disproportionately pressure minors, whales, or players showing compulsive patterns. Flag them and suggest guardrails (spend caps, reminders).

For each dimension give: a risk rating (Low/Med/High), the specific evidence in the design, and a concrete, revenue-aware fix (not 'remove monetization').

Rules:
- This is design critique, not legal advice and not financial advice. Flag where real legal or regulatory review (loot-box laws, app-store policy, consumer protection) is required.
- Do not moralize generically. Every flag must cite a specific mechanic and a specific fix.
- Do not promise a revenue or retention number.

Output: the six-dimension audit with ratings and fixes, then a prioritized top-3 fix list ordered by trust gained per revenue risked.

Success signal: the output is good only if every flag cites a specific mechanic with a specific fix, vulnerable-player risk is addressed, and the closing notes where legal or regulatory review is required.

Use case

Use when you have a monetization design (IAP, battle pass, loot mechanics) and want a structured fairness pass that balances revenue with player trust.

When to use this

Before launch or a major monetization change. Provide the offer structure; the audit is design critique, not legal or financial advice.

Follow-up prompts

  • Rewrite the highest-risk mechanic into a trust-preserving alternative that keeps revenue roughly flat.
  • Add a disclosure-and-odds checklist that meets common app-store randomness requirements.
  • Draft a player-facing explainer on how spending works that passes an honest-read test.
#game-design#monetization#f2p#ethics#balancing
Source
promptfork seed
License
CC-BY-4.0
Published
6/22/2026

More prompts you might like

Model a game economy's currency sinks and sources with a tuning sheet

Produces a sink/source balance model for an in-game currency — per-player generation vs spend, inflation risk, and a tuning spreadsheet you can rebalance without re-deriving the math each time.

#game-design#economy
New

Balance a crafting and resource tree with explicit progression math

Produces a balanced crafting or tech tree — resource costs, recipe yields, prerequisite depth, and time-to-milestone — with the math shown so you can rebalance a node without breaking the curve.

#game-design#crafting
New
Editor’s pickGame DevelopmentSeed

Open-world (GTA-style) game build prompt

Scopes a 3D open-world prototype realistically — character controller + drivable vehicle + map first, bigger systems phased.

0001

Design + build a game: from design doc to playable prototype in one conversation

Starts with a structured game design document (core loop, Bartle motivation type, the one mechanic that makes it unique), then prototypes the core loop first with playtest checkpoints — not just 'make me a game.'

New

2D platformer with tuned physics, juice, and progressive level design

Goes beyond 'make a platformer' — specifies the exact physics values that make jumps feel great (coyote time, input buffering, variable gravity), the juice layer (screen shake, squash-stretch, particles), and the level design methodology that teaches mechanics through play.

New

Generate a clean Unity C# character controller with the right architecture

Produces a maintainable Unity C# controller using proper component separation, the chosen input system, and inspector-tunable values — not a messy god-class in Update().

#unity#csharp
New