Make Every Shop Visit Shape the Next Round

Plan a between-round shop for an existing card survival game. Define offer lifetimes, currency, rerolls, purchase safety, and round-transition tests.

Seele Editorial TeamUpdated November 16, 2026

A between-round shop can make a card survival game feel more strategic, but only if players understand what each choice buys and how long it lasts. Separate random battle rewards, shop offers, purchase transactions, and persistent unlocks. Then build the next round from a clear snapshot so temporary effects do not leak forward.

A fictional card survivor reviews three shop choices beside a cleared arena before starting the next round.
The candle-keeper and shop are fictional teaching material, not a tested game.

This guide is for an existing card-based survival game. No deck, economy, round flow, or save file was inspected. Treat the sample currency and cards as design prompts, then verify the rules in the actual project.

Make the shop a decision point

When a round ends, the shop should help answer: what should I change before the next one? A player might buy a card, remove a weak card, reroll an offer, or save currency for a later round. The screen should make the cost, effect, and lifetime of each choice legible before purchase. Keep the offer set small enough to compare without obscuring the next step.

ChoicePossible purposeLifetime to disclose
Buy a cardChange the next round's deckOne round, current run, or profile?
Remove or transformImprove deck consistencyDoes the deck change persist?
RerollTrade currency for new optionsDoes the new offer set survive reload?
Save currencyKeep flexibility for laterDoes unspent balance carry over?

In the fictional candle-keeper example, a purchased shield card lasts for the next round, while a discovered recipe remains unlocked for the run. These rules are invented. A real game may choose different lifetimes; write them down in the offer data and communicate them in the shop interface.

Separate offer generation from purchase

Generate an offer set from a known input: current run state, eligible card pool, round, and any existing rarity or unlock rules. Save enough information to reproduce or validate that set if the player can leave and reopen the shop. Otherwise, returning to the screen may silently reroll offers or change prices.

A fictional survival shop displays a small currency purse, three rotating card offers, and one reserved reroll token.
Keep the offer pool, current balance, and reroll action visibly distinct.

When a player buys, validate the offer and available currency, apply the cost, then apply the card effect as one logical transaction. Give the purchase a stable offer or transaction ID so reopening the screen cannot apply it twice. Avoid a flow where the currency is deducted but the card fails to enter the deck, or the card is granted without the cost being recorded.

TransitionState to updateFailure to prevent
Generate offersCurrent offer IDs and costsOffers change unexpectedly on re-entry
PurchaseBalance and card destinationCost and effect diverge
RerollReroll cost and new offersRepeated action avoids the cost
Start roundSnapshot of deck and run stateTemporary shop state leaks into battle

Keep the existing progression system as the source of truth. Trace how the game already handles battle drops, deck edits, currency, and round starts. A second shop inventory or balance field can disagree with the combat system and create hard-to-reproduce state.

Set lifetimes before adding persistence

Label each offer effect as round-only, run-long, or profile-persistent. A temporary shield can disappear at round end. A card unlocked for a run may remain available until death or restart. A profile-level card pool may survive sessions. Make those categories explicit and reuse the project’s current reset flow.

For a Godot project, the official saving tutorial shows an example of identifying data that should persist and serializing relevant fields. That does not decide this game's card lifetimes or prove a shop implementation. Follow the existing save model and confirm the current engine version and target platform before adding fields.

Use a copied save to think through old data. If the new shop fields are absent, should the player receive the old balance, an empty offer state, or a one-time conversion? Specify defaults and schema version. Keep a recoverable source copy until the migration passes in the actual project.

Ask AI to trace the current loop first

Provide the files or project areas that own round completion, rewards, currency, deck editing, and save state. Ask AI to map those responsibilities before proposing code. Bound the change: preserve combat rules, deck draw order, existing card IDs, round pacing, and restart behavior. Request changed files, transaction assumptions, migration defaults, tests, and rollback steps.

Inspect the existing card survival round, reward, currency, deck, and save flow before editing. Add a small between-round shop that uses the current progression owner. Preserve battle rewards, draw rules, card IDs, and restart behavior. Make each purchase apply cost and effect once. First list files, state transitions, old-save defaults, edge cases, and rollback steps. Do not claim the shop passes until tested in this project.

SEELE’s current catalog describes creating a game from an idea and exploring playable game categories. That can help sketch a separate card survival concept or shop direction. It does not establish that SEELE modifies an existing repository or preserves player saves.

Test the whole round transition

Test a normal purchase and the paths likely to interrupt it: close the screen, reload, press back, or re-enter the same result. Then check the next round and the intended reset. The illustration below shows an invented transition, not an observed game result.

The fictional candle-keeper enters a fresh arena round with one purchased card while temporary battle effects fade behind.
Temporary effects should follow the game's reset rule; verify that in the actual build.
TestActionVerify
Insufficient balanceChoose an offer that costs more than availableNo card or partial cost is applied
PurchaseBuy one offer and reopen the shopCost and effect apply once
RerollReroll, then reload the shopOffer set and cost follow the chosen rule
Round startBegin the next battlePurchased state transfers; temporary state resets
Restart/deathEnd the run using supported pathRun and profile unlocks reset or persist as designed
Older saveLoad a duplicate from before the shopDefaults and migration preserve a playable run

Record build, run ID, round, offer ID, currency before and after, and observed card destination. If the expected result fails, locate the broken transition—offer generation, purchase, persistence, or round initialization—instead of broadly rewriting the economy.

Frequently asked questions

What should a between-round shop do in a card survival game?

Present a small set of choices that turn the last round into a decision about the next one. Show cost, effect, and whether a card is temporary or permanent. Then start the next round from an explicit state snapshot rather than carrying every previous effect forward.

How many offers should a survival shop show?

Choose the smallest offer set that creates a meaningful decision for the current screen and economy. More options are not automatically better if players cannot compare them quickly. Test offer variety and reroll rules with the actual deck and round pacing.

Should bought cards stay in the deck forever?

That depends on the run design. A purchased card may last one round, one run, or across sessions; label that lifetime and store it with the matching state owner. Keep shop purchases separate from random battle rewards so duplicate grants and reset behavior are easy to inspect.

How can I prevent the shop from granting duplicate purchases?

Give a purchase a stable offer or transaction identity and apply its cost and effect as one validated operation. Reopening the shop should not apply the same transaction again. Test interruption, reload, and back-button paths with a copied save before changing the live progression system.

What should I test after adding a between-round shop?

Test insufficient currency, one purchase, reroll, leaving and reopening, round start, death, restart, and an older save. Record build, run ID, round, offer ID, and observed state. A mock shop screen can explain the choices but cannot prove the economy or save behavior works.

Keep the offer and the next round connected

A strong shop makes its tradeoffs clear, applies each purchase once, and starts the next round from the intended state. Define lifetimes before adding save fields, keep one progression owner, and verify reload and restart behavior with copied saves. That gives the shop room to grow without muddying the survival loop.

To explore a separate playable card survival idea, try SEELE AI Game Maker. It is a concept tool, not an existing-project editor.

Sources

SEELE AI

Turn this guide into a playable build.

Start with a focused brief, then iterate in the Seele AI Workspace.

Start creating