Stephen W.
- EnderSteve04
- endersteve04
- Europe/Stockholm
- Yes
- No
MC-102425
MCPE-41381![[Mojang] Cory Scheviak](../../../data/avatars/users/92893.png){kind=small}
MCPE-42900MCPE-43900
Iron Golems often find themselves stuck 1 block deep in the ground when they are on matted/pathway dirt, I believe it happens when they are jumping and the negative velocity of the golem is saved, then when the chunk is reloaded, my guess is that their position is reloaded into a rounded or estimated position and then they are stuck in the ground.
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some end pillars appear exposed when they aren't
This glitch allows twice the large XP drop, and two dragon eggs.
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some endpillarsappear exposed when they aren't
This glitch allows twice thelarge XPdrop, and two dragon eggs.Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some end crystals in the end dimension appear exposed when they aren't.
This glitch allows twice the first enderdragon defeat experience points drop, and two dragon eggs.Yet another end dimension related bug (particle bug, needs direct confirmation externally) occurs, it happens most likely when:
a: an end world is converted to beta when an area affect cloud of harming from the enderdragon fireball was still active when the world was unloaded.
b: occurs when reloading the end dimension via exiting and rejoining while dragon fireball cloud is in effect.
c: any unloading and reloading of world or dimension (jump through portal) when dragon fireball effect hasn't expired its timer.
d: when the user is in the end dimension, loads the end dimension while the world is in singleplayer.
This results in the particle effect from the dragon fireball area of effect cloud rendering to the users particle render distance on the y axis of where it was last unloaded. The particle glitch is brief, only lasts as long as an individual particle from the dragons area affect cloud does.A good note for another end loot bug is that elytra (obtained from end) will have a minor UI bug during flight, where the player's head is located different than when the player is not flying, but the location of which the player looks at chests, shoots bows and drops blocks remains unchanged. This results in the player flying in spaces where the head would normally be during non-flight, and the player will suffocate if he or she flies into the bottom of a block, showing the suffocation air bar (oxygen bar hud) and sometimes causing damage to the player, but the players head is not rendering near a block. This principle goes for attempting opening chests during slow flight (elytra plus slow falling), and looking at a chest during flight and attempting to open the chest doesn't function unless the player looks at a vertical axis lower than normal. Shooting bows during elytra flight is bugged; the arrow shoots like the player is standing, even if he is descending during flight. This glitch is simply that the location where the player interacts with the world (the head) doesn't change during flight, but the camera position does.
A final note is that during elytra flight, any horizontal motion does not damage the player when impacting walls, but vertical motion does, is this a bug or a feature?
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some end crystals in the end dimension appear exposed when they aren't.
This glitch allows twice the first enderdragon defeat experience points drop, and two dragon eggs.Yet another end dimension related bug (particle bug, needs direct confirmation externally) occurs, it happens most likely when:
a: an end world is converted to beta when an area affect cloud of harming from the enderdragon fireball was still active when the world was unloaded.
b: occurs when reloading the end dimension via exiting and rejoining while dragon fireball cloud is in effect.
c: any unloading and reloading of world or dimension (jump through portal) when dragon fireball effect hasn't expired its timer.
d: when the user is in the end dimension, loads the end dimension while the world is in singleplayer.
This results in the particle effect from the dragon fireball area of effect cloud rendering to the users particle render distance on the y axis of where it was last unloaded. The particle glitch is brief, only lasts as long as an individual particle from the dragons area affect cloud does.1.8.1 Bugs (all pending to be confirmed)
A good note for another end loot bug is that elytra (obtained from end) will have a minor UI bug during flight, where the player's head is located different than when the player is not flying, but the location of which the player looks at chests, shoots bows and drops blocks remains unchanged. This results in the player flying in spaces where the head would normally be during non-flight, and the player will suffocate if he or she flies into the bottom of a block, showing the suffocation air bar (oxygen bar hud) and sometimes causing damage to the player, but the players head is not rendering near a block. This principle goes for attempting opening chests during slow flight (elytra plus slow falling), and looking at a chest during flight and attempting to open the chest doesn't function unless the player looks at a vertical axis lower than normal. Shooting bows during elytra flight is bugged; the arrow shoots like the player is standing, even if he is descending during flight. This glitch is simply that the location where the player interacts with the world (the head) doesn't change during flight, but the camera position does.
A final note is that during elytra flight, any horizontal motion does not damage the player when impacting walls, but vertical motion does, is this a bug or a feature?
Conversion Bugs (confirmed)
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some end crystals in the end dimension appear exposed when they aren't.
This glitch allows twice the first enderdragon defeat experience points drop, and two dragon eggs.Yet another end dimension related bug (particle bug, needs direct confirmation externally) occurs, it happens most likely when:
a: an end world is converted to beta when an area affect cloud of harming from the enderdragon fireball was still active when the world was unloaded.
b: occurs when reloading the end dimension via exiting and rejoining while dragon fireball cloud is in effect.
c: any unloading and reloading of world or dimension (jump through portal) when dragon fireball effect hasn't expired its timer.
d: when the user is in the end dimension, loads the end dimension while the world is in singleplayer.
This results in the particle effect from the dragon fireball area of effect cloud rendering to the users particle render distance on the y axis of where it was last unloaded. The particle glitch is brief, only lasts as long as an individual particle from the dragons area affect cloud does.1.8.1 Bugs (all pending to be confirmed)
A good note for another end loot bug is that elytra (obtained from end) will have a minor UI bug during flight, where the player's head is located different than when the player is not flying, but the location of which the player looks at chests, shoots bows and drops blocks remains unchanged. This results in the player flying in spaces where the head would normally be during non-flight, and the player will suffocate if he or she flies into the bottom of a block, showing the suffocation air bar (oxygen bar hud) and sometimes causing damage to the player, but the players head is not rendering near a block. This principle goes for attempting opening chests during slow flight (elytra plus slow falling), and looking at a chest during flight and attempting to open the chest doesn't function unless the player looks at a vertical axis lower than normal. Shooting bows during elytra flight is bugged; the arrow shoots like the player is standing, even if he is descending during flight. This glitch is simply that the location where the player interacts with the world (the head) doesn't change during flight, but the camera position does.
A final note is that during elytra flight, any horizontal motion does not damage the player when impacting walls, but vertical motion does, is this a bug or a feature?
Conversion Bugs (confirmed)
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some end crystals in the end dimension appear exposed when they aren't.
This glitch allows twice the first enderdragon defeat experience points drop, and two dragon eggs.
Yet another end dimension related bug (particle bug, needs direct confirmation externally) occurs, it happens most likely when:
a: an end world is converted to beta when an area affect cloud of harming from the enderdragon fireball was still active when the world was unloaded.
b:occurs when reloading the end dimension via exiting and rejoining while dragon fireball cloud is in effect.
c:any unloading and reloading of world or dimension (jump through portal) when dragon fireball effect hasn't expired its timer.
d:when the user is in the end dimension, loads the end dimension while the world isin singleplayer.
This results in the particle effect from the dragon fireball area of effect cloud rendering to the users particlerenderdistance on the y axis of where it was last unloaded. The particle glitch is brief, only lasts as long as an individual particle from the dragons area affect cloud does.1.8.1
Bugs (all pending to be confirmed)
A good note for another end loot bug is that elytra (obtained from end) will have a minor UI bug during flight, where the player's head is located different than when the player is not flying, but the location of which the player looks at chests, shoots bows and drops blocks remains unchanged. This results in the player flying in spaces where the head would normally be during non-flight, and the player will suffocate if he or she flies into the bottom of a block, showing the suffocation air bar (oxygen bar hud) and sometimes causing damage to the player, but the players head is not rendering near a block. This principle goes for attempting opening chests during slow flight (elytra plus slow falling), and looking at a chest during flight and attempting to open the chest doesn't function unless the player looks at a vertical axis lower than normal. Shooting bows during elytra flight is bugged; the arrow shoots like the player is standing, even if he is descending during flight. This glitch is simply that the location where the player interacts with the world (the head) doesn't change during flight, but the camera position does.
A final note is that during elytra flight, any horizontal motion does not damage the player when impacting walls, but vertical motion does, is this a bug or a feature?Conversion Bugs (confirmed)
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some end crystals in the end dimension appear exposed when they aren't.
This glitch allows twice the first enderdragon defeat experience points drop, and two dragon eggs.
Updates for end dimension bugs; unconfirmed(additional, random, end dimension bug; unconfirmed)
Yet another end dimension related bug (particle bug, needs direct confirmation externally) occurs, it happens most likely when:
a: an end world is converted to beta when an area affect cloud of harming from the enderdragon fireball was still active when the world was unloaded.
b: occurs when reloading the end dimension via exiting and rejoining while dragon fireball cloud is in effect.
c: any unloading and reloading of world or dimension (jump through portal) when dragon fireball effect hasn't expired its timer.
d: when the user is in the end dimension, loads the end dimension while the world is in singleplayer.
This results in the particle effect from the dragon fireball area of effect cloud rendering to the users particle render distance on the y axis of where it was last unloaded. The particle glitch is brief, only lasts as long as an individual particle from the dragons area affect cloud does.~1.8.1 unconfirmed (but frequently occurring) bugs
1.8.1 Elytra Bugs (all pending to be confirmed; added after confirmation)
A good note for another end loot bug is that elytra (obtained from end) will have a minor UI bug during flight, where the player's head is located different than when the player is not flying, but the location of which the player looks at chests, shoots bows and drops blocks remains unchanged. This results in the player flying in spaces where the head would normally be during non-flight, and the player will suffocate if he or she flies into the bottom of a block, showing the suffocation air bar (oxygen bar hud) and sometimes causing damage to the player, but the players head is not rendering near a block. This principle goes for attempting opening chests during slow flight (elytra plus slow falling), and looking at a chest during flight and attempting to open the chest doesn't function unless the player looks at a vertical axis lower than normal. Shooting bows during elytra flight is bugged; the arrow shoots like the player is standing, even if he is descending during flight. This glitch is simply that the location where the player interacts with the world (the head) doesn't change during flight, but the camera position does.
Conversion Bugs (confirmed)
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some end crystals in the end dimension appear exposed when they aren't.
This glitch allows twice the first enderdragon defeat experience points drop, and two dragon eggs.
Updates for end dimension bugs;unconfirmed(additional, random, end dimension bug
; unconfirmed)
Yet another end dimension related bug (particle bug, needs direct confirmation externally) occurs, it happens most likely when:
a: an end world is converted to beta when an area affect cloud of harming from the enderdragon fireball was still active when the world was unloaded.
b: occurs when reloading the end dimension via exiting and rejoining while dragon fireball cloud is in effect.
c: any unloading and reloading of world or dimension (jump through portal) when dragon fireball effect hasn't expired its timer.
d: when the user is in the end dimension, loads the end dimension while the world is in singleplayer.
This results in the particle effect from the dragon fireball area of effect cloud rendering to the users particle render distance on the y axis of where it was last unloaded. The particle glitch is brief, only lasts as long as an individual particle from the dragons area affect cloud does.~1.8.1
unconfirmed(but frequently occurring) bugs
1.8.1 Elytra Bugs (all pending to be confirmed; added after confirmation)
A good note for another end loot bug is that elytra (obtained from end) will have a minor UI bug during flight, where the player's head is located different than when the player is not flying, but the location of which the player looks at chests, shoots bows and drops blocks remains unchanged. This results in the player flying in spaces where the head would normally be during non-flight, and the player will suffocate if he or she flies into the bottom of a block, showing the suffocation air bar (oxygen bar hud) and sometimes causing damage to the player, but the players head isnot rendering near a block. This principle goes for attempting opening chests during slow flight (elytra plus slow falling), and looking at a chest during flight and attempting to open the chest doesn't function unless the player looks at a vertical axis lower than normal. Shooting bows during elytra flight is bugged; the arrow shoots like the player is standing, even if he is descending during flight. This glitch is simply that the location where the player interacts with the world (the head) doesn't change during flight, but the camera position does.Conversion Bugs (confirmed)
Converting a 1.8.1 World (enderdragon defeated, egg harvested) and loading it up on 1.10.3 Beta version causes respawning the enderdragon to act like the first enderdragon battle, releasing the first defeat XP amount, and dragon egg. Respawning it once more causes the enderdragon to be invisible and will only render when the world is reloaded.
Note that the invisible enderdragon has all functions (healing, dragon breath, etc) but the entity that renders the mob texture itself is missing (enderdragon).
Another issue between worlds is that iron bars do not render from a certain distance, making some end crystals in the end dimension appear exposed when they aren't.
This glitch allows twice the first enderdragon defeat experience points drop, and two dragon eggs.
Updates for end dimension bugs; pending additional confirmation(additional, random, end dimension bug)
Yet another end dimension related bug (particle bug, needs direct confirmation externally) occurs, it happens most likely when:
a: an end world is converted to beta when an area affect cloud of harming from the enderdragon fireball was still active when the world was unloaded.
b: occurs when reloading the end dimension via exiting and rejoining while dragon fireball cloud is in effect.
c: any unloading and reloading of world or dimension (jump through portal) when dragon fireball effect hasn't expired its timer.
d: when the user is in the end dimension, loads the end dimension while the world is in singleplayer.
This results in the particle effect from the dragon fireball area of effect cloud rendering to the users particle render distance on the y axis of where it was last unloaded. The particle glitch is brief, only lasts as long as an individual particle from the dragons area affect cloud does.~1.8.1 pending confirmation (but frequently occurring) bugs
1.8.1 Elytra Bugs (all pending to be confirmed; added after confirmation)
A good note for another end loot bug is that elytra (obtained from end) will have a minor UI bug during flight, where the player's head is located different than when the player is not flying, but the location of which the player looks at chests, shoots bows and drops blocks remains unchanged. This results in the player flying in spaces where the head would normally be during non-flight, and the player will suffocate if he or she flies into the bottom of a block, showing the suffocation air bar (oxygen bar hud) and sometimes causing damage to the player, but the players head is not rendering near a block (flight animation head location vs standing head location). This principle goes for attempting opening chests during slow flight (elytra plus slow falling), and looking at a chest during flight and attempting to open the chest doesn't function unless the player looks at a vertical axis lower than normal. Shooting bows during elytra flight is bugged; the arrow shoots like the player is standing, even if he is descending during flight. This glitch is simply that the location where the player interacts with the world (the head) doesn't change during flight, but the camera position does.
When flying with elytra, the player head hitbox remains in the same vertically bound position and opening chests, aiming bows and flying through 1 block height spaces is glitched to the original player head location.
[Deleted to avoid duplication of bugs]
Player hitbox remains unchanged during Elytra flight.[Deleted]
Highlighted Bug:
Foxes tend to run from players from a certain distance, but lack any radius to which the fox will run away from the player further than that radius to be "safe" from the player, meaning foxes continue to start and stop running as the player is walking towards them. The starting and stopping motion can be more obvious if the player is imbued with slowness, but because of the motion of the fox, it can be subtle (smooth deceleration and acceleration)Non-Bugs (Deleting this is likely necessary)
Fox iris's aren't white in real life circumstances, unlike the texture of the fox's face in this update, which are cross eyed for some reason, unless this feature is intended.Fox head body proportions aren't generally accurate for the model, except the case that this is a representation of a Fennec fox, but the species of the
"Fox is not specified.(If you need to delete any parts of this feel free, especially the last two small paragraphs)
Highlighted Bug:
Foxes tend to run from players from a certain distance, but lack any radius to which the fox will run away from the player further than that radius to be "safe" from the player, meaning foxes continue to start and stop running as the player is walking towards them. The starting and stopping motion can be more obvious if the player is imbued with slowness, but because of the motion of the fox, it can be subtle (smooth deceleration and acceleration)Non-Bugs (Deleting this is likely necessary)
Fox iris's aren't white in real life circumstances, unlike the texture of the fox's face in this update, which are cross eyed for some reason, unless this feature is intended.Fox head body proportions aren't generally accurate for the model, except the case that this is a representation of a Fennec fox, but the species of the Fox is not directly specified.
(If you need to delete any parts of this feel free, especially the last two small paragraphs)
Highlighted Bug:
Foxes tend to run from players from a certain distance, but lack any radius to which the fox will run away from the player further than that radius to be "safe" from the player, meaning foxes continue to start and stop running as the player is walking towards them. The starting and stopping motion can be more obvious if the player is imbued with slowness, but because of the motion of the fox, it can be subtle (smooth deceleration and acceleration)Non-Bugs (Deleting this is likely necessary)
Fox iris's aren't white in real life circumstances, unlike the texture of the fox's face in this update, which are cross eyed for some reason, unless this feature is intended.Fox head body proportions aren't generally accurate for the model, except the case that this is a representation of a Fennec fox, but the species of the Fox is not directly specified.
(If you need to delete any parts of this feel free, especially the last two small paragraphs)
Foxes tend to run from players from a certain distance, but lack any radius to which the fox will run away from the player further than that radius to be "safe" from the player, meaning foxes continue to start and stop running as the player is walking towards them. The starting and stopping motion can be more obvious if the player is imbued with slowness, but because of the motion of the fox, it can be subtle (smooth deceleration and acceleration)
If you are able to respond or could perhaps respond I'd like to note that:
The texture of the fox's face in this update are cross eyed for some reason, unless this feature is intended.
Foxes' tails also are completely straight in this snapshot, but in real situations are almost never this way unless they are running away or other situations.
Will these features change throughout the updates or are textures/models going to stay the same throughout the updates? I just find that foxes have traits that include sly and menacing rather than wonky eyed and chubby (ish) cheeks. I cannot report on the minecraft feedback website at this time due to the device I'm using, which restricts certain sites. But when I can I certainly will.
Acquire elytra and engage in flight, using explosive fireworks as boost during flight, have the enderman within the explosion radius upon detonation, the player and enderman will take damage, but the enderman does not become hostile from the player's exploding firework (unlike TNT, of which enderman become hostile to the player who detonated it)
Taking any type of firework rocket and renaming it (e.g.: missile ) will result in the firework item rendering its new name when changing the held item to it, but not when looking at it in the inventory.
(note that I had toggled my inventory cursor off at the time)
Endermen don't become hostile if player uses explosive fireworks with elytra.Renamed fireworks do not display name in inventory.
Taking any type of firework rocket and renaming it (e.g.: missile ) will result in the firework item rendering its new name when changing the
held item toit, but not when looking at it in the inventory.
(note that I had toggled my inventory cursor off at the time)Taking any type of firework rocket and renaming it (e.g.: missile ) will result in the firework item rendering its new name when changing the inhand item to the firework rocket, but not when looking at the renamed firework in the inventory. Instead, it displays its original name, "Firework Rocket"
Note: firework NBT (crafted with firework star) included:
-flight duration: 1
-trail
-purple
-large ball
-fade to black(additionally note that I had toggled my inventory cursor off at the time)
Renamed fireworks do not display new name in inventory.
During February 19, 2018 (8:00-10:00 PM CST) An unexpected crash occurred in a free minecraft marketplace world (Void world superflat generation), called "ABSTRACTION: Minecon Earth"
Following
was anautomatic crash report logged to Mojang from the application regarding "EnderSteve04" and his game crash, the following circumstances were amid the crash:-The gamemode was survival, with achievements enabled. The difficulty was set to peaceful
-The enderdragon was respawned using four crystals
-The dragon was beginning his fire breath attack for about the 7 time, I built a bit around the podium so I wouldn't fall.
-The dragon egg podium was floating, and the obsidian towers go down to y=0
-Two attempts at defeating the enderdragon, both crashed at similar points, the health value was different each time for the enderdragon before each crash, monster spawners and evoker entities were present (as part of the abstraction) before the crash.
-Fallen iron bar entities and even a dragon breath harming cloud entity was in during the crash
-About as soon as the dragon breath was floating (see the bug report please), the game crashed in an unusual way:
The resulting crash caused all non-player entities to freeze, and all new particles excluding ones that direct player interactions cause (critical hit, sometimes landing after a fall), would render, but all others would not. If the player attempted to break a block, the block would not render the animation that results when in progress of breaking a block, would not drop the block, nor does the particles render when it a block destroyed. No noises would play except the player and his elytra.
The enderdragon was stuck on his flight animation hovering on the podium
Attempting to return to a different dimension, entering settings, or leaving the game during the softlock would cause a direct game crash.
Attempts to summon new entities such as firework rockets for flight or to soar in the air would
I have video uploaded to xbox live of this, and am preparing to upload it to the bug for further detail and much better explanation
During February 19, 2018 (8:00-10:00 PM CST) An unexpected crash occurred in a free minecraft marketplace world (Void world superflat generation), called "ABSTRACTION: Minecon Earth"
Following right after was a (hopefully) automatic crash report logged to Mojang from the application minecraft regarding "EnderSteve04" and his game crash, the following circumstances were amid the crash:
-The gamemode was survival, with achievements enabled. The difficulty was set to peaceful
-The enderdragon was respawned using four crystals
-The dragon was beginning his fire breath attack for about the 7 time, I built a bit around the podium so I wouldn't fall.
-The dragon egg podium was floating, and the obsidian towers go down to y=0
-Two attempts at defeating the enderdragon, both crashed at similar points, the health value was different each time for the enderdragon before each crash, monster spawners and evoker entities were present (as part of the abstraction) before the crash.
-Fallen iron bar entities and even a dragon breath harming cloud entity was in during the crash
-About as soon as the dragon breath was floating (see the bug report please), the game crashed in an unusual way:
The resulting crash caused all non-player entities to freeze, and all new particles excluding ones that direct player interactions cause (critical hit, sometimes landing after a fall), would render, but all others would not. If the player attempted to break a block, the block would not render the animation that results when in progress of breaking a block, would not drop the block, nor does the particles render when it a block destroyed. No noises would play except the player and his elytra.
The enderdragon was stuck on his flight animation hovering on the podium
Attempting to return to a different dimension, entering settings, or leaving the game during the softlock would cause a direct game crash.
Attempts to summon new entities such as firework rockets for flight or to soar in the air would
I have video uploaded to xbox live of this, and am preparing to upload it to the bug for further detail and much better explanation
I've been frustrated to find that observer blocks dont update to the following blocks, generally those with extended block updates, such as:
-Beetroot
-Wheat
-Melon stem
-Carrot
-Potato
-Pumpkin stem
and more...This same "problem" occurred once on pocket edition (then got fixed), but is the same situation on bedrock, and makes automatic farms really frustrating to build.
I'd like to report a bug (or series of bugs) that occured that led this glitch to be:
I was playing on one of my worlds, and apparently it was updating to the beta (of which I cancelled). It was updating as I was leaving the nether, and then it got stuck in the loading screen. I could hear everything in my base, portal noises, cats, pistons, everything. But never would the screen leave unless I quit minecraft and loaded it back again. I'd like to report that this occurred by doing the following. Keep in mind that this glitch begins when you leave the nether, and persists as such after the update, of which was at the time automatic:Events before glitch
-Have a series of chests with shulker boxes loaded in the nether.
-Have multiple nether portals in the overworld linked to one in the nether.
-Have a lot of furry friends (cats) (18) (Overworld)
-Exit nether whilst game is updating from 1.10 to beta 1.11.0.7
-Have a number of minecart hoppers in overworld (20)
-Have a genuine Xbox One product (not any name brand extensions like X or 4K or S)
-Game is on hard difficulty
-Banners with at least four decorations are in render in each dimension (15)
-Have a number of chests rendering in the nether (224 chest blocks total, but rendered as 112 double chests)This is game breaking, and makes old and dedicated worlds harder than ever to play, especially if you have a storage place in the nether, with one chestful of enchanted bows, all in legitimate vanilla survival
I'd like to report a bug (or series of bugs) that occured that led this glitch to be:
I was playing on one of my worlds, and apparently it was updating to the beta (of which I cancelled). It was updating as I was leaving the nether, and then it got stuck in the loading screen. I could hear everything in my base, portal noises, cats, pistons, everything. But never would the screen leave unless I quit minecraft and loaded it back again. I'd like to report that this occurred by doing the following. Keep in mind that this glitch begins when you leave the nether, and persists as such after the update, of which was at the time automatic:Events before glitch
-Have a series of chests with shulker boxes loaded in the nether.
-Have multiple nether portals in the overworld linked to one in the nether.
-Have a lot of furry friends (cats) (18) (Overworld)
-Exit nether whilst game is updating from 1.10 to beta 1.11.0.7
-Have a number of minecart hoppers in overworld (20)
-Have a genuine Xbox One product (not any name brand extensions like X or 4K or S)
-Game is on hard difficulty
-Banners with at least four decorations are in render in each dimension (15)
-Have a number of chests rendering in the nether (224 chest blocks total, but rendered as 112 double chests)This is game breaking, and makes old and dedicated worlds harder than ever to play, especially if you have a storage place in the nether, with one chestful of enchanted bows, all in legitimate vanilla survival
I'd like to report a bug (or series of bugs) that occurred that led this glitch to be:
I was playing on one of my worlds, and apparently it was updating to the beta (of which I cancelled). It was updating as I was leaving the nether, and then it got stuck in the loading screen. I could hear everything in my base, portal noises, cats, pistons, everything. But never would the screen leave unless I quit minecraft and loaded it back again. I'd like to report that this occurred by doing the following. Keep in mind that this glitch begins when you leave the nether, and persists as such after the update, of which was at the time automatic:Events before glitch
-Have a series of chests with shulker boxes loaded in the nether.
-Have multiple nether portals in the overworld linked to one in the nether.
-Have a lot of furry friends (cats) (18) (Overworld)
-Exit nether whilst game is updating from 1.10 to beta 1.11.0.7
-Note that in this situation, I wasnt signed up for the beta and it was updating without me knowing, keep in mind while I was playing on my favorite world.
-Have a number of minecart hoppers in overworld (20)
-Have a genuine Xbox One product (not any name brand extensions like X or 4K or S)
-Game is on hard difficulty
-Banners with at least four decorations are in render in each dimension (15)
-Have a number of chests rendering in the nether (224 chest blocks total, but rendered as 112 double chests)This is game breaking, and makes old and dedicated worlds harder than ever to play, especially if you have a storage place in the nether, with one chestful of enchanted bows, all in legitimate vanilla survival
Exiting nether portal causes Overworld to load, but not leave loading screen. (1.11.0.7 Beta)
I'd like to report a bug (or series of bugs) that occurred that led this glitch to be:
I was playing on one of my worlds, and apparently it was updating to the beta (of which I cancelled). It was updating as I was leaving the nether, and then it got stuck in the loading screen. I could hear everything in my base, portal noises, cats, pistons, everything. But never would the screen leave unless I quit minecraft and loaded it back again. I'd like to report that this occurred by doing the following. Keep in mind that this glitch begins when you leave the nether, and persists as such after the update, of which was at the time automatic:Events before glitch
-Have a series of chests with shulker boxes loaded in the nether.
-Have multiple nether portals in the overworld linked to one in the nether.
-Have a lot of furry friends (cats) (18) (Overworld)
-Exit nether whilst game is updating from 1.10 to beta 1.11.0.7
-Note that in this situation, I wasnt signed up for the beta and it was updating without me knowing, keep in mind while I was playing on my favorite world.
-Have a number of minecart hoppers in overworld (20)
-Have a genuine Xbox One product (not any name brand extensions like X or 4K or S)
-Game is on hard difficulty
-Banners with at least four decorations are in render in each dimension (15)
-Have a number of chests rendering in the nether (224 chest blocks total, but rendered as 112 double chests)This is game breaking, and makes old and dedicated worlds harder than ever to play, especially if you have a storage place in the nether, with one chestful of enchanted bows, all in legitimate vanilla survival
Deleted because it was labelled as duplicate based on title, rather than actually the content and the specific bug in question.
Exiting nether portal causes Overworld to load, but not leave loading screen. (1.11.0.7 Beta)Deleted
Deleted because it was labelled as duplicate based on title, rather than actually the content and the specific bug in question.
I'd like to report a bug (or series of bugs) that occurred that led this glitch to be:
I was playing on one of my worlds, and apparently it was updating to the beta (of which I cancelled). It was updating as I was leaving the nether, and then it got stuck in the loading screen. I could hear everything in my base, portal noises, cats, pistons, everything. But never would the screen leave unless I quit minecraft and loaded it back again. I'd like to report that this occurred by doing the following. Keep in mind that this glitch begins when you leave the nether, and persists as such after the update, of which was at the time automatic:Events before glitch
-Have a series of chests with shulker boxes loaded in the nether.
-Have multiple nether portals in the overworld linked to one in the nether.
-Have a lot of furry friends (cats) (18) (Overworld)
- Exit nether whilst game is updating from 1.10 to beta 1.11.0.7
-Have a number of minecart hoppers in overworld (20)
-Have a genuine Xbox One product (not any name brand extensions like X or 4K or S)
-Game is on hard difficulty
-Banners with at least four decorations are in render in each dimension (15)
-Have a number of chests rendering in the nether (224 chest blocks total, but rendered as 112 double chests)This is game breaking , and makes old and dedicated worlds harder than ever to play, especially if you have a storage place in the nether, with one chestful of enchanted bows, all in legitimate vanilla survival
DeletedStuck loading overworld; Faulty Beta 1.11.0.7 Portal Bug
World updated to beta while playing; no notification and world needs to be reverted[Deleted]
Dear Mojang, (Skip to end for "Bug")As I was playing on one of my minecraft worlds; survival, with tons of progress, a mysterious glitch regarding the loading of the overworld from the nether occurred, where it was stuck on the loading screen until you stopped minecraft. In addition to this I realized that minecraft was updating as I was playing on the world. To this, it seemed too soon for an update to be released, for last one was less than a week ago. Confused, I discovered that the game updated to the beta version, of which I had not signed up and did not ask for. After I had realized this, I reloaded the world hastily hoping that the bug with the portal stopped, and it did, but I wasn't in the portal and on the uppermost solid block above the portal. To this, I then stopped playing in frustration to the transportation of items that now would be much slower than normal. The following day I reported the bug, oblivious to the beta update's situation. I looked at the support site seeking to revert it from the beta update, as I wasn't sure if I did this by a mistake. Then I found a message on the sideboard describing the latest tweet from the support division of Mojang, it says:
Mojang Status"A beta build for Xbox One was accidentally sent out to all players regardless if they were on the beta or not. We are working to get this resolved. Please do not open any saved games if you received this build as you will not be able to
open them again until 1.11 releases. -HZ"To my surprise, Mojang did an oopsie this time, not me. When I discovered this, I realized that my world updated to the beta without consent, notification, nor warning. Looking further into the tweet I found that I wouldn't be able to play the world anyway, as it would be reverted back to the original update.
Luckily, no new chunks were generated, and no new items were crafted, meaning the world is still eligible to be reverted back to its prior state, regardless if it damages the worlds state.
I was wondering if you had any tools (world editor) that would be able to change the "world version" variable back to 1.10. I can extract the world file and bundle it up into a .mcworld file from my xbox. I will be using an application (Metro Commander) that is the only xbox microsoft store item that can do it, albeit unintentionally. I would be able to do this myself but unfortunately my home computer hit the bucket, and the safest version of a versatile world editor is windows only.
Bug: MC World updated to accidental beta as I was playing it and wasn't notified of it, Can it be fixed if you supply a world version reverter or just take my world file and edit it back, I only ask your help if you have the utilities that mojang will allow you to use to revert my world file back, I have no other way of doing this, circumstance defines it.
I will acquire the .mcworld file on hand if so, If not I can simply disclose and delete the issue, but it is an issue, as my input was playing on my world and other forces (Beta release incident) led to this outcome, please respond.
Wrongly marked as duplicate, see prior versions minus title.
Faulty 1.11.0.7 Update Updated whilst playing on the world; --> no warning or way to revert world version <--
Faulty 1.11.0.7 Update Updated whilst playing on the world; --> no warning or way to revert world version<--Faulty 1.11.0.7 Update Updated whilst playing on the world; --> no warning or way to revert world version without help
Faulty 1.11.0.7 Update Updated whilst playing on the world; --> no warning or way to revert world version withouthelpFaulty 1.11.0.7 Update Updated whilst playing on the world; --> no warning or way to revert world version without aid
(Note this is in reference to but not declaring the faulty 1.11.0.7 update, do not mark as duplicate)I was playing on one of my heavily played survival worlds when a mysterious portal screen lockup caused me to view the sidebar hub of Xbox. Realizing the game was updating, I hastily quit minecraft, thinking the portal screen lockup was caused by it. What actually happened is the world registered as 1.11.0.7 as it was updating, meaning I had no chance to undo the version update, meaning my world is in a unstable beta and has no backup, and the tweet from Mojang Status was shortly after, meaning, My world was updated without consent as I was playing on it. Is there any way to revert the world version, even through means such as giving you the world and changing the version it displays as. (I can attain the world file from the xbox one)
(Note this is in reference to but not declaring the faulty 1.11.0.7 update, do not mark as duplicate) My question here is if you have the software (world editor) to help me revert the version, as no new chunks or items were generated correlating to the beta update, please help if you can.I was playing on one of my heavily played survival worlds when a mysterious portal screen lockup caused me to view the sidebar hub of Xbox. Realizing the game was updating, I hastily quit minecraft, thinking the portal screen lockup was caused by it. What actually happened is the world registered as 1.11.0.7 as it was updating, meaning I had no chance to undo the version update, meaning my world is in a unstable beta and has no backup, and the tweet from Mojang Status was shortly after, meaning, My world was updated without consent as I was playing on it. Is there any way to revert the world version, even through means such as giving you the world and changing the version it displays as. (I can attain the world file from the xbox one)
This is a duplicate of MCPE-41198. Just a note, but not a Moderator.
Sadly, between versions, such as java and bedrock, the way things are programmed allow certain types of redstone creations to work. Because of the difference in precision and function between Java and Bedrock, certain creations will not work identically to others.
If you built your house on a witch hut, the actual hut doesn't spawn witches, as soon as the witch hut is generated, chunk the structure block was in will be assigned as a witch spawn chunk, it oftentimes spawns on wood, as wood is the witch hut's floor block. If not, I'm just guessing you didn't see the witch coming into the house and additionally, there is no way we could do anything about this unless you have screenshots, video or something else. 9 times out of 10 says this isn't a bug, just a mistake or very sly witch.
Just wait until the world you load up is complete void, and you keep falling into the void forever, and ever, until you peek to attempt to copy the world, but it fails to, then you go into creative, and realize that the world you spend your precious time on is gone forever.
More likely than not this isn't due to experimental mode, looks like you just loaded up a corrupted or empty texture pack. All you need to do it switch back to the standard Minecraft resource packs, reload it, or re-download the texture pack you are using for the world in the settings menu.
Also the bug tracker SPECIFICALLY said to not say things like "Help" or any other gibberish title for a bug.
Your problem is along with most others, look: ticking chunks have been changed, redstone often has a tiny change that affects almost all redstone builds, your bug is along with one of many. The best you could do is provide two clips of different versions of Minecraft, and show how one redstone function has changed, and the other has not.
I looked already and found that no other users have reported this on the bedrock codebase. Thank you for your help in testing out this glitch yourself.
Can confirm for worlds such as ones that were updated from previous versions (releases).
Not too sure about new worlds, will have to try them out.
looks like (my bug reported) for the dragon egg happening twice (the focus was for the dragon being invisible) was fixed (indeed), but now there is no chance of getting a dragon egg nor the sum of exp with it... hm...
Hey oval, I made a Java report for the latest snapshot just minutes ago, could you take a look at it?
Do you have video of the bug occurring or steps to recreate it?
What version was your world at when you played it before opening it to this bug?
What world type is the world you are using?
I can confirm this for console version xbox of minecraft bedrock, though may not always happen, it does occur on books and armor (excluding elytra). The issue is that Feather falling is an enchantment that seems heavily biased towards the output on any eligible enchantment items (armor, book).
Look, just spawn in the mob yourself, and look from the side, you may not have seen that the eyes go to the side too, not all wonky eyed all the way.
Was the mob climbing vines?
Is the mob on the tree or inside the tree?
Did the tree grow as the mob was climbing the vines?
Can you provide a screenshot or video?
If you tried to sleep in the nether, the bed explodes, but it resets your spawnpoint to the world spawn, did this happen?
Your fallen gear also doesn't stay on your player if you respawn with "keepInventory" off.
Did this happen?
I have all achievements excluding one other and the super fuel achievement, I can confirm this for Xbox One, and have been frustrated to the inability to earn this achievement, regardless of how or what world you attempt to earn it on.
Me either, I attempted to do the formatting codes for the Realm name, and it defaulted to the previous name AND locked the realm name. This is frustrating, knowing that I am paying for this, and there is nothing I can do to fix it. I created my own separate issue related to, but regarding the fact that now you cannot even change the Realm name to any name with "§" in it.
This feature works as intended, Bad Omen effect is a increment value that decreases, it can last as long as five minutes or more, and will wear off only if you die or encounter a village, of which a raid will begin.
This still affects versions unto this day (1.9.0+) and should be fixed as it creates large amounts of lag if unattended, and can act as a "booster" or "landmine" due to the knockback.
Whilst double_plant_2 takes up 2 blocks instead of one, the frequency of the drops for it is fourfold, and doesn't quite scale, but the ratio is fixed to a 4:1 ratio for tallgrass to shortgrass, so it seems to be intended.
Can you give the iPad model? I don't know what "this iPad" means if you don't tell me.
If Jay_Wells is seeing this, please recreate the circumstances, note the one I highlight, and please just see if you get similar results, please. I will provide video of the event as to provide just how this event happens, and if it persists.
Might I ask, is there any way a mojang developer could create a simple tool to revert this, as I posted an issue regarding the fact that the same beta update bug happened while I was playing on a world, and that mean't I had no knowledge or chance of being able to revert it.
Try this text with a paragraph break, or any other emoji, if the same font change occurs, this is actually an intended feature. This behavior is because enchantments are affected by text formatting codes, of which when associated with any non minecraft text, default to that font.
this feature is intended, as the zombie is changing, not the armor.
This is a result of the fact that mojang accidentally released a beta update, of which applied to users who didn't sign up for it, and in result causing most players unable to access the realms and any worlds that you and other players start since yesterday to likely be inaccessible until 1.11 update, which is gonna be a hefty period of time.
What if no new chunks were generated during playing? could prove to allow reversion.