Farming · Convenience Upgrade guide
Build the farming loop first, then test one optional farming 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 farming 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 farming browser prototype centered on seasonal routines, crop goals, and homestead expression.
A convenience upgrade preview with a concrete description and direct Koin price.
Place the convenience upgrade after this loop advances: a farming browser prototype centered on seasonal routines, crop goals, and homestead expression. Wait for a safe pause. Player progress must not depend on the offer.
Offer-card rules: Connect value to the season; 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 farming browser prototype centered on seasonal routines, crop goals, and homestead expression. If play becomes incomplete, fix the game before changing the offer.
Use the farmhouse, storage screen, market close, or start of a day after crops and animals are safe. Avoid offers while watering, harvesting, or racing an in-game clock.
Explain whether the item is decorative, adds storage, opens a side area, or supplies a fixed quantity. Do not imply that a seasonal crop or festival reward requires the purchase unless it truly does.
Confirm that fields, planted crops, tools, animal care, and the calendar remain stable. The delivered item should appear in the correct chest, wardrobe, building menu, or map location.
This farming game uses a farming browser prototype centered on seasonal routines, crop goals, and homestead expression. Review the genre through choose a quiet farm moment and connect value to the season. 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. Begin at the farmhouse with a recorded date, weather, crop stages, tool levels, animal care, storage, and festival progress. Open the choice only after urgent chores are safe. Cancel and continue the day without losing time or selected tools, then try insufficient Koin from the same menu. Buy the item, locate it in the chest, wardrobe, building menu, or map, and use it only as described. Sleep to the next day and reopen the game. Check that planted crops advanced normally, animals retained care state, seasonal goals remained available, and the Koin item neither duplicated nor replaced an earned reward. Ordinary farm routines must still feel complete without it.
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 cancellation 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.
After the player buys it, 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 farming 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, visible 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 a Koin shortage, a cancelled choice, repeated input, interruption, and reload.
Result: A visible, stable result
Run the success path first, followed by cancel, an insufficient balance, repeated clicks, and reload. Ask one other person to try it without an explanation.
Result: Solo creator plan
Create a browser-playable farming game prototype for a solo creator. Build the core loop around seasonal routines, crop goals, and homestead expression. 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 specific Koin amount, current Koin balance, 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