Farming · Cosmetic Items guide
Build the farming loop first, then test one optional farming identity pack at 40 Koin. This guide focuses on appearance, permanence, ownership, and equip state.
Create this game flow
Focused keyword and player case
Offer the farming identity pack for 40 Koin only after a safe gameplay pause. Show appearance, permanence, ownership, and equip state before confirmation. Cancel and insufficient balance must preserve progress; success must deliver once and remain correct after reload.
Use the focused cosmetic items 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.
Give design, UI, and QA one shared item definition. Everyone should use the same benefit, duration, Koin price, and ownership rule.
A farming browser prototype centered on seasonal routines, crop goals, and homestead expression.
A cosmetic collection preview with a concrete description and direct Koin price.
Place the cosmetic collection 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; Preview it during play. Show the item, benefit, ownership or duration, balance, and specific Koin amount. Keep confirm and cancel separate.
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.
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 indie studio, the cosmetic collection should support that loop without becoming mandatory. Review the item through preview it during play and make ownership obvious. An indie studio can divide timing, interface, implementation, and failure testing among named owners. 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. 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.
Design owns the offer timing and free path, UI owns readable states, engineering owns state transitions, and QA owns failure coverage. Agree on the same item definition before anyone creates implementation tickets.
Use the prototype in a short team session and walk through decline, insufficient Koin, pending, success, delivery, and reopening. Resolve player-facing disagreement in the build instead of leaving it inside separate documents.
After the journey is approved, split identity, durable ownership, native billing, security, refunds, policy, localization, accessibility, and analytics into explicit work. The prototype should not be treated as proof that those systems exist.
Have a tester interrupt confirmation, repeat an input, change screens during delivery, and reload at several points. Compare the result with the agreed item promise and reject duplicate grants or unexplained Koin changes.
Schedule a short session with design, UI, engineering, and QA using the same playable link and item definition. Assign one person to operate while the others record disagreements about timing, wording, delivery, fairness, and recovery. End with an explicit decision for each disputed state and name the owner of every native implementation task. Update the prototype or source brief before tickets spread outdated assumptions. QA should then write independent scenarios from the agreed player promise, including interruption and duplicate input. This creates a shared reference without mistaking the browser build for a backend, billing integration, revenue forecast, or release approval.
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.
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.
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.
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.
Make the main activity playable before adding the cosmetic collection. Players need context to judge whether the item is useful.
Result: A working farming foundation
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
Show the exact Koin amount, current Koin balance, confirm, cancel, and what ownership means. Design chooses the offer moment, UI makes every state distinct, and QA tests transitions and recovery. Use the playable prototype during the team review.
Result: An understandable decision
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
Write test cases for not enough Koin, a player cancellation, delayed delivery, repeated input, and reload. Create production tickets only after the player journey is agreed.
Result: Indie studio plan
Create a browser-playable farming game prototype for a small indie studio. Build the core loop around seasonal routines, crop goals, and homestead expression. 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.
Keep the item optional. Show its full price in Koin, visible Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
State the exact item, appearance, permanence, ownership, and equip state, and the full 40 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