Repository navigation
|
How can a team catch Random reward mechanic without disclosed odds automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rni 'lootbox\|loot box\|gacha\|mystery box\|random reward' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Loot box, gacha, or random reward purchase present without odds disclosed before purchase. The fix. Disclose the odds for every random reward before the user purchases. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
BOTH-LOOTBOX-ODDSwith a coverage line and a proper exit code.What the hit means. Loot box, gacha, or random reward purchase present without odds disclosed before purchase.
The fix. Disclose the odds for every random reward before the user purchases.
Recipe source. data/detection-recipes.json
This is a maintainer FAQ for a…