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 · Cooking · Direct Koin item
How a Student Team Can Add a Koin Cosmetic Collection to a Cooking Game
Build the cooking 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 cooking
A cooking browser prototype centered on recipe mastery, kitchen upgrades, and playful presentation.
What the item offers
A cosmetic collection preview with a concrete description and direct Koin price.
A practical cooking example
Offer moment
Place the cosmetic collection after this loop advances: a cooking browser prototype centered on recipe mastery, kitchen upgrades, and playful presentation. Wait for a safe pause. Player progress must not depend on the offer.
Offer card
Offer-card rules: Show the kitchen change; Preview it during play. Show the item, benefit, ownership or duration, balance, and clearly stated Koin cost. 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 cooking browser prototype centered on recipe mastery, kitchen upgrades, and playful presentation. If play becomes incomplete, fix the game before changing the offer.
Design the cosmetic collection in detail
Offer after service
Use the recipe book, kitchen planning screen, or completed shift rather than interrupting chopping, timing, or a customer order. The player should finish the current task before evaluating an item.
Show the kitchen change
Preview a utensil skin, station capacity, recipe chapter, or fixed ingredient quantity in context. Explain whether it changes appearance, available space, or the dishes that can be prepared.
Reopen the same recipe
Following the purchase and reload, confirm the item appears in the pantry, equipment menu, or recipe list. A player cancellation and too little Koin should preserve ingredients, active upgrades, ratings, and order progress.
Trace the item from planning through service
This cooking game uses a cooking browser prototype centered on recipe mastery, kitchen upgrades, and playful presentation. Review the genre through offer after service and show the kitchen change. 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. Choose a recipe and record ingredients, station upgrades, customer orders, rating, timer, and pantry quantities. Open the choice after a completed shift or from kitchen planning, then cancel without consuming food or changing the selected menu. Try insufficient Koin from the same stable state. Complete a valid utensil style, station capacity, recipe chapter, or fixed ingredient quantity and locate it where preparation actually occurs. Run one service, return to the recipe book, and reopen the game. Verify that ingredients reconcile, order progress and ratings remain earned, the delivered scope matches the card, and normal mastery is not made tedious simply to promote a convenience purchase.
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
Following the purchase, 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 cooking loop
Make the main activity playable before adding the cosmetic collection. Players need context to judge whether the item is useful.
Result: A working cooking 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, current 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
4. Deliver and recover
Test preview, confirm, insufficient balance, success, equip the owned cosmetic and keep it visible in inventory, and reload. Then test a Koin shortage, a cancelled choice, repeated input, interruption, and reload.
Result: A visible, stable result
5. Test as a student team
Demonstrate confirm, cancel, too little Koin, 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 cooking game prototype for a student game team. Build the core loop around recipe mastery, kitchen upgrades, and playful presentation. 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 precise Koin price, balance before spending, confirm, cancel, low-balance, success, visible delivery, and reload states.
Student Team playtest checklist
- The cosmetic collection supports the existing cooking loop.
- The item benefit and ownership rule are clear ahead of confirmation.
- The full price in Koin and current Koin balance appear together.
- A cancelled choice returns to play without loss or pressure.
- Success visibly delivers the confirmed cosmetic collection.
- Demonstrate confirm, cancel, too little Koin, 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 playable browser prototype. 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 cooking 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 cooking 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