Audience need
The experience must show which player owns an item and prevent shared-device purchase confusion.
Local Multiplayer Groups · Player-first Koin purchase UX
Koin Optional-Only Purchase Design for Local Multiplayer Groups
Design one optional Koin item around the real needs of local multiplayer groups. This guide applies optional-only purchase design to the offer, confirmation, a player cancellation, recovery, and delivered result.
Create this game flow
Start with what local multiplayer groups need
Design principle
Preserve a complete playable path and avoid selling relief from deliberately created frustration.
Small first scope
Use one item and one Koin price so players can evaluate the complete choice without navigating a large shop.
Optional-Only Purchase Design in practice
Offer moment
Choose a calm point where local multiplayer groups understand the game context and can decline without interrupting active play.
Offer card
Show the item, benefit, duration or quantity, full price in Koin, Koin balance now, confirm, and cancel in plain language.
Safe recovery
After cancellation or not enough Koin, preserve progress and return local multiplayer groups to an understandable game state.
Visible delivery
Following a successful result, show ownership, equipped state, unlocked content, or remaining quantity where the item will be used.
Apply optional-only purchase design throughout the flow
Make ownership obvious on a shared device
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.
Prove that declining leaves a complete game
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.
Finish the free path first
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.
Offer an easy decline
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.
Do not sell relief from frustration
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.
Design the flow in five steps
1. Start with the audience requirement
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
2. Apply optional-only purchase design
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
3. Define one non-required item
Name the benefit, duration or quantity, ownership rule, clearly stated Koin cost, and delivered result.
Result: An understandable offer
4. Playtest with local multiplayer groups
Try confirmation, cancellation, not enough Koin, repeated input, interruption, delivery, and reload without coaching.
Result: Audience-specific feedback
5. Revise the unclear moment
Change one prompt instruction, regenerate, and compare whether players understand the choice more quickly.
Result: A focused second version
Generate it in SEELE
Prompt 1
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.
Prompt 2
Keep the item optional. Show its full price in Koin, Koin balance now, confirm, cancel, low-balance, success, visible delivery, and reload states.
Playtest with local multiplayer groups
- The flow directly responds to this need: show which player owns an item and prevent shared-device purchase confusion.
- Optional-Only Purchase Design changes the interface behavior, not only the heading.
- The item and precise Koin price appear ahead of confirmation.
- Declining or lacking Koin does not erase progress or create pressure.
- The delivered item matches the confirmed promise.
- Someone from this audience can explain the choice without coaching.
Before this flow goes live
- The design must continue to show which player owns an item and prevent shared-device purchase confusion.
- This guide uses a direct Koin transaction for one optional game item. It does not create a subscription or recurring charge.
- The result is a prototype that runs in a browser. Native billing, identity, durable entitlements, security, refunds, and store approval need separate implementation.
- SEELE does not provide payment analytics, tax tools, payout reports, or guaranteed revenue through this flow.
Frequently asked questions
Why does optional-only purchase design matter for local multiplayer groups?
It makes the choice easier to understand while respecting this audience's needs.
Is this a subscription?
No. The player spends Koin directly on one named item or unlock.
What happens if the player cancels?
Return to the same game state without spending Koin or delivering the item.
What if the Koin balance is too low?
Explain the shortage, preserve progress, and do not deliver the item.
Does this include payment or revenue reports?
No. It covers the player-facing purchase experience, not financial reporting.
Is the prototype ready for a native store?
No. Identity, persistence, security, refunds, native APIs, policy, and accessibility still need production work.
Build a optional-only purchase design prototype
Open the complete prompt in SEELE, adjust the item and Koin price, then generate a playable version you can test.
Open this prompt in Workspace