Anonymous Person
More than one avatar was detected! There might be multiple accounts sharing this same name.
Assigned
No issues.
Reported
View all
MCPE-219547
Vibrant Visuals: Water in air blurs background
Duplicate
MCPE-145298
Lush Caves Interfering with mansions
Incomplete
MCPE-145296
Insane ammounts of copper generated in new Expirimental features
Incomplete
BDS-14242
Deepslate not generating (NOTE: WRONG CATEGORY SORRY)
Duplicate
MC-104652
World takes different chunks, copies them all over the world
Duplicate
MC-87940
Breeding Bug
Duplicate
MCPE-10057
Massive loss of progress
Duplicate
MC-70677
Zombies Don't Break Doors
Duplicate
MC-56612
Ghasts despawn UPON entering spectator mode
Duplicate
Even when you're hungry?
the build height limit is 320, that is probably why.
If you look in the bedrock beta, this is not a feature yet, due to the fact that updates are being released at different rates so that updates on java get tested a little before they go on bedrock.
duplicate of MCPE-127708
Turning the biome blend option in the video settings off should give you a better look at it.
I have figured out the problem. I turned off VBO's to reduce lag but when I turned them on, my world fixed by itself.
You do realize that the "Removed Herobrine" is a joke by Mojang, right?
Herobrine is not real.
The "Removed Herobrine" thing is a joke from Mojang.
I didn't quite understand. Were you using pocket edition or pocket editor? If you use pocket editor, that is a 3rd party client/server and should be worked out with the owners or managers of pocket editor. And Herobrine doesn't exist.
The "Removed Herobrine" thing is just a joke made by Mojang. Check out the minecraft wiki to learn more.
The custom map has a command making the custom name visible. Use
/summon Horse ~ ~ ~ {CustomName:"Dinnerbone",CustomNameVisible:1}
Herobrine is not real nor has he ever existed. Check the minecraft wiki for more info.
But I must admit, the polar bear does look a bit silly... 😛
??? No, its not fixed. It was fixed in 13w42b, now its come back!
This is a bug in 1.8, not 13w42b! It is not fixed!