Roguelike · Convenience Upgrade guide
Build the roguelike loop first, then test one optional roguelike loadout slot at 50 Koin. This guide focuses on free baseline, exact capacity change, permanence, and restored ownership.
Create this game flow
Focused keyword and player case
Offer the roguelike loadout slot for 50 Koin only after a safe gameplay pause. Show free baseline, exact capacity change, permanence, and restored ownership before confirmation. Cancel and insufficient balance must preserve progress; success must deliver once and remain correct after reload.
Use the focused convenience upgrade 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.
Describe player behavior in ordinary language. Name what appears on screen instead of asking for a generic checkout or monetization system.
A roguelike browser prototype centered on repeat runs, build variety, and loss-resistant value.
A convenience upgrade preview with a concrete description and direct Koin price.
Place the convenience upgrade 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 rules: Explain what survives; Show the before-and-after limit. Show the item, benefit, ownership or duration, balance, and specific Koin amount. Keep confirm and cancel separate.
Test preview, confirm, insufficient balance, success, apply the durable convenience entitlement and show the changed limit, and reload. Show that change inside normal play instead of relying only on a success message.
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.
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.
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.
Buy the item, start a run, lose, and return to the hub. Then repeat through a cancelled choice and a Koin shortage. Only the promised ownership or quantity should carry across attempts.
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 convenience upgrade should support that loop without becoming mandatory. Review the item through show the before-and-after limit and treat the upgrade as durable. A no-code creator should describe observable screens and change only one generation instruction per iteration. The example offer is: A convenience upgrade preview with a concrete description and direct Koin price. This offer emphasizes less friction while preserving the playable free path 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.
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.
If delivery is unclear, revise only the delivery sentence. If cancelling the action loses progress, revise the return-state sentence. Small prompt changes make it easier to understand which instruction improved or damaged the result.
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.
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.
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.
Display the current capacity, preset count, queue size, travel option, or workflow limit beside the precise improvement and show whether ownership is permanent. Play a representative session without it and record whether storage, repetition, waiting, or navigation already feels intentionally designed. If the free experience is cramped or slow only to sell relief, repair that baseline first. Complete the choice, apply the new limit in its normal screen, fill or use the added capacity, and reopen the game. The higher limit should remain visible and should never appear buyable again for the same account state. Check that a cancelled choice preserves existing configuration, insufficient Koin changes nothing, and the upgrade helps without turning ordinary progression into a penalty.
Display the current capacity or workflow and the exact improvement, such as additional inventory slots or another saved preset.
Once buying is complete, apply the new limit visibly and preserve it after reload. Do not make the player buy the same permanent improvement again.
Test the game without the upgrade. If normal play feels deliberately slow, cramped, or repetitive only to sell relief, improve the free experience first.
Make the main activity playable before adding the convenience upgrade. Players need context to judge whether the item is useful.
Result: A working roguelike foundation
A convenience upgrade 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
Show the exact Koin amount, available 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
Test preview, confirm, insufficient balance, success, apply the durable convenience entitlement and show the changed limit, and reload. Then test not enough Koin, cancellation, repeated input, interruption, and reload.
Result: A visible, stable result
Generate the failure states explicitly. If the result only shows success, add too little Koin, cancellation, interruption, and reload to the next prompt.
Result: No-code creator plan
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 convenience upgrade offer containing an inventory expansion with before-and-after capacity, Koin price, and persistent owned state. Price it directly in Koin, require an explicit confirmation, show the balance effect, and apply the durable convenience entitlement and show the changed limit. Do not add subscriptions, external payment checkout, revenue reporting, or guaranteed earnings. Include insufficient-Koin, cancel, success, and reload states.
Keep the item optional. Show its precise Koin price, balance before spending, confirm, cancel, low-balance, success, visible delivery, and reload states.
State the exact item, free baseline, exact capacity change, permanence, and restored ownership, and the full 50 Koin price before the player confirms.
Use a natural planning, customization, or post-session moment. Do not interrupt active controls or make ordinary progression depend on opening the offer.
The free-game progress must remain intact, and a successful purchase must restore the same owned item, content, quantity, or capacity without another charge.
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