![]() ROllerozxa |
|
![]() ROllerozxa Posts: 137 Joined: 2020-12-26 |
Posted on 2026-05-17 19:37 Link |
It's been over a year since the last release of Principia, partially due to a lack of development activity on the game but also due to a lack of testing of changes that are made for the game, which is a prerequisite for actually being able to actually release a new version. Specifically this time, there is both new locations for user data directories on some platforms as well as a new directory structure, as well as migration code to move from the old to the new. While it's careful enough that no data loss should occur, even for junk files that people may have scattered in their user data directory themselves, it's still important that the most important data is correctly migrated to ensure that users are not confused by their levels disappearing. For more information about the migration process see User Data Directory Migration page on the wiki. However, this is not all. There have been many other changes since the latest release and many technical code changes have also been made, and finding any potential regressions would also be greatly appreciated. See the changelog for a (slightly outdated) summary. Note, in big letters to make you read it: BACK UP ANY IMPORTANT USER DATA BEFORE INSTALLING! You will not be able to go back.For Android, make sure you have some way of accessing the Principia app data. Do NOT install the Android version if you cannot access your user data directory. First, make sure you have installed or run the current stable version of Principia, see the downloads page, and create a level or two in the sandbox (just drag out some planks and then save). This is important in order to test the migration process. Then, see the following download links. These are built off of commit 8771027 which is the latest commit at release.
Then report your findings. Report any issues you find but also let me know if things, especially the migration, work like they should. |
| binarctq | |
|
binarctq
Posts: 4 Joined: 2026-04-26 |
Posted on 2026-05-31 00:29 Link |
Hey, so I'm very late, but I tested this across windows, linux and android. On linux (appimage) it works just as intended, migration is run and all useful data is carried over, and empty folders aren't removed (intended behaviour?) On windows 10, the migration runs but only the .autosave level is carried across, normal player .plvl levels are not. The old userdata folder under C:\Users\user\Principia is renamed to Principia_old, but that seems like the end of it (except the .autosave level) For android 16, same situation as windows. I am running GrapheneOS, maybe this hinders it in some way? I do not have another working android device to test unfortunately. Let me know if there's any other way I can help. |
![]() ROllerozxa |
|
![]() ROllerozxa Posts: 137 Joined: 2020-12-26 |
Posted on 2026-05-31 01:43 Link |
Thanks for the testing. Just checked real quick and yeah seems like moving over the levels & such is broken on Windows (there's a specific Win32 codepath for moving files based on wildcard) - I swore this used to work so I will have to take a closer look at that. As for Android I'm not really sure what happened there. I've tested it in the Android SDK emulator with an Android 16 image and it works there so it may be an issue with whatever GrapheneOS is doing.... Not sure about that. |
| binarctq | |
|
binarctq
Posts: 4 Joined: 2026-04-26 |
Posted on 2026-05-31 11:00 Link |
So it was a mistake on my part, I manually copied the userdata folder between the versions because I had the F-Droid version installed, something was not right. Just tested by making some levels with the latest stable signed by you, then directly updating to the dev version and it all works. |
![]() ROllerozxa |
|
![]() ROllerozxa Posts: 137 Joined: 2020-12-26 |
Posted on 2026-06-01 20:10 Link |
I see. I ended up looking further into the problem on Windows and ended up fixing it - turns out I had forgotten to use wide UTF-16 strings for the filepaths. :S When I was writing it I was working on it as an independent program and likely hadn't defined UNICODE so it was using the equivalent ASCII functions. Just Win32 stuff... But yes that should work now, thanks for making me aware of it! |