Puzzle · Cosmetic Items guide
Build the puzzle loop first, then test one optional puzzle 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 puzzle 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.
Describe player behavior in ordinary language. Name what appears on screen instead of asking for a generic checkout or monetization system.
A puzzle browser prototype centered on readable rules, hint pacing, and satisfying solution feedback.
A cosmetic collection preview with a concrete description and direct Koin price.
Place the cosmetic collection after this loop advances: a puzzle browser prototype centered on readable rules, hint pacing, and satisfying solution feedback. Wait for a safe pause. Player progress must not depend on the offer.
Offer-card rules: Describe hint depth precisely; Preview it during play. Show the item, benefit, ownership or duration, balance, and precise Koin price. 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 puzzle browser prototype centered on readable rules, hint pacing, and satisfying solution feedback. If play becomes incomplete, fix the game before changing the offer.
Introduce the item only after the player has solved enough examples to understand the puzzle language. A hint offer shown before the first genuine attempt turns learning into a purchase decision.
Say whether the item reveals a small clue, highlights a legal move, or shows the full solution. Keep the board visible so players can judge the help without losing their current reasoning.
Cancel, not enough Koin, and interruption must return to the exact arrangement, move count, and timer state. A delivered hint should affect only the promised puzzle and should not silently solve later levels.
This logic challenge game uses a puzzle browser prototype centered on readable rules, hint pacing, and satisfying solution feedback. Review the genre through wait until the rule is learned and describe hint depth precisely. For a no-code creator, the cosmetic collection should support that loop without becoming mandatory. Review the item through preview it during play and make ownership obvious. A no-code creator should describe observable screens and change only one generation instruction per iteration. 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 board whose rule has already been taught and save its exact arrangement, move count, timer, and available undo actions. Let the player make a genuine attempt before opening the item. Cancel and continue from the same reasoning state, then trigger insufficient Koin without resetting pieces or revealing information. For a valid purchase, apply only the promised clue, highlight, quantity, or theme; do not advance a later puzzle or erase the solution process. Solve or abandon the board, reopen the game, and inspect hint inventory and progress. The final result should preserve mastery, make the help level obvious, and avoid turning every difficult moment into another prompt.
Ask for the item preview, price, balance, buttons, pending state, delivered state, and return path in ordinary language. Avoid broad requests for a monetization backend that do not tell the generator what players should see.
If delivery is unclear, revise only the delivery sentence. If cancellation loses progress, revise the return-state sentence. Small prompt changes make it easier to understand which instruction improved or damaged the result.
A first result may demonstrate only success. Add separate directions for insufficient Koin, cancel, repeated input, interruption, and reopening, then operate each path rather than assuming a labeled button works.
Keep the last playable version beside the new generation. Compare the same player actions in both builds, preserve the stronger behavior, and avoid replacing a working core game merely to alter purchase wording.
When a generated build misses the intent, describe the exact action and outcome instead of asking for a better purchase system. For example, say that choosing cancel must close the panel and resume at the same checkpoint, or that success must add one named item to a visible inventory slot. Keep the previous generation open, change one instruction, and compare identical routes. If a control is only decorative, state which state change it needs to produce. Continue until preview, decline, insufficient Koin, pending, delivery, and reopening can all be operated. Anything requiring identity, native billing, security, or refunds belongs in a separate production plan.
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 logic challenge 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. Prompt for the preview, price, balance, confirm, cancel, success, and owned state separately. Change one instruction at a time between generations.
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
Generate the failure states explicitly. If the result only shows success, add an insufficient balance, a cancelled choice, interruption, and reload to the next prompt.
Result: No-code creator plan
Create a browser-playable puzzle game prototype for a no-code creator. Build the core loop around readable rules, hint pacing, and satisfying solution feedback. 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