Strategy · Cosmetic Items guide
Build the strategy loop first, then test one optional strategy identity pack at 40 Koin. This guide focuses on appearance, permanence, ownership, and equip state.
Create this game flow
Focused keyword and player case
Offer the strategy identity pack for 40 Koin only after a safe gameplay pause. Show appearance, permanence, ownership, and equip state before confirmation. Cancel and insufficient balance must preserve progress; success must deliver once and remain correct after reload.
Use the focused cosmetic 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 strategy browser prototype centered on planning depth, unit identity, and legible tactical tradeoffs.
A cosmetic collection preview with a concrete description and direct Koin price.
Place the cosmetic collection 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; Preview it during play. Show the item, benefit, ownership or duration, balance, and specific Koin amount. Keep confirm and cancel separate.
Test preview, confirm, insufficient balance, success, equip the owned cosmetic and keep it visible in inventory, 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, a player cancellation, 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 solo creator, the cosmetic collection should support that loop without becoming mandatory. Review the item through preview it during play and make ownership obvious. A solo creator should revise one prompt instruction at a time and compare both playable versions. The example offer is: A cosmetic collection preview with a concrete description and direct Koin price. This offer emphasizes expression without changing competitive power 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.
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.
Place the visual on the actual character, vehicle, card, room, trail, or game object and compare it with the thumbnail at normal play scale. Check front, back, motion, color contrast, overlapping equipment, and any platform-specific crop. State that it is visual only when no statistic, rule, or outcome changes. Confirm the exact piece or bundle, then replace buy with owned or equip and file it under an obvious collection category. Switch to another cosmetic, reopen the game, and select it again without another deduction. Also inspect multiplayer, streaming, and accessibility contexts so the design does not hide hazards, impersonate earned rarity, expose private information, or suggest competitive power that the item never provides.
Show the cosmetic on the character, vehicle, card, or game space where players will actually see it. A thumbnail alone can hide scale, color, or animation differences.
Once buying is complete, change the action from buy to owned or equip. Keep the cosmetic in the relevant collection after reload so players know where to use it.
Describe the item as visual only when it changes no stats or outcomes. Avoid rarity language that suggests an advantage the cosmetic does not provide.
Make the main activity playable before adding the cosmetic collection. Players need context to judge whether the item is useful.
Result: A working tactical planning foundation
A cosmetic collection 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, equip the owned cosmetic and keep it visible in inventory, 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 strategy game prototype for a solo creator. Build the core loop around planning depth, unit identity, and legible tactical tradeoffs. Add one optional cosmetic collection offer containing a three-item style set with preview, Koin price, confirmation, and equip state. Price it directly in Koin, require an explicit confirmation, show the balance effect, and equip the owned cosmetic and keep it visible in inventory. 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, appearance, permanence, ownership, and equip state, and the full 40 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