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 · Jump-and-Run · Direct Koin item
How a Student Team Can Add a Koin Content Unlock to a Jump-and-Run Game
Build the jump-and-run game first, then add one optional content unlock 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 content unlock around the game
Why it fits jump-and-run
A platformer browser prototype centered on movement mastery, checkpoint rhythm, and level discovery.
What the item offers
A content unlock preview with a concrete description and direct Koin price.
A practical jump-and-run example
Offer moment
Place the content unlock after this loop advances: a platformer browser prototype centered on movement mastery, checkpoint rhythm, and level discovery. Wait for a safe pause. Player progress must not depend on the offer.
Offer card
Offer-card rules: Show movement items in motion; Describe the included content. 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, mark the purchased content as owned and open its entry point, and reload. Show that change inside normal play instead of relying only on a success message.
Free path
Test a free session around a platformer browser prototype centered on movement mastery, checkpoint rhythm, and level discovery. If play becomes incomplete, fix the game before changing the offer.
Design the content unlock in detail
Use a checkpoint, not a jump
Present the offer on a level map or at a stable checkpoint after movement has stopped. Never place confirmation where the same button is used for jumping, dashing, or quickly restarting.
Show movement items in motion
Preview a trail, costume, or convenience effect during a short safe animation. Players need to see silhouette, color contrast, and whether the visual competes with hazards or collectible feedback.
Return to the same checkpoint
After cancel or not enough Koin, restore position, lives, collected objects, and checkpoint progress. Following the purchase, make the item selectable before the next run rather than changing controls without warning.
Rehearse the flow across a checkpoint run
This jump-and-run game uses a platformer browser prototype centered on movement mastery, checkpoint rhythm, and level discovery. Review the genre through use a checkpoint, not a jump and show movement items in motion. For a student team, the content unlock should support that loop without becoming mandatory. Review the item through describe the included content and open a visible entry point. A student team can split the demonstration between the game loop, interface explanation, and classroom playtesting. The example offer is: A content unlock preview with a concrete description and direct Koin price. This offer emphasizes a durable, understandable extension to the core experience before expanding the catalog. Start at a checkpoint with a known life count, collected objects, ability set, and best time. Complete a short movement section before opening the choice on a map or rest screen. Decline, then resume with jump, dash, and camera controls immediately restored. Try insufficient Koin and verify that no life or collectible is consumed. After buying, select the cosmetic, checkpoint aid, or convenience item before the next attempt instead of changing movement unexpectedly. Finish the section, fail once, restart, and reopen the game. Confirm that checkpoint position, earned pickups, control mapping, and purchased ownership reconcile without extra grants or an accidental confirmation from a gameplay button.
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.
Trace the promised content boundary
Name the exact level, chapter, quest, character, route, or mode, describe its approximate scope, and identify the visible entry point that will open after confirmation. Complete the advertised core path without it and verify that essential clues, main-story resolution, required accessibility options, and ordinary progression remain intact. Buy the unlock, start it from the map or menu, leave midway, and find it again after reopening. Confirm that ownership replaces the locked treatment and does not require another Koin deduction. Review age context, rights, moderation, localization, save compatibility, and whether the public description overstates length or replay value. Bonus content may extend a complete game; it should not reveal that the promised game was unexpectedly incomplete.
Describe the included content
Name the level, chapter, quest, character, or mode and explain its approximate scope. Players should understand what opens before they confirm.
Open a visible entry point
Following a successful result, replace the locked state with an owned state and a clear way to start the content. Preserve that entry point after reload.
Keep the promised game complete
A bonus path can extend the experience, but the core ending and advertised main game should not disappear behind an unexpected purchase.
Build it in five steps
1. Finish the jump-and-run loop
Make the main activity playable before adding the content unlock. Players need context to judge whether the item is useful.
Result: A working jump-and-run foundation
2. Write one item definition
A content unlock 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, mark the purchased content as owned and open its entry point, 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, 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 platformer game prototype for a student game team. Build the core loop around movement mastery, checkpoint rhythm, and level discovery. Add one optional content unlock offer containing a bonus chapter card with scope, Koin price, ownership state, and launch action. Price it directly in Koin, require an explicit confirmation, show the balance effect, and mark the purchased content as owned and open its entry point. 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 content unlock supports the existing jump-and-run 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 content unlock.
- 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: hiding the promised core ending behind an unexpected purchase.
- 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 jump-and-run offer contain?
A content unlock 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 jump-and-run 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