The developer’s launch FAQ says version 0.70 saves carry over to 1.0. It separately says that console-to-Steam cross-save is not available.
Before an update or mod change
Close the game cleanly, identify your platform’s supported save-management options and preserve an unchanged backup where possible. Label it with the date, game version and mod setup.
A synced save and a separate backup are not the same plan. If a bad change syncs, the synced copy may not be the older version you expected to keep.
When asking for help
Include the platform, exact build, whether the save originated in 0.70 and whether any mods were active. Explain what happened just before the problem and whether a new, separate save works.
Avoid uploading a full directory to a stranger. Inspect files for personal information and prefer official support channels for troubleshooting.
What our tools store
The website’s deck planner is independent of your game save. It saves only your entered deck notes and owned counts in this browser. Its JSON export is a website backup, not a game save file.
Clearing browser storage can remove the local worksheet. Download a backup before changing browsers or devices.
The update is installed but features seem missing
The official 1.0 FAQ says a new save is not required for 0.70-to-1.0 carryover. Check the build you are running, let any pending update finish, and distinguish a missing feature from its unlock requirement. The playable-card Workbench unlock is shop level 7; use the Workbench guide rather than resetting your shop.
Carryover does not establish safe downgrades or modded-save recovery. If the problem is a crash, poor frame rate or broken textures, use technical troubleshooting. File verification checks the installation, not whether lost progress can be recovered.
Choose the right migration path
Updating the same shop and moving to another platform are different jobs. The developer’s September 14 launch FAQ permits 0.70 saves to carry into 1.0, but separately says console-to-Steam cross-save is not available. Owning another edition does not turn a browser planner export into a transferable shop save.
- Write down the current platform, installed build and the shop you want to keep.
- For an update on the same platform, use its normal update process and retain an unchanged backup where supported. Keep the original instead of testing on the only copy.
- For a platform switch, check that destination’s official support before copying files. Do not use a converter claiming an unsupported cross-save path.
- After updating, check the loaded shop and inventory before replacing your older backup. Treat a mismatch as a support question, not an instruction to start over.
This is a save-preservation checklist, not a recovery tool. Console and PC builds can have different update schedules; the PC 1.02 notes are not proof of a console build number.
Good questions. Clear answers.
Does the planner edit my game files?
No. It neither reads nor writes game saves, and it does not require your Steam account.
Can I move my console shop to Steam by exporting the wiki planner?
No. The planner export contains website notes, not the game save. The developer’s launch FAQ says console-to-Steam cross-save is unavailable.
Source-reviewed . Recommendations are editorial guidance, not in-game benchmark results.
OPNeon Games — 1.0 update and launch FAQ Workbench unlock, playable TCG, Ascension, tournament participation, save transfer and multiplayer status.
OPNeon Games — official 1.0 Update FAQ Reopened September 19: 0.70 saves carry forward to 1.0; console-to-Steam cross-save is not offered; model/memory optimization is described. This is not a save-recovery, downgrade-compatibility or measured-FPS promise.
Steam Support — Verify Integrity of Game Files Platform guidance reviewed September 19: Library → Properties → Installed Files → Verify integrity of game files for installation checks. Steam notes that some local configuration files can fail verification normally. This is not a TCG-specific save repair or an FPS guarantee.