ls4ngu1n4ri0l
Comments
hello, here we tested it in our realms after the 1.20.14 update, and we verified that apparently the problem was solved.
what happens now is that instead of closing the game, it freezes for a few seconds and works again.
We have also verified that the microsoft account connection error has been resolved.
many thanks to the support team, we at Legiao Craft Realms appreciate the effort.
Hello, do we have any news about this case? we will be suspending the realms subscription until the problem is resolved because we are having a lot of losses
hello, we noticed that this problem happens when loading an area of the map, we don't know for sure but it could be that some block or item is giving this type of conflict with the 1.20.12 update
I ask that the moderators solve it as soon as possible because it is discouraging players from the realms that we signed.
the problem persists, but it is causing less damage than in the last update,
we are spawning outside the portal layer and taking damage until the map loads.
I hope the moderators fix this problem soon.
hello, after update1.20.11 the problem seems to have reduced.
let's test today's update 1.20.12
hello, in our realms we try some possible temporary solutions until the technical team solves it definitively,
problem: apparently it's a possible spawn glitch that causes us to spawn above or below the portal, causing us to suffocate in the ground or receive damage from mobs.
possible alternatives:
1 - break and reconnect the portal on both sides (nether and overworld) to correct the respawn height.
2 - expand the portal to a height of 6 blocks or more.
3 - open an empty and protected space of at least 3 blocks up and down from the portal
additional - always use a totem and a pickaxe in hand for extra security
hello, this problem had been solved when we reduced the simulation distance to 4, but after yesterday's update (11/07/2023) the problem came back and is now much more evident, I suggest you review the update made yesterday to find out what happened
it was identified that after the 1.20.14 update the problem continues, but with a much lower lethality, and a low frequency.
I believe you are on the right path