Vinícius Verissimo Bazan
Assigned
Reported
MCPE-147823
Skin from other split-screen players are not what they should be.
Duplicate
MCPE-147322
Boats disappearing after disembarking
Duplicate
MCPE-147314
mobs disappear after entering the world or returning from the Nether
Duplicate
MCPE-147313
mobs disappear after entering the world or returning from the Nether
Duplicate
Comments
What exactly is Mojang doing? I realized that this issue was first reported on 12/11/2019.
It may not be a serious problem, but it is frustrating over so long the problem persists unresolved.
In 1 month it completes 2 years of existing bug without resolution.
basically the problem occurs when we have at least one player with split screen on xbox.
When loading the player his skin is the default (Steve or Alex), even if previously he has customized his skin in his own profile.
This issue also does not allow the player to select any skin previously saved in their profile.
I reported this same issue as well, but I didn't notice if anyone else mentioned it: Going through the Nether portal back to the overworld also makes the mobs disappear. This just doesn't happen if there is another player in the portal of destiny carrying the land.
I accidentally added two identical reports.
The other reporter has id MCPE-147314, he is more complete.
From what I've noticed these issues are only happening with worlds created before 1.18?
I had this problem also in an old world of mine, but I still haven't accessed it after the upgrade as I'm waiting for a definitive solution.
That's why I decided to create a new world, I've already tamed a dog and so far I haven't had any problem with a tamed dog disappearing (in another world before 1.17 about 8 tamed dogs disappeared).
Could it be that worlds generated in this new version are not affected by the bug?
Note: Sorry for any grammatical errors and syntax. My mother tongue is not English, that's why I'm following this bug with google translator, I also used this tool to translate what I just published.
Reply from @unknown:
We know there are plenty of worlds from 1.17 or earlier that aren't affected., and we haven't been using 1.18 long enough to decide whether any new worlds are affected, so it's premature to be speculating about this.
As a general rule, drawing conclusions based only on the experiences of one person or on one device isn't very reliable. Bugs often have seemingly different behaviors for different people, because there are many, many differences in devices, in people's play styles, and between versions of the game. So in looking for what causes a bug, the developers have to consider everybody's individual experiences to make sure their fix fixes the problem from everybody.
BTW, the translation looks flawless to me.