Local Multiplayer · Optional-Only IAP guide
Design one offer for local multiplayer with a single acceptance goal: prove the free path is complete and the purchase adds bounded value without manufactured friction or progression blocking. Keep the exact Koin price and a safe refusal path visible.
Create this game flow
Focused keyword and player case
Offer a 25 Koin appearance-only item after a safe pause. Keep every level and control available for free, remove countdown language, and make declining a normal return to play. For local multiplayer, Complete the core loop without opening the offer, compare paid and free outcomes, and reject any design that turns refusal into a penalty.
Use the focused optional-only iap hub for an authentic screenshot, direct playable result, and the complete purchase-state checklist. Gameplay evidence supports placement testing; it does not prove a live transaction.
The experience must show which player owns an item and prevent shared-device purchase confusion.
Preserve a complete playable path and avoid selling relief from deliberately created frustration.
Use one item and one Koin price so players can evaluate the complete choice without navigating a large shop.
Choose a calm point where local multiplayer groups understand the game context and can decline without interrupting active play.
Show the item, benefit, duration or quantity, full price in Koin, visible Koin balance, confirm, and cancel in plain language.
After cancellation or not enough Koin, preserve progress and return local multiplayer groups to an understandable game state.
Following a successful result, show ownership, equipped state, unlocked content, or remaining quantity where the item will be used.
Identify which player, profile, controller, or in-game character is making the choice and receiving the item. Cancel and delivery must not affect another participant, while shared-screen wording should avoid exposing private balance or account information.
Play the advertised core route from the first meaningful action through recovery and its promised conclusion without opening the offer. Record any place where storage, pacing, difficulty, retry access, story information, or social participation feels intentionally weakened. Decline the item at several natural moments and confirm that progress continues from the same point without repeated pressure. Then buy it and compare the owned experience against the free route: the item may add expression, bounded content, or reasonable convenience, but it must not reveal that frustration was manufactured to sell relief. Remove guilt, countdowns, loss threats, and language that treats a voluntary choice as required.
Play the complete promised game without opening the offer. Progress, recovery, and the core ending should still feel intentional. For local multiplayer groups, the experience must show which player owns an item and prevent shared-device purchase confusion.
Give players a visible dismiss action and return them to the exact game state they left without repeated pressure. For local multiplayer groups, the experience must show which player owns an item and prevent shared-device purchase confusion.
Avoid slowing ordinary progress or creating unnecessary limits simply to make the item that remains optional feel required. For local multiplayer groups, the experience must show which player owns an item and prevent shared-device purchase confusion.
Write this into the prompt before the item description: Show which player owns an item and prevent shared-device purchase confusion.
Result: A clear design constraint
Preserve a complete playable path and avoid selling relief from deliberately created frustration. Carry the same principle through confirmation and delivery.
Result: A consistent player experience
Name the benefit, duration or quantity, ownership rule, clearly stated Koin cost, and delivered result.
Result: An understandable offer
Try confirmation, cancellation, not enough Koin, repeated input, interruption, delivery, and reload without coaching.
Result: Audience-specific feedback
Change one prompt instruction, regenerate, and compare whether players understand the choice more quickly.
Result: A focused second version
Create a browser-playable game purchase-flow prototype for local multiplayer groups. Optimize for optional-only purchase design: preserve a complete playable path and avoid selling relief from deliberately created frustration. Apply this audience requirement: show which player owns an item and prevent shared-device purchase confusion. Use one item the player may decline priced directly in Koin with preview, explicit confirm and cancel, insufficient-balance feedback, success, and visible delivery. Do not include subscriptions, revenue reporting, payment-provider UI, or guaranteed outcomes.
Keep the item optional. Show its full price in Koin, visible Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
Complete the core loop without opening the offer, compare paid and free outcomes, and reject any design that turns refusal into a penalty.
Use audience-appropriate language while you prove the free path is complete and the purchase adds bounded value without manufactured friction or progression blocking. Keep quantity, duration, restrictions, and the delivered state explicit.
A browser prototype can validate wording, layout, and state behavior; identity, billing, policy approval, durable entitlements, refunds, and support still need production implementation.
Open the complete prompt in SEELE, adjust the item and Koin price, then generate a playable version you can test.
Open this prompt in WorkspaceRelated-search decision guide
Turn each phrase into a brief: define the desired output, source material, destination, constraints, and reviewer before you generate or build.
Record the input, expected output, format, destination, rights, performance target, and human review as a concrete acceptance test. “Best” depends on the input, editing needs, export target, rights, collaboration, and performance budget. AI-assisted output still needs human review for rights, editability, technical fit, and release readiness.