Indie studio plan
Give design, UI, and QA one shared item definition. Everyone should use the same benefit, duration, Koin price, and ownership rule.
Indie Studio guide · Horror · Direct Koin item
How an Indie Studio Can Add a Koin Consumable Boost to a Horror Game
Build the horror game first, then add one optional consumable boost that supports the existing play loop. This guide keeps the item understandable from its first preview through delivery and reload.
Create this game flow
Plan the consumable boost around the game
Why it fits horror
A horror browser prototype centered on tension, atmosphere, and non-paywalled narrative access.
What the item offers
A consumable boost preview with a concrete description and direct Koin price.
A practical horror example
Offer moment
Place the consumable boost after this loop advances: a horror browser prototype centered on tension, atmosphere, and non-paywalled narrative access. Wait for a safe pause. Player progress must not depend on the offer.
Offer card
Offer-card rules: Protect narrative access; State the exact limit. Show the item, benefit, ownership or duration, balance, and full price in Koin. Keep confirm and cancel separate.
Successful result
Test preview, confirm, insufficient balance, success, decrement quantity only when the player deliberately activates it, and reload. Show that change inside normal play instead of relying only on a success message.
Free path
Test a free session around a horror browser prototype centered on tension, atmosphere, and non-paywalled narrative access. If play becomes incomplete, fix the game before changing the offer.
Design the consumable boost in detail
Do not monetize the scare
Place the offer in a menu, chapter break, or safe room rather than during pursuit, darkness, or a jump scare. Fear and urgency should come from the game, not from a purchase decision.
Protect narrative access
Cosmetics or clearly labeled bonus scenes can be optional, but essential clues, accessibility aids, and the advertised ending should not be withheld. Explain content warnings and scope before the player confirms.
Test atmosphere and recovery
Cancel, reload, and return from the safe room without changing checkpoints, collected clues, audio state, or difficulty. Delivered visuals must remain readable without undermining contrast needed for navigation.
Check the purchase without weakening tension or access
This horror game uses a horror browser prototype centered on tension, atmosphere, and non-paywalled narrative access. Review the genre through do not monetize the scare and protect narrative access. For a indie studio, the consumable boost should support that loop without becoming mandatory. Review the item through state the exact limit and consume only on activation. An indie studio can divide timing, interface, implementation, and failure testing among named owners. The example offer is: A consumable boost preview with a concrete description and direct Koin price. This offer emphasizes a clearly bounded short-term benefit before expanding the catalog. Reach a safe room after recording the checkpoint, clues, inventory, audio settings, difficulty, and current objective. Present the choice away from pursuit or a jump scare. Cancel and return to the same atmosphere without another immediate prompt, then trigger insufficient Koin with neutral language. Complete a valid cosmetic or clearly bounded bonus-content choice and use its entry point without hiding essential clues, accessibility aids, or the advertised ending. Move into the next scene and reopen the game. Verify that lighting contrast, navigation audio, story continuity, and checkpoint recovery remain reliable, and that fear comes from authored play rather than pressure surrounding the transaction.
Give each discipline one decision
Design owns the offer timing and free path, UI owns readable states, engineering owns state transitions, and QA owns failure coverage. Agree on the same item definition before anyone creates implementation tickets.
Review the playable flow together
Use the prototype in a short team session and walk through decline, insufficient Koin, pending, success, delivery, and reopening. Resolve player-facing disagreement in the build instead of leaving it inside separate documents.
Turn states into production tasks
After the journey is approved, split identity, durable ownership, native billing, security, refunds, policy, localization, accessibility, and analytics into explicit work. The prototype should not be treated as proof that those systems exist.
Keep QA independent of the happy path
Have a tester interrupt confirmation, repeat an input, change screens during delivery, and reload at several points. Compare the result with the agreed item promise and reject duplicate grants or unexplained Koin changes.
Turn the review into an owned team decision
Schedule a short session with design, UI, engineering, and QA using the same playable link and item definition. Assign one person to operate while the others record disagreements about timing, wording, delivery, fairness, and recovery. End with an explicit decision for each disputed state and name the owner of every native implementation task. Update the prototype or source brief before tickets spread outdated assumptions. QA should then write independent scenarios from the agreed player promise, including interruption and duplicate input. This creates a shared reference without mistaking the browser build for a backend, billing integration, revenue forecast, or release approval.
Account for every unit from purchase through use
Write the quantity, effect, duration, activation rule, stack limit, expiration behavior, and moment of consumption before presenting a Koin amount. A successful purchase should add inventory first; it must not activate merely because the player confirmed. Use one unit, interrupt the effect, finish a session, and reopen the game while recording remaining quantity and time. Repeat input during buying and activation to catch double subtraction. Compare ordinary progress, retry access, and failure recovery without the boost, then remove any design that makes the free route intentionally unreasonable. The player should always know how many uses remain, when an effect ends, and whether unused quantity survives another session.
State the exact limit
Show quantity, duration, activation rule, and the point when the consumable is removed. Players should know whether they are buying one use, several uses, or a timed effect.
Consume only on activation
Buying and using are separate actions. Add the item to inventory once buying is complete, then reduce its quantity only when the player deliberately activates it.
Avoid failure pressure
Do not present the boost immediately after every loss or make ordinary progress unreasonable without it. The free retry and recovery path should remain understandable.
Build it in five steps
1. Finish the horror loop
Make the main activity playable before adding the consumable boost. Players need context to judge whether the item is useful.
Result: A working horror foundation
2. Write one item definition
A consumable boost preview with a concrete description and direct Koin price. Keep the same wording in the preview, confirmation, and delivered state.
Result: A consistent player promise
3. Generate the purchase choice
Show the exact Koin amount, available Koin balance, confirm, cancel, and what ownership means. Design chooses the offer moment, UI makes every state distinct, and QA tests transitions and recovery. Use the playable prototype during the team review.
Result: An understandable decision
4. Deliver and recover
Test preview, confirm, insufficient balance, success, decrement quantity only when the player deliberately activates it, and reload. Then test a Koin shortage, a cancelled choice, repeated input, interruption, and reload.
Result: A visible, stable result
5. Test as a indie studio
Write test cases for an insufficient balance, a cancelled choice, delayed delivery, repeated input, and reload. Create production tickets only after the player journey is agreed.
Result: Indie studio plan
Generate it in SEELE
Prompt 1
Create a browser-playable horror game prototype for a small indie studio. Build the core loop around tension, atmosphere, and non-paywalled narrative access. Add one optional consumable boost offer containing a single-use boost with duration, quantity, Koin price, and activation feedback. Price it directly in Koin, require an explicit confirmation, show the balance effect, and decrement quantity only when the player deliberately activates it. Do not add subscriptions, external payment checkout, revenue reporting, or guaranteed earnings. Include insufficient-Koin, cancel, success, and reload states.
Prompt 2
Keep the item optional. Show its precise Koin price, balance before spending, confirm, cancel, low-balance, success, visible delivery, and reload states.
Indie Studio playtest checklist
- The consumable boost supports the existing horror loop.
- The item benefit and ownership rule are clear ahead of confirmation.
- The full price in Koin and current Koin balance appear together.
- A cancelled choice returns to play without loss or pressure.
- Success visibly delivers the confirmed consumable boost.
- Write test cases for an insufficient balance, a cancelled choice, delayed delivery, repeated input, and reload. Create production tickets only after the player journey is agreed.
Before you publish
- Avoid this design problem: pressure loops that make failure feel like a forced purchase.
- 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 playable browser prototype. 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
What should this horror offer contain?
A consumable boost preview with a concrete description and direct Koin price. Start with one item and one price.
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. The browser prototype still needs native billing, persistence, security, refunds, and platform approval.
Build this horror purchase flow
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