Local Multiplayer · Transparent Koin Pricing guide
Design one offer for local multiplayer with a single acceptance goal: show the exact Koin amount beside the named item with quantity, duration, permanence, restrictions, and the resulting balance. Keep the exact Koin price and a safe refusal path visible.
Create this game flow
Focused keyword and player case
Present “3 shield charges · 10 seconds each · 30 Koin” together with the current balance and post-purchase balance before confirmation. Do not rely on a vague bundle label. For local multiplayer, Ask a reviewer to repeat the full price, quantity, duration, and owned result before pressing Confirm; revise any field they cannot recover from the screen.
Use the focused transparent koin pricing 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.
Show the item, exact Koin amount, balance effect, duration, and ownership result prior to confirming.
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.
Give a new player the offer without explanation and ask them to name the selected item, full Koin amount, available balance, expected balance afterward, quantity or duration, and ownership rule. Let them decline, then repeat with insufficient Koin and a successful choice. Review every place the value appears and remove crossed-out amounts, vague premium labels, unsupported real-currency comparisons, or urgency that distracts from the final cost. The wording on the preview, confirmation, success message, and owned view must describe the same thing. Reopen the game and verify that the balance and ownership shown to the player still match the one transaction they approved.
Place the exact Koin amount beside the balance before spending and show the expected remaining balance ahead of confirmation. For local multiplayer groups, the experience must show which player owns an item and prevent shared-device purchase confusion.
State whether the item is permanent, consumed on use, limited by quantity, or active for a fixed time. For local multiplayer groups, the experience must show which player owns an item and prevent shared-device purchase confusion.
Avoid fake urgency, crossed-out prices, unsupported currency comparisons, and labels that hide the final Koin amount. 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
Show the item, exact Koin amount, balance effect, duration, and ownership result before the player confirms. 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 transparent Koin pricing: show the item, exact Koin amount, balance effect, duration, and ownership result before the player confirms. Apply this audience requirement: show which player owns an item and prevent shared-device purchase confusion. Use one non-required item 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.
Ask a reviewer to repeat the full price, quantity, duration, and owned result before pressing Confirm; revise any field they cannot recover from the screen.
Use audience-appropriate language while you show the exact Koin amount beside the named item with quantity, duration, permanence, restrictions, and the resulting balance. 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 Workspace