No-code creator plan
Describe player behavior in ordinary language. Name what appears on screen instead of asking for a generic checkout or monetization system.
No-Code Creator guide · Roguelike · Direct Koin item
How a No-Code Creator Can Add a Koin Consumable Boost to a Roguelike Game
Build the roguelike 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 roguelike
A roguelike browser prototype centered on repeat runs, build variety, and loss-resistant value.
What the item offers
A consumable boost preview with a concrete description and direct Koin price.
A practical roguelike example
Offer moment
Place the consumable boost after this loop advances: a roguelike browser prototype centered on repeat runs, build variety, and loss-resistant value. Wait for a safe pause. Player progress must not depend on the offer.
Offer card
Offer-card rules: Explain what survives; State the exact limit. Show the item, benefit, ownership or duration, balance, and specific Koin amount. 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 roguelike browser prototype centered on repeat runs, build variety, and loss-resistant value. If play becomes incomplete, fix the game before changing the offer.
Design the consumable boost in detail
Offer between runs
Use the hub, results screen, or loadout selection after a run has ended. A purchase prompt should not interrupt a room, obscure an attack, or exploit the few seconds immediately before a loss.
Explain what survives
State whether the item lasts one run, becomes a permanent unlock, or enters a future reward pool. Players should know what remains after defeat before they spend Koin.
Repeat the death-and-reload test
Buy the item, start a run, lose, and return to the hub. Then repeat through cancellation and not enough Koin. Only the promised ownership or quantity should carry across attempts.
Follow ownership through a loss and another run
This roguelike game uses a roguelike browser prototype centered on repeat runs, build variety, and loss-resistant value. Review the genre through offer between runs and explain what survives. For a no-code creator, the consumable boost should support that loop without becoming mandatory. Review the item through state the exact limit and consume only on activation. A no-code creator should describe observable screens and change only one generation instruction per iteration. 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. Begin in the hub with a recorded unlock pool, loadout, currency, run count, and difficulty. Open the choice between attempts, cancel, and start a run with the same seed rules and equipment. Try insufficient Koin without consuming the next attempt. Complete a valid choice only after stating whether it lasts one run, remains permanent, or enters a future reward pool. Use it, deliberately lose, and return to the hub. Start another run and reopen the game to compare persistence. Confirm one deduction, the promised surviving state, unchanged earned progression, and no offer timed to exploit the instant before or after defeat.
Describe screens, not infrastructure
Ask for the item preview, price, balance, buttons, pending state, delivered state, and return path in ordinary language. Avoid broad requests for a monetization backend that do not tell the generator what players should see.
Change one instruction per version
If delivery is unclear, revise only the delivery sentence. If cancellation loses progress, revise the return-state sentence. Small prompt changes make it easier to understand which instruction improved or damaged the result.
Generate failure paths deliberately
A first result may demonstrate only success. Add separate directions for insufficient Koin, cancel, repeated input, interruption, and reopening, then operate each path rather than assuming a labeled button works.
Save a copy before refining
Keep the last playable version beside the new generation. Compare the same player actions in both builds, preserve the stronger behavior, and avoid replacing a working core game merely to alter purchase wording.
Debug the result through observable behavior
When a generated build misses the intent, describe the exact action and outcome instead of asking for a better purchase system. For example, say that choosing cancel must close the panel and resume at the same checkpoint, or that success must add one named item to a visible inventory slot. Keep the previous generation open, change one instruction, and compare identical routes. If a control is only decorative, state which state change it needs to produce. Continue until preview, decline, insufficient Koin, pending, delivery, and reopening can all be operated. Anything requiring identity, native billing, security, or refunds belongs in a separate production plan.
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 after the player buys it, 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 roguelike loop
Make the main activity playable before adding the consumable boost. Players need context to judge whether the item is useful.
Result: A working roguelike 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, current Koin balance, confirm, cancel, and what ownership means. Prompt for the preview, price, balance, confirm, cancel, success, and owned state separately. Change one instruction at a time between generations.
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 not enough Koin, cancellation, repeated input, interruption, and reload.
Result: A visible, stable result
5. Test as a no-code creator
Generate the failure states explicitly. If the result only shows success, add an insufficient balance, a cancelled choice, interruption, and reload to the next prompt.
Result: No-code creator plan
Generate it in SEELE
Prompt 1
Create a browser-playable roguelike game prototype for a no-code creator. Build the core loop around repeat runs, build variety, and loss-resistant value. 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 full price in Koin, Koin balance now, confirm, cancel, low-balance, success, visible delivery, and reload states.
No-Code Creator playtest checklist
- The consumable boost supports the existing roguelike loop.
- The item benefit and ownership rule are clear before the player confirms.
- The precise Koin price and available Koin balance appear together.
- A player cancellation returns to play without loss or pressure.
- Success visibly delivers the confirmed consumable boost.
- Generate the failure states explicitly. If the result only shows success, add an insufficient balance, a cancelled choice, interruption, and reload to the next prompt.
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 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
What should this roguelike 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 roguelike 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