Data, Backup & Upgrading
Where your Command Pocket data lives, how it is protected, and how upgrades work.
Where your data lives
| Data | Location | Version controlled? |
|---|---|---|
| Per-user data (unshared Pocket / Notes / Colors / Quick Actions, recent history, usage stats, UI preferences) | UserSettings/CommandPocket/LocalData.json | No. UserSettings/ is ignored by standard Unity VCS templates |
| Your shared data (the kinds you enabled) | .../CommandPocket/Data/Profiles/{name}.json | Yes, commit your own file |
| Team data (e.g. Pocket categories) | .../CommandPocket/Data/SharedData.json | Yes |
Data safety
- All data files are written atomically: a crash mid-write can never corrupt them.
- Saves are content-gated: recompiles don't touch the files, so committed profile files stay clean in
git status. - Pending edits are flushed on quit and before every script recompile, so an ordinary quit or recompile does not drop your work.
- If a file ever fails to load, a recovery copy is quarantined under
UserSettings/CommandPocket/Quarantine/and Command Pocket keeps working.
Backup
Committing regularly to Git covers the shared files. Your local data can be backed up by copying UserSettings/CommandPocket/LocalData.json.
Upgrading from v1.0
v1.2 introduces the profile system and a new storage layout, so your v1.0 data does not carry over. We recommend a clean install rather than upgrading in place:
- Note down any important Notes, Colors or Pocket items first.
- Delete the previous
Command Pocketfolder from your project. - Import v1.2. On first launch you are asked for a profile name; you can change it later in Settings.
Unity 2022.3 projects cannot upgrade. v1.2 requires Unity 6000.0 or newer; stay on v1.0.0 on older editors.