Tower Defense · Consumable Items guide
Build the tower defense loop first, then test one optional three tower defense recovery tokens at 30 Koin. This guide focuses on quantity, effect, duration, activation rule, and remaining inventory.
Create this game flow
Focused keyword and player case
Offer the three tower defense recovery tokens for 30 Koin only after a safe gameplay pause. Show quantity, effect, duration, activation rule, and remaining inventory before confirmation. Cancel and insufficient balance must preserve progress; success must deliver once and remain correct after reload.
Use the focused consumable items 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.
Keep the first version to one offer. A small scope makes it possible to finish the game loop, purchase choice, delivery, and recovery without maintaining a large shop.
A tower defense browser prototype centered on wave planning, tower roles, and upgrade timing.
A consumable boost preview with a concrete description and direct Koin price.
Place the consumable boost after this loop advances: a tower defense browser prototype centered on wave planning, tower roles, and upgrade timing. Wait for a safe pause. Player progress must not depend on the offer.
Offer-card rules: Keep tower roles readable; State the exact limit. Show the item, benefit, ownership or duration, balance, and full price in Koin. Keep confirm and cancel separate.
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.
Test a free session around a tower defense browser prototype centered on wave planning, tower roles, and upgrade timing. If play becomes incomplete, fix the game before changing the offer.
Show an offer before a wave or after rewards are counted, never while enemies are moving and towers require attention. The player should be able to inspect the lane and dismiss the choice calmly.
Preview range, target rules, duration, or visual-only status with the same symbols used in play. Avoid selling an unclear boost that makes wave balance impossible to understand without purchasing it.
Compare the free path and owned state against the same wave. A player cancellation and reload must preserve placed towers and earned currency, while the delivered item appears only in its promised build or inventory slot.
This tower defense game uses a tower defense browser prototype centered on wave planning, tower roles, and upgrade timing. Review the genre through use the build phase and keep tower roles readable. For a solo 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 solo creator should revise one prompt instruction at a time and compare both playable versions. 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. Prepare a map with a fixed tower layout, earned currency, incoming wave, lives, and upgrade choices. Open the item only during the build phase, cancel, and verify that placement and targeting rules remain intact. Try insufficient Koin without starting the wave or consuming game resources. Complete the valid choice, place or equip the delivered result, and run the same wave used by the free version. Compare range symbols, target priorities, visual clarity, and outcome without hiding balance changes. Then restart or reopen at the next build phase and check that towers, rewards, ownership, and Koin reconcile once. The game should not require the item to repair a wave made unfair on purpose.
Treat the purchase flow as one small feature inside the game, not a separate storefront project. Finish one offer, one confirmation, one delivery path, and the recovery states before considering another item or catalog category.
Write the benefit, Koin amount, duration, ownership rule, and delivery location once. Copy that definition into the offer, confirmation, inventory, and test notes so solo edits do not create contradictory promises.
Generate the game, complete the core activity, decline the offer, trigger insufficient Koin, buy successfully, and reopen the game. Record the first confusing moment instead of changing several screens at once.
Give the link to someone who has not seen the prompt. Ask them to find the price, explain the item, cancel, complete the choice, and locate what was delivered without hints from you.
Choose the single player action that is still confusing and save the current build before editing. Rewrite only the relevant prompt sentence, generate again, and replay the same success and recovery routes in both versions. Keep a short note containing what changed, which version behaved more clearly, and what remains outside your implementation ability. Prefer a finished item with honest boundaries over a broad shop containing unfinished states. When asking someone else to test, give them the link and one goal but no walkthrough; their first hesitation is more useful than another hour spent polishing copy you already understand.
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.
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.
Buying and using are separate actions. Add the item to inventory following the purchase, then reduce its quantity only when the player deliberately activates it.
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.
Make the main activity playable before adding the consumable boost. Players need context to judge whether the item is useful.
Result: A working tower defense foundation
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
Show the exact Koin amount, balance before spending, confirm, cancel, and what ownership means. Reuse the same item definition across the preview, confirmation, and owned state. That keeps the copy and behavior consistent while you work alone.
Result: An understandable decision
Test preview, confirm, insufficient balance, success, decrement quantity only when the player deliberately activates it, and reload. Then test an insufficient balance, cancelling the action, repeated input, interruption, and reload.
Result: A visible, stable result
Run the success path first, followed by cancel, not enough Koin, repeated clicks, and reload. Ask one other person to try it without an explanation.
Result: Solo creator plan
Create a browser-playable tower defense game prototype for a solo creator. Build the core loop around wave planning, tower roles, and upgrade timing. 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.
Keep the item optional. Show its clearly stated Koin cost, available Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
State the exact item, quantity, effect, duration, activation rule, and remaining inventory, and the full 30 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