Rui Miranda

Steps to Reproduce:

1. Backup your minecraftWorlds before!

2. Delete minecraftWorlds

rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds"

1. Delete TEST folder if exists

rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\TEST\minecraftWorlds"

1. Create TEST folder

mkdir "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\TEST\minecraftWorlds"

1. Create symlink

mklink /J "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds" "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\TEST\minecraftWorlds"

1. Start Minecraft App

2. Create a new world

Observed Results:
Error,
"There was a problem loading this world"

Expected Results:
No error, world should be created and placed in TEST folder

There seems to have been a change in behaviour since version 1.17.34, before with symlink Minecraft app crashed on start, now it starts and crashes on world create.

I can confirm it's ok now on 1.18

still same frequency in new version, also with parrots: video of bug with parrots

Realms disconnects often and world is rollback, if this can't be fixed then increase autosave/backup frequency, or give an option to do so.
I keep loosing a lot of gametime due to this.
Currently happening on 1.17.10

Still happening on new release 1.17.10 and no activity on this bug...bump

Still happening on new release 1.17.10 and no activity on this bug...bump

Still happening on new release 1.17.0 and no activity on this bug...bump

This is still happening.
Tested with 3 cats and game disconnected, tested without cats and the game did not disconnect.
In this case I was able to connect right away after, but the game rollbacked.

Test OK: https://drive.google.com/file/d/1SldlororQjO0R_ayN-H0FTn4CHV6SBh5/view?usp=sharing
Test KO: https://drive.google.com/file/d/1eSTo9uCghiaazzockQ7wkVLvjmw_EYiP/view?usp=sharing

Still happening on new release 1.16.221 and no activity on this bug...bump

Still happening on new release 1.16.220 and no activity on this bug...bump

I did some more testing and discovered that symlink only works if the target folder is placed under the LocalState folder or sub-folders.

Is this an expected behaviour?

Here are the cmd tests I made:

REM backup your minecraftWorlds before!!!

rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds"
rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\minecraftWorlds"
rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\minecraftWorlds"
REM ignore errors

REM test 1 ok:
mkdir "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\minecraftWorlds"

mklink /J "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds" "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\minecraftWorlds"

REM start minecraft windows app, it opens ok
rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\minecraftWorlds"
rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds"

REM test 2 ko:
mkdir "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\minecraftWorlds"

mklink /J "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds" "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\minecraftWorlds"

REM start minecraft windows app, it fails ko
rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\minecraftWorlds"
rmdir /q /s "%UserProfile%\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds"