Miles Thompson
Assigned
Reported
Comments
In a way, i’m sorry to say this, I tried to recreate the error today as i have previously, and I can not reproduce it, even with the exact same steps, this means the workaround I thought i had found is probably coincidence and it is more likley that I hit a timing issue with my microsoft user auth (although at the time i had logged out and back in on both server and client which should have covered this scenario)
The only other factor i did not try was my childs user account logging in after world move across versions. I will keep this in mind if it happens agai.
Sorry for the hassle, As i can no longer reproduce the error please close this ticket. If it happens again on the next version switch I will open a new ticket and try again to track it down then.
Hit by this as well, just a hotfix version breaks the version validation check between client and dedicated server. request no version match on a hotfix decimal position or in-step release for dedicated servers and clients.
Hit by this as well, just a hotfix version breaks the version validation check between client and dedicated server. request no version match on a host fix decimal position or in-step release for dedicated servers and clients.
Sorry Kanada, my workaround turned out to be coincidence with some background online Auth mechanism. I can't recreate my original issue again.
We know the problem is to do with Microsoft inline authentication, when you switch to online_mode=false, it bypasses Microsoft authentication, which is why you can access your world again. I would love to know if there is some kind of cached record of authentication against new BSD world versions.
I would follow the original advice for the nethernet error. Try logout of Minecraft, launcher, xbox, Microsoft store (try a vanilla BSD world with online-mode=true),.log back in on your client, then if that works try moving your world files over.
Looking through forums ,& past bug reports this issue keeps happening to BSD setups, it's just very hard to pin down exactly what part of the Auth chain is causing this.