Old versions of QC are bricked after an update and remotely signed out

[kc01-8]

🤔 Current Behavior

Old versions are inexplicably remotely signed out and effectively bricked until a new update is installed. There is no reason my installation should not continue to function as is after the initial sign in. I do not want to recompile my mods and lose my worlds due to unavailable mods at the whims of the next update.

✅ Expected Behavior

It would be highly appreciated likely by many who dont bother to report it if this can be somehow patched. It makes wanting to mod and continually play far less enticing because your modlist is almost guaranteed to not be perfectly matchable on the next version for months, if at all, and therefore all progress is likely lost. This has now happened to me twice.

There is no justifiable reason that this program should not continue to function in perpetuity after the initial online sign in to verify ownership.

🥽 Headset Details

Any build prior to the latest

ℹ️ Anything else?

A developer told me it's a side effect of the current system. I believe this is of high priority to fix. A very large amount of people are simply not interested in updating or starting from scratch. The silent majority mostly wishes to set it up once and enjoy it forever, as is, uninterrupted and unmolested be it by updates or any other thing.

[thewiilover]

Please refer to the discords faq channel (heres the message link so its easier to find: https://discord.com/channels/820767484042018829/821469293156892724/1202798703505842237)

[thewiilover]

this is also unfixable. this would require a complete revert of the way questcraft works. the devs will never fix this

[Cartrigger]

Also any version of 4.0 is remotely bricked on complete accident, because we updated our mods and how they are parced in the new version, it deletes all core mods from 4.x
You can upgrade easily by copying files from your quest to your PC or phone, then transferring back after the update.
If you really wanted to, you could grab old Vivecraft versions for 4.0.3 and sideload all your mods, it would still work but you will not be offered support.
Also relating to your initial, I don't see a reason on why not to update if 5.0 offers 90 to 120 fps.

TLDR: We didn't break on purpose but it's a fact that it did, and it's not fixable.

[computer-catt]

i see your point in if a program is working, a new update shouldn't break it, but backwards compatibility is hard and makes everything slower, its not too difficult to transfer your worlds either :p

[thejudge156]

I asked him to open this issue, for the future this behavior should be changed.

[thejudge156]

I will say this now, all previous versions will not be patched to work again, only the future versions will have a fix.

[kc01-8]

i see your point in if a program is working, a new update shouldn't break it, but backwards compatibility is hard and makes everything slower, its not too difficult to transfer your worlds either :p

It's not about backwards compatability. It's about not phoning home to microsoft, beyond the initial verification which I imagine is forced upon you. There is no genuine reason to require additional verification beyond this. There is no actual need to be compatible with anything, but merely to not be interfered with. Should I rather take my quest offline after I have signed in to prevent it? What exactly is so profound as to prevent you from actively interfering with and disabling old versions, a forced online login that doesnt actually save? Or is it nothing to do with the program and your hand is forced by microsoft?

[Cartrigger]

Sign in should still work, running the game will crash but is possible to play if you grab mods from our GitHub and grab included mods on modrinth manually.

[thewiilover]

i see your point in if a program is working, a new update shouldn't break it, but backwards compatibility is hard and makes everything slower, its not too difficult to transfer your worlds either :p

It's not about backwards compatability. It's about not phoning home to microsoft, beyond the initial verification which I imagine is forced upon you. There is no genuine reason to require additional verification beyond this. There is no actual need to be compatible with anything, but merely to not be interfered with. Should I rather take my quest offline after I have signed in to prevent it? What exactly is so profound as to prevent you from actively interfering with and disabling old versions, a forced online login that doesnt actually save? Or is it nothing to do with the program and your hand is forced by microsoft?

Nobody is forcing anything on anyone.
But why would you want to stay on any old versions that are proven to have much worst performance than the newest version. I mean I know it might be a hassle to move around some of the files to the correct place due to those changes, but I'd rather do that for 5 minutes and get a huge boost in the fps than stay on the older version and get worst performance.

[Cartrigger]

I'll revisit it.

Overall, we have made strives to make this issue better, but now with 5.0 broken, that means all releases are broken. We don't remotely sign out people as signing in does not phone home, but version getting (1.20.1, mods) are broken.

In the next release, we will be moving to a new system which will break 5.0 most likely, but will make it where all new releases are not broken. We will also be supporting upgrading to the new version from 5.0.

Please note that I am not a developer so this may be proofread later and corrected.