Cozy · Convenience Upgrade guide
Build the cozy loop first, then test one optional cozy loadout slot at 50 Koin. This guide focuses on free baseline, exact capacity change, permanence, and restored ownership.
Create this game flow
Focused keyword and player case
Offer the cozy loadout slot for 50 Koin only after a safe gameplay pause. Show free baseline, exact capacity change, permanence, and restored ownership before confirmation. Cancel and insufficient balance must preserve progress; success must deliver once and remain correct after reload.
Use the focused convenience upgrade 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 cozy browser prototype centered on gentle pacing, decoration, and low-stress collection.
A convenience upgrade preview with a concrete description and direct Koin price.
Place the convenience upgrade after this loop advances: a cozy browser prototype centered on gentle pacing, decoration, and low-stress collection. Wait for a safe pause. Player progress must not depend on the offer.
Offer-card rules: Preview in the player space; Show the before-and-after limit. Show the item, benefit, ownership or duration, balance, and clearly stated Koin cost. Keep confirm and cancel separate.
Test preview, confirm, insufficient balance, success, apply the durable convenience entitlement and show the changed limit, and reload. Show that change inside normal play instead of relying only on a success message.
Test a free session around a cozy browser prototype centered on gentle pacing, decoration, and low-stress collection. If play becomes incomplete, fix the game before changing the offer.
Use an optional catalog, decorating menu, or natural collection milestone. Avoid countdowns, repeated popups, loss language, and visual urgency that conflicts with a low-stress play rhythm.
Show furniture, colors, outfits, or companion accessories inside the room or scene where they will be used. Include scale and placement limits so the purchase is not based on a tiny thumbnail.
Cancel and continue decorating, collecting, or talking without another prompt. Not enough Koin should explain the shortage quietly, while successful delivery places the item in an obvious collection category.
This cozy game uses a cozy browser prototype centered on gentle pacing, decoration, and low-stress collection. Review the genre through keep the invitation gentle and preview in the player space. For a solo creator, the convenience upgrade should support that loop without becoming mandatory. Review the item through show the before-and-after limit and treat the upgrade as durable. A solo creator should revise one prompt instruction at a time and compare both playable versions. The example offer is: A convenience upgrade preview with a concrete description and direct Koin price. This offer emphasizes less friction while preserving the playable free path before expanding the catalog. Set up a calm room, collection, conversation, or decorating task and let the player make progress before visiting the optional catalog. Cancel once and watch whether the game immediately asks again, changes the tone, or blocks the activity. Try insufficient Koin with quiet language and a clear return. Complete a valid choice, preview scale and placement in the real space, and store the result in an obvious category. Continue collecting or talking, then reopen the build and find the item again. Review animation, color, reading comfort, and shared-screen privacy. The entire sequence should preserve a gentle pace and avoid countdowns, guilt, loss language, or manufactured scarcity.
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.
Display the current capacity, preset count, queue size, travel option, or workflow limit beside the precise improvement and show whether ownership is permanent. Play a representative session without it and record whether storage, repetition, waiting, or navigation already feels intentionally designed. If the free experience is cramped or slow only to sell relief, repair that baseline first. Complete the choice, apply the new limit in its normal screen, fill or use the added capacity, and reopen the game. The higher limit should remain visible and should never appear buyable again for the same account state. Check that a cancelled choice preserves existing configuration, insufficient Koin changes nothing, and the upgrade helps without turning ordinary progression into a penalty.
Display the current capacity or workflow and the exact improvement, such as additional inventory slots or another saved preset.
Once buying is complete, apply the new limit visibly and preserve it after reload. Do not make the player buy the same permanent improvement again.
Test the game without the upgrade. If normal play feels deliberately slow, cramped, or repetitive only to sell relief, improve the free experience first.
Make the main activity playable before adding the convenience upgrade. Players need context to judge whether the item is useful.
Result: A working cozy foundation
A convenience upgrade 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, available Koin balance, 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, apply the durable convenience entitlement and show the changed limit, and reload. Then test not enough Koin, cancellation, repeated input, interruption, and reload.
Result: A visible, stable result
Run the success path first, followed by cancel, too little Koin, repeated clicks, and reload. Ask one other person to try it without an explanation.
Result: Solo creator plan
Create a browser-playable cozy game prototype for a solo creator. Build the core loop around gentle pacing, decoration, and low-stress collection. Add one optional convenience upgrade offer containing an inventory expansion with before-and-after capacity, Koin price, and persistent owned state. Price it directly in Koin, require an explicit confirmation, show the balance effect, and apply the durable convenience entitlement and show the changed limit. 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 precise Koin price, balance before spending, confirm, cancel, low-balance, success, visible delivery, and reload states.
State the exact item, free baseline, exact capacity change, permanence, and restored ownership, and the full 50 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