• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Deuterium Oxide

Distribution Manager
Paradox Staff
15 Badges
Jan 13, 2014
568
434
  • Magicka: Wizard Wars Founder Wizard
As recently announced, we now attempt to cloud sync playsets - at least playsets that contain mods downloaded from PDX Mods. As a result of this change, playsets are now owned by a certain account user. This is necessary since we can only cloud save data on a per-user basis, not on a per-machine basis. In fact, doing that would sort of undo the usefulness of the cloud sync in the first place, as the intent is to share playsets between installations of the game.

Taking ownership
The first user to log in to their account on the launcher will assume ownership of existing local playsets. This behaviour was selected because we know that the vast majority of our launcher installations are used by a single player, and this facilitates that use-case. Still, it might be not be intuitive for multi-user installations - See below for remedy.

Using others playsets
For users that share an installation but have separate PDX accounts, all playsets installed for the same computer user (regardless of PDX account ownership) are available for play and editing: You can use and edit your brothers' playsets, but you whatever changes you make to your brothers' playsets won't be cloud synced until he logs in. This way, anyone downloading their playsets to your computer won't have your changes to their playsets propagate and overwriting their server copy.

If you want your own copy of a playset belonging to another PDX account holder, you can make a clone of that playset that will be your own, and thus synced just like you'd aniticipate. Please be aware that any changes you make to your copy will not be transferred to the original playset you cloned.

Playsets and GDPR
Now for a fun bit of legalese. If you request that your account be deleted, it will be deleted. D'uh. This includes any associated cloud copies of your playsets, which will be irretrievably lost. If you have any playsets installed that belong to that now non-existant account. If you plan on a "clean exit" you should do the following:

Recommended GDPR actions
  1. Export all playsets you want to keep to file ("share" under the menu next to the playset selection drop-down when viewing a playset)
  2. Delete all playsets associated with the user you intend to delete (another option in the same menu)
  3. Log out of the launcher
  4. File your GDPR request
  5. Import your playsets into the launcher again ensuring they are not associated with a PDX account
  6. Don't create a new account or log in (or you'll just end up in our databases again)
If you have managed to end up in a weird state where you want to start over - Despair not! It'll just be a bit more work and file-system cranking. Try this:

In case of GDPR OOPS
  1. Export all playsets you want to keep to file ("share" under the menu next to the playset selection drop-down when viewing a playset)
  2. Close the launcher
  3. Locate the launcher-v2.sqlite file (exact location depending on your operating system)
  4. Delete the launcher-v2.sqlite knowing that this will wipe out any playsets you didn't export
  5. Restart the launcher and skip any account onboarding (or you'll just end up in our databases again)
  6. Import your playsets into the launcher again ensuring they are not associated with a PDX account
Edit: The playset ownership feature was changed in 2021.10.1 to allow local users edit rights to all playsets. Further safety measures to ensure unwanted changes don't propagate to your cloud backup will be implemented at a later point in time.
 
Last edited:
  • 1
  • 1Like
Reactions: