Student team plan
Use Koin as a simulated game value for a classroom project. The exercise demonstrates player choice and interface states, not real payment processing.
Student Team guide · Track Competition · Direct Koin item
How a Student Team Can Add a Koin Cosmetic Collection to a Track Competition Game
Build the track competition game first, then add one optional cosmetic collection that supports the existing play loop. This guide keeps the item understandable from its first preview through delivery and reload.
Create this game flow
Plan the cosmetic collection around the game
Why it fits track competition
A racing browser prototype centered on vehicle identity, track progression, and fair competitive readability.
What the item offers
A cosmetic collection preview with a concrete description and direct Koin price.
A practical track competition example
Offer moment
Place the cosmetic collection after this loop advances: a racing browser prototype centered on vehicle identity, track progression, and fair competitive readability. Wait for a safe pause. Player progress must not depend on the offer.
Offer card
Offer-card rules: Separate style from performance; Preview it during play. Show the item, benefit, ownership or duration, balance, and full price in Koin. Keep confirm and cancel separate.
Successful result
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.
Free path
Test a free session around a racing browser prototype centered on vehicle identity, track progression, and fair competitive readability. If play becomes incomplete, fix the game before changing the offer.
Design the cosmetic collection in detail
Decide between races
Put the choice in the garage, event map, or results screen. A purchase layer should never obscure steering, timing, lap position, or the countdown that begins a competitive race.
Separate style from performance
If an item changes only paint, decals, trails, or celebration effects, say so. When a benefit affects handling or progression, show the exact rule and test whether non-buyers can compete fairly.
Check garage ownership
Deliver the confirmed item to the selected vehicle or collection, then revisit it after a race and reload. Cancellation must preserve tuning, event selection, and earned rewards without changing the grid position.
Compare the garage, race, and return states
This track competition game uses a racing browser prototype centered on vehicle identity, track progression, and fair competitive readability. Review the genre through decide between races and separate style from performance. 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. Select a vehicle, record its tuning, event, grid, earned rewards, and visual setup, then complete a short race before entering the garage offer. Cancel and make sure the same event and tuning remain selected. Trigger insufficient Koin and confirm that the countdown or next-race action cannot spend anything. Buy the item from a deliberate garage confirmation, apply it to the intended vehicle, and run the same track again. Separate cosmetic changes from handling or progression in the comparison. After results and a fresh load, verify one owned item, unchanged earned rewards, stable season progress, and a free competitor path that remains readable and fair.
Frame it as a design exercise
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.
Divide the demonstration clearly
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.
Document what the prototype omits
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.
Present both success and failure
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.
Explain the system during a live demonstration
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.
Audit the cosmetic from preview to ownership
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.
Preview it during play
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.
Make ownership obvious
After the player buys it, 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.
Protect competitive clarity
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.
Build it in five steps
1. Finish the track competition loop
Make the main activity playable before adding the cosmetic collection. Players need context to judge whether the item is useful.
Result: A working track competition foundation
2. Write one item definition
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
3. Generate the purchase choice
Show the exact Koin amount, balance before spending, 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
4. Deliver and recover
Test preview, confirm, insufficient balance, success, equip the owned cosmetic and keep it visible in inventory, and reload. Then test not enough Koin, cancellation, repeated input, interruption, and reload.
Result: A visible, stable result
5. Test as a student team
Demonstrate confirm, cancel, an insufficient balance, success, delivery, and reload. Do not collect payment details, account data, or personal information.
Result: Student team plan
Generate it in SEELE
Prompt 1
Create a browser-playable racing game prototype for a student game team. Build the core loop around vehicle identity, track progression, and fair competitive readability. 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.
Prompt 2
Keep the item optional. Show its full price in Koin, Koin balance now, confirm, cancel, low-balance, success, visible delivery, and reload states.
Student Team playtest checklist
- The cosmetic collection supports the existing track competition loop.
- The item benefit and ownership rule are clear before the player confirms.
- The precise Koin price and available Koin balance appear together.
- A player cancellation returns to play without loss or pressure.
- Success visibly delivers the confirmed cosmetic collection.
- Demonstrate confirm, cancel, an insufficient balance, success, delivery, and reload. Do not collect payment details, account data, or personal information.
Before you publish
- Avoid this design problem: players mistaking cosmetic rarity for a gameplay advantage.
- This guide uses a direct Koin transaction for one optional game item. It does not create a subscription or recurring charge.
- The result is a prototype that runs in a browser. Native billing, identity, durable entitlements, security, refunds, and store approval need separate implementation.
- SEELE does not provide payment analytics, tax tools, payout reports, or guaranteed revenue through this flow.
Frequently asked questions
What should this track competition offer contain?
A cosmetic collection preview with a concrete description and direct Koin price. Start with one item and one price.
Is this a subscription?
No. The player spends Koin directly on one named item or unlock.
What happens if the player cancels?
Return to the same game state without spending Koin or delivering the item.
What if the Koin balance is too low?
Explain the shortage, preserve progress, and do not deliver the item.
Does this include payment or revenue reports?
No. It covers the player-facing purchase experience, not financial reporting.
Is the prototype ready for a native store?
No. The browser prototype still needs native billing, persistence, security, refunds, and platform approval.
Build this track competition purchase flow
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