I found a way to fix this stupid useless issue.
If you can't open your own world with multiplayer enabled, CONNECT TO A VPN(why this fixes it, don't ask me. I'm pretty sure theres nothing wrong with my own ip address but maybe minecraft isn't so sure). For me at least, the world will load up perfectly, and without any lag, and other players can join my world.
I'm using Android 10, playing v1.16.200
Still an issue in 1.16.200.02
My theory is that this happens because the helmet is displayed under the drowned's skin. Because of irregularities in the head texture, the helmets colour can be seen poking out here and there.
I explored a nether fortress on hard difficulty, adventure mode with Resistance 10 and Regeneration 10(making myself immortal) on android 1.16.100 on my own singleplayer world, and experienced this:
After running around for about 40 minutes, I started getting knockback, the wither effect, and got set on fire from unexplained sources.
Because I was immortal, I was able to retrace my steps. And I saw a wither skeleton hacking away at where I was 40 seconds before, explaining the knockback and wither effect. The fire probably came from a blaze shooting me.
I hit the wither skeleton from its side with my fist until it died. It received knockback from the direction I(my detached ghost?) hit it(not from the direction that it was hitting 'my body'). The wither skeleton's damage, knockback and death animations were very laggy.
So I surmise that 40 seconds ago, 'my body' got frozen on the spot, while 'my detached ghost' left and went on walking. To the wither skeleton 'my body' was a frozen target it could see that was completely immune to knockback. While it was hitting 'my body', 'my detached ghost' received knockback and the wither effect. After that 'my detached ghost' went back and killed the wither skeleton, with 'my detached ghosts' attacks seeming to come from where 'my detached ghost' was standing, not where 'my body' was standing.
After that I saved and reloaded my game, and everything was back to normal.
edit: so sometimes its the player that freezes and becomes a ghost and not always the mob? 😃
Hi there! I have been experiencing this issue too, on android 1.16.100 and 1.16.101. Fortunately, there are ways to fix it.
1) Go to World Settings->Multiplayer and uncheck Multiplayer Game, and try opening your world again. It should open successfully.
2) Turn off ALL internet connections before trying to open the world, and it should open successfully. After the world opens, you can turn on your internet again.
Unfortunately, players cannot join your game after you open it even with the off-on internet method.(so you can only play singleplayer)
What seems to be happening here is that there is a bug for worlds with multiplayer enabled.
Seems to me there are two seperate issues here, one where the error message shows up because of invalid user ip address(workaroundable by turning off multiplayer, going offline or using a vpn) and another issue where the error message shows up because of something else