Idle · Cosmetic Items guide
Build the idle loop first, then test one optional idle 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 idle 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.
Use Koin as a simulated game value for a classroom project. The exercise demonstrates player choice and interface states, not real payment processing.
An idle browser prototype centered on return cadence, visible progress, and low-pressure decisions.
A cosmetic collection preview with a concrete description and direct Koin price.
Place the cosmetic collection after this loop advances: an idle browser prototype centered on return cadence, visible progress, and low-pressure decisions. Wait for a safe pause. Player progress must not depend on the offer.
Offer-card rules: State time effects exactly; Preview it during play. Show the item, benefit, ownership or duration, balance, and clearly stated Koin cost. 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 an idle browser prototype centered on return cadence, visible progress, and low-pressure decisions. If play becomes incomplete, fix the game before changing the offer.
Let players collect and understand offline progress before showing an item. Opening the game to an immediate modal can hide what happened during the absence and turn a routine check-in into pressure.
For a boost, show its duration, activation time, multiplier, and whether it continues while the game is closed. Permanent capacity changes should display the old and new limit side by side.
Reload immediately, return after a short gap, and simulate a longer absence. The item, remaining duration, accumulated resources, and Koin balance should reconcile without duplicate grants or lost progress.
This idle game uses an idle browser prototype centered on return cadence, visible progress, and low-pressure decisions. Review the genre through respect the return moment and state time effects exactly. For a student team, the cosmetic collection should support that loop without becoming mandatory. Review the item through preview it during play and make ownership obvious. A student team can split the demonstration between the game loop, interface explanation, and classroom playtesting. 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. Collect a known amount of offline progress before any offer appears and record generators, capacities, timers, and saved resources. Decline the item, close briefly, and confirm that ordinary accumulation continues. Try insufficient Koin without resetting the return summary. Complete a valid boost or capacity choice and state its activation time, duration, multiplier, and offline behavior. Reopen immediately, after a short simulated gap, and after a longer interval; calculate what should remain each time. Verify one deduction, one ownership or quantity state, and no duplicated offline reward. The free cadence should still feel deliberate rather than slowed to make the purchased relief seem necessary.
Use Koin as simulated game value and explain that the project demonstrates interface states and player choice. Do not collect card details, account credentials, personal information, or money for a classroom prototype.
One teammate can build the game loop, another can own interface wording, and another can run the playtest. Everyone should be able to explain why the item is optional and where it appears after confirmation.
List native billing, identity, durable storage, security, refunds, age rules, accessibility, and platform review as future production concerns. This shows technical understanding without pretending the browser project solves them.
During the demo, cancel once, attempt the item without enough Koin, complete a valid choice, and reopen the game. Explain which results are simulated and what would require real engineering in a released product.
Prepare a short presentation that begins with the playable core activity, then shows a voluntary item preview, decline, insufficient Koin, valid confirmation, delivery, and reopening. Each teammate should explain one design reason and one technical boundary rather than reading the interface aloud. Include a diagram or note showing which values are simulated and which production systems are absent. Ask classmates to identify any pressure language, inaccessible control, unclear ownership rule, or privacy concern. Finish by describing how identity, durable storage, security, refunds, native policy, and testing would change a real implementation, without collecting personal or payment information during the exercise.
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 idle 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, visible Koin balance, confirm, cancel, and what ownership means. Divide the work between the game loop, interface copy, and playtesting. Explain why the item is optional and how the game stays complete without it.
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
Demonstrate confirm, cancel, not enough Koin, success, delivery, and reload. Do not collect payment details, account data, or personal information.
Result: Student team plan
Create a browser-playable idle game prototype for a student game team. Build the core loop around return cadence, visible progress, and low-pressure decisions. 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