Strategy · Consumable Items guide
Build the strategy loop first, then test one optional three strategy 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 strategy 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.
Describe player behavior in ordinary language. Name what appears on screen instead of asking for a generic checkout or monetization system.
A strategy browser prototype centered on planning depth, unit identity, and legible tactical tradeoffs.
A consumable boost preview with a concrete description and direct Koin price.
Place the consumable boost after this loop advances: a strategy browser prototype centered on planning depth, unit identity, and legible tactical tradeoffs. Wait for a safe pause. Player progress must not depend on the offer.
Offer-card rules: Explain rule impact; State the exact limit. Show the item, benefit, ownership or duration, balance, and clearly stated Koin cost. 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 strategy browser prototype centered on planning depth, unit identity, and legible tactical tradeoffs. If play becomes incomplete, fix the game before changing the offer.
Use a campaign map, deployment screen, or completed turn where the player can compare options without a timer. Do not interrupt a tactical command or hide information needed for the current decision.
State whether the item changes appearance, unlocks a scenario, adds a reusable option, or grants a limited resource. Show affected units and constraints instead of using a vague strategic advantage label.
Test the purchase, cancelling the action, and low-balance routes from one saved planning state. Unit positions, resources, objectives, and queued actions should remain identical except for the item the player confirmed.
This tactical planning game uses a strategy browser prototype centered on planning depth, unit identity, and legible tactical tradeoffs. Review the genre through pause at a planning boundary and explain rule impact. 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. Save a planning screen with known units, resources, objectives, queued actions, and map information. Inspect the item away from an active timer, cancel it, and confirm that the plan remains identical. Attempt it with insufficient Koin without advancing the turn or changing deployment. Complete a valid choice and place the resulting scenario, cosmetic, resource quantity, or reusable option exactly where described. Play one turn, undo or reload where the game allows, and return to the same planning layer. Compare the saved position and ownership record so that the confirmed benefit is the only difference. This test exposes hidden grants, altered tactical information, and paid relief from artificial constraints.
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 cancellation 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.
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 after the player buys it, 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 tactical planning 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, 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
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
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
Create a browser-playable strategy game prototype for a no-code creator. Build the core loop around planning depth, unit identity, and legible tactical tradeoffs. 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 full price in Koin, visible 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