![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg)
[Mojang] Adrian Östergård
- nighter
- nighter
- Europe/Stockholm
- Yes
- No
WEB-450
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
MC-140117MC-140118
MC-169466
MCPE-16931
duplicates
is duplicated by
duplicates
is duplicated by
Fucking mojang !!!!!!!!!!
Realms loading text has one smaller text-line in German
duplicates
is duplicated by
is duplicated by
relates to
relates to
is duplicated by
is duplicated by
is duplicated by
duplicates
is duplicated by
duplicates
relates to
relates to
is duplicated by
is duplicated by
Maria Lemónduplicates
relates to
relates to
duplicates
is duplicated by
relates to
MCPE-15069
duplicates
is duplicated by
is duplicated by
Minecraft: Windows 10 Edition Beta still crashes!
Are you going to fix the bug for Minecraft: Windows 10 Edition as well or not?
GK, the same thing happens to me over a month. I don't think they are actually aware of the problem we have. I hope they solve the bug ASAP, so we can play Minecraft: Windows 10 Edition again!
I don't think so. My computer name doesn't contain any special characters.
duplicates
is duplicated by
Packed ice produces water when broken in creative
Packed ice produces water when brokenin creative
Transaprent blocks underwater, when viewed underwater, have flowing textureTransparent blocks underwater, when viewed underwater, have flowing texture
relates to
relates to
is duplicated by
duplicates
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Bonemeal-ing any flower gives you the generic dandelion and ploppy flower
This bug makes every flower nonrenewable (limited resource within a limited space) with the exception of the ploppy and dandelion.
To Reproduce, pick any flower except the ploppy then bonemeal the flower.[MCPE Mod] AMAN4700: You must bonemeal an existing flower for this to work.
Update by
This bug makes every flower nonrenewable (limited resource within a limited space) with the exception of the ploppy and dandelion.
To Reproduce, pick any flower except the ploppy then bonemeal the flower.[MCPE Mod] AMAN4700: You must bonemeal an existing flower for this to work.
Update by
This bug makes every flower nonrenewable (limited resource within a limited space) with the exception of the ploppy and dandelion.
To Reproduce, pick any flower except the ploppy then bonemeal the flower.[MCPE Mod] AMAN4700: You must bonemeal an existing flower for this to work.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please, avoid duplicated comments. Post only NEW information regarding this bug.
This bug makes every flower nonrenewable (limited resource within a limited space) with the exception of the ploppy and dandelion.
To Reproduce, pick any flower except the ploppy then bonemeal the flower.[MCPE Mod] AMAN4700: You must bonemeal an existing flower for this to work.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please,avoid duplicated comments. Post only NEW information regarding this bug.
Armour on monsters (zombies, zombie pigmen, skeletons) and their baby variants is not visible, though it applies all effects normally amd drops when the mob is killed. On skeletons, it can still be seen through their ribcages, suggesting that it has been scaled incorrectly.
Original Report: Found this bug on the new update 0.13.1
i added a screenshots belowUPDATE FOR 0.14.0 BETA
Zombie Pigman armor doesn't render properly stillUPDATE FOR 0.15.4
Still affects Pigman, but now StraysUpdate by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.
Creepers, Skeletons and Zombies/Pigman(aggressive) standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't chase the survival player.
Ocelots standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't run from the player.
Cows, Mooshrooms, Sheep, Pigs, Rabbits, and Chickens standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't follow the player when holding feed.
This also affects passive mobs like Villagers, Wolves(aggressive/tamed/untamed), Ocelots(tamed/untamed) and other entities that I did not mention BUT slimes move on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped just fine.Steps to duplicate
- Place either beds, cakes, daylight sensors, enchantment tables, or chests regular or trapped on the ground in a 5x5 area.
- Make sure you are crouching first because these are interactive blocks.
- Spawn an animal or hostile mob in the center. (For example: I spawned an ocelot the ocelot doesn't/can't run away.)
Notice how the mob or animal doesn't move from where you spawned them. They are stuck standing on the interactive blocks forever.Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.
Creepers, Skeletons and Zombies/Pigman(aggressive) standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't chase the survival player.
Ocelots standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't run from the player.
Cows, Mooshrooms, Sheep, Pigs, Rabbits, and Chickens standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't follow the player when holding feed.
This also affects passive mobs like Villagers, Wolves(aggressive/tamed/untamed), Ocelots(tamed/untamed) and other entities that I did not mention BUT slimes move on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped just fine.Steps to duplicate
- Place either beds, cakes, daylight sensors, enchantment tables, or chests regular or trapped on the ground in a 5x5 area.
- Make sure you are crouching first because these are interactive blocks.
- Spawn an animal or hostile mob in the center. (For example: I spawned an ocelot the ocelot doesn't/can't run away.)
Notice how the mob or animal doesn't move from where you spawned them. They are stuck standing on the interactive blocks forever.Update
by[Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.Creepers, Skeletons and Zombies/Pigman(aggressive) standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't chase the survival player.
Ocelots standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't run from the player.
Cows, Mooshrooms, Sheep, Pigs, Rabbits, and Chickens standing on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped don't follow the player when holding feed.
This also affects passive mobs like Villagers, Wolves(aggressive/tamed/untamed), Ocelots(tamed/untamed) and other entities that I did not mention BUT slimes move on beds, cakes, daylight sensors, enchantment tables, and chests regular or trapped just fine.Steps to duplicate
- Place either beds, cakes, daylight sensors, enchantment tables, or chests regular or trapped on the ground in a 5x5 area.
- Make sure you are crouching first because these are interactive blocks.
- Spawn an animal or hostile mob in the center. (For example: I spawned an ocelot the ocelot doesn't/can't run away.)
Notice how the mob or animal doesn't move from where you spawned them. They are stuck standing on the interactive blocks forever.Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.
Dead bush should be flammable, but won't catch fire
We all know that when redstone ore is being mine, step on or just being touch it start glowing which is a block update but the observer block doesn't read this block update which means that the observer doesn't give off a redstone signal and yes i do know how the observer block work. But it does work with other block update but not when the redstone ore block is being updated so it can glow. My phone is a samsung galaxy s4.
List of things not detected by Observer (Keep updated):
- Redstone ore glowing
- Fence Gates activated by redstone.
- Change the daylight sensor.
- Redstone torches changing state
- Reducing snowlayers' height when shot with arrows.
- Growing Cocoa Pods
- Lighting Nether Portal
- Powering Activator Rails
- Placing Redstone Dust
- Activating Weighted Pressure Plates
- Top half of door
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.
We all know that when redstone ore is being mine, step on or just being touch it start glowing which is a block update but the observer block doesn't read this block update which means that the observer doesn't give off a redstone signal and yes i do know how the observer block work. But it does work with other block update but not when the redstone ore block is being updated so it can glow. My phone is a samsung galaxy s4.
List of things not detected by Observer (Keep updated):
- Redstone ore glowing
- Fence Gates activated by redstone.
- Change the daylight sensor.
- Redstone torches changing state
- Reducing snowlayers' height when shot with arrows.
- Growing Cocoa Pods
- Lighting Nether Portal
- Powering Activator Rails
- Placing Redstone Dust
- Piston activating (the body, not the head)
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.
is duplicated by
is duplicated by
Description revised as of 0.15.90.2 rplatham:
When picking up items, the game does not seem to check to see if the stack should be split so that some of it stays on the ground because picking up all of it would overfill the player's inventory.Example to Reproduce
- Fill all slots of your inventory and include two stacks of the same item (for this example, we'll use two full stacks (64) of coal)
- Place some more coal (say 16) in a chest nearby.
- Drop one full stack of coal from your inventory on the ground.
- Go get the 16 coal from the chest.
- Now pick up the full stack of coal from the ground.
- Observe that you now have two full stacks of coal in your inventory and there is no coal on the ground.
I expected that the full stack of coal on the ground would become a stack of 16 coal on the ground since your inventory could only hold 48 more coal.
------------------------------------------------------------------------------------
Old Description
- Add a full stack of some items to a chest
- Add a non-full stack of the same item to your inventory
- Fill all other slots of your inventory with anything else
- Open the chest (Screenshot 1)
- Long-click the item stack in the chest and transfer all of it to your inventory (Screenshot 2)
It works and nothing remains in the chest.
A stack of the remaining items is now stored in an invisible slot of your inventory. (Screenshot 3)It isn't accessible directly, but if you try to send more items of the same type to your inventory from a chest they will stack on it (Visually they disappear but in fact they stack there, the problem doesn't happens when you send the item from a crafting table output, only from a chest)
If the item type is a combustible or something that can be burnt, the "invisible" stack is still available in the furnace UI.
It's not the only case where it happens but it's the easiest to reproduce.
In the screens I managed to make all the wood disappear from my inventory but that wasn't voluntary and I don't know exactly how, the inventory is sometimes a little strange when there are some invisible stacks around... (Screenshot 4)Other way to reproduce by kaleb418:
1. Fill inventory up with random items.
2. Say, for instance, you have a stack of coal in your inventory. Throw out the stack of coal onto the ground.
3. Get another stack of coal in your inventory. Place down a chest. Make sure your inventory is still full, with one stack of coal in your inventory and one stack on the ground.
4. Change game mode to survival.
5. Put some coal in the chest, but still keep some in your inventory so there are no empty slots.
6. Pick up the coal on the ground. It will all go into your inventory, and the remainder of the coal that doesn't go into the visible slot will seemingly disappear.Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
The beam from a beacon is not rendering properly. It is black and has extra black 'edges' around it, and flashes.
Tested on LG Nexus 5 and Samsung TabPro
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
duplicates
is duplicated by
Sometime the mob running/move too fast
Addition by [Mojang] Mega_Spud (Jay Wells)
It seems that mobs generated before the latest update (0.15.90.7) are affected by this, and will move at a much higher speed than normal.Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
The comment section in the bug tracker is only meant for providing additional information regarding a bug report, it's not meant to be used as a forum for discussion. Please see [Mojang] slicedlime's comment on where you can hold discussions.
If you don't respect the rules of the bug tracker, you may be banned.
[Mojang] Adrian Östergård's comment
The bug
In 1.2.5 SSP and before the little wobble to the whole viewport that occurs when you take damage used to indicate the direction the damage came from. As part of the 1.3 client/server merge, this behavior was lost.
Steps to view correct behavior
- Revert to 1.2.5 SSP and start a new creative world
- Build the contraption as shown in the image attachment below
- Fill the dispensers with arrows.
- Exit MC and use NBTExplorer to change the world to survival mode (alternatively play survival until you obtain those items or open a copy of a current world)
- Facing forward, strafe left into the left pressure plate. Arrow will hit you and the viewport will tilt to the right, simulating the head whiplash.
- Facing forward, strafe right into the right pressure plate. Arrow will hit you and the viewport will tilt to the left, simulating the head whiplash.
- Facing forward, walk into the front pressure plate. Arrow will hit you and the viewport will tilt DOWN, simulating being hit in the top of the head by something
- Facing forward, back into the rear pressure plate, Arrow will hit you and the viewport will tilt UP, simulating being hit in the back of the head and having forward whiplash.
- This seemingly "cool aesthetic" actually has real gameplay value because it indicates to fighters where incoming damage is originating from.
- Repeat all steps in latest version (no need to use NBT editors just open to lan with cheat mode to switch gamemode). Notice how the viewport will always tilt right no matter what.
Code analysis (MCP Names)
EntityLivingBase.attackedAtYaw is not synced to the client, causing an animation present in the client to not be correctly rendered.
This bug makes every flower nonrenewable (limited resource within a limited space) with the exception of the ploppy and dandelion.
To Reproduce, pick any flower except the ploppy then bonemeal the flower.
[MCPE Mod] AMAN4700: You must bonemeal an existing flower for this to work.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.
Description revised as of 0.15.90.2 rplatham:
When picking up items, the game does not seem to check to see if the stack should be split so that some of it stays on the ground because picking up all of it would overfill the player's inventory.
Example to Reproduce
- Fill all slots of your inventory and include two stacks of the same item (for this example, we'll use two full stacks (64) of coal)
- Place some more coal (say 16) in a chest nearby.
- Drop one full stack of coal from your inventory on the ground.
- Go get the 16 coal from the chest.
- Now pick up the full stack of coal from the ground.
- Observe that you now have two full stacks of coal in your inventory and there is no coal on the ground.
I expected that the full stack of coal on the ground would become a stack of 16 coal on the ground since your inventory could only hold 48 more coal.
------------------------------------------------------------------------------------
Old Description
- Add a full stack of some items to a chest
- Add a non-full stack of the same item to your inventory
- Fill all other slots of your inventory with anything else
- Open the chest (Screenshot 1)
- Long-click the item stack in the chest and transfer all of it to your inventory (Screenshot 2)
It works and nothing remains in the chest.
A stack of the remaining items is now stored in an invisible slot of your inventory. (Screenshot 3)
It isn't accessible directly, but if you try to send more items of the same type to your inventory from a chest they will stack on it (Visually they disappear but in fact they stack there, the problem doesn't happens when you send the item from a crafting table output, only from a chest)
If the item type is a combustible or something that can be burnt, the "invisible" stack is still available in the furnace UI.
It's not the only case where it happens but it's the easiest to reproduce.
In the screens I managed to make all the wood disappear from my inventory but that wasn't voluntary and I don't know exactly how, the inventory is sometimes a little strange when there are some invisible stacks around... (Screenshot 4)
Other way to reproduce by kaleb418:
1. Fill inventory up with random items.
2. Say, for instance, you have a stack of coal in your inventory. Throw out the stack of coal onto the ground.
3. Get another stack of coal in your inventory. Place down a chest. Make sure your inventory is still full, with one stack of coal in your inventory and one stack on the ground.
4. Change game mode to survival.
5. Put some coal in the chest, but still keep some in your inventory so there are no empty slots.
6. Pick up the coal on the ground. It will all go into your inventory, and the remainder of the coal that doesn't go into the visible slot will seemingly disappear.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Update by [Mojang] Adrian Östergård: This affects multiple mobs.
Affected mobs (keep updated):
- Villager
- Chicken
- Cow
- Pig
- Sheep
- Wolf
- Ocelot
- Mooshroom
- Silverfish
- Spider
- Cave Spider
- Zombie
- Zombie Pigman
Original report: Ocelots will jump up and sit on chests as normal. However, when they jump onto a bed to sit on it, they just keep jumping up and down on it and alternating between sit and stand positions in the air. Playing iOS release.
I'm playing in multiplayer on a MCPE 0.12.1 Server.
I've built a enchantment table and placed it accessible for all.
When the Host enchants an Item, he'll get different enchantments offered afterwards.
When I (Client) enchant items, the enchantment doesn't change afterwards. I can reproduce the same enchantment over and over.
I can abuse the bug to get lots of luck I books, but somehow this isn't what i want...
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Zombie Pig should spawn in the nether portals , but when it happens they disappear instantly. This did not happen until the 0.12.1 Build 7.
I tested the Windows 10 edition and Android 5.0 and both occur this error.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Usually, if you press and hold you are able to extinguish fire. But on the 0.13.0 builds, it won't work on survival.
Update:
As of 0.15.2, this bug affects Android users playing single player or as LAN host. Android Clients connected via LAN are not affected.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
If a snow block in a snowy biome is exposed to the sky, it and any snow blocks beneath it will eventually disappear, the uppermost being replaced by a stack of snow layers. It has been suggested that this occurs only during or after snowfall. This information fits with most current observations, however, they may also be replaced following the unloading/reloading of their chunk.
For ice plains spikes biomes, which generate snow blocks in the place of grass, this happens immediately upon generation (or upon reloading a world last opened prior to 0.12.1).
Shown is a player-built igloo in an ice plains biome (old-type world), before and after the snow blocks were replaced, in addition to a newly generated ice plains spikes biome (infinite world).
All snow blocks in a chunk appear to be ticked at the same moment, assuming the required conditions are met. It also seems as though nearby snow layers are regenerated during any occurence.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
I was trying to build an XOR gate in MCPE, but I came across an issue in which redstone, when powered by a strongly powered adjacent block would not power horizontally adjacent blocks. One configuration in which this happens is attached below.
I could not reproduce this bug in the PC (Java) edition of Minecraft, and I have also attached pictures of it functioning correctly there.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Armour on monsters (zombies, zombie pigmen, skeletons) and their baby variants is not visible, though it applies all effects normally amd drops when the mob is killed. On skeletons, it can still be seen through their ribcages, suggesting that it has been scaled incorrectly.
Original Report: Found this bug on the new update 0.13.1
i added a screenshots below
UPDATE FOR 0.14.0 BETA
Zombie Pigman armor doesn't render properly still
UPDATE FOR 0.15.4
Still affects Pigman, but now Strays
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.
When i was working on my note block song (slowest setting, 3 minecraft ticks.), i pressed the button to chevk my progress. And then, at one point in the song, the redstone repeaters bugged out on me and went on the fastest speed. (1 minecraft tick) and when i checked on the setting of the redstone repeaters at the point where it went bugged out, it was on the slowest (3 ticks), setting. When i pressed the button again, it still went fast. Do you know why it's doing this? (The system is Amazon's newest kindle, Fire 5th generation)
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Some attachable block moved by piston doesn't update anymore, unless if you removed the piston.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
We all know that when redstone ore is being mine, step on or just being touch it start glowing which is a block update but the observer block doesn't read this block update which means that the observer doesn't give off a redstone signal and yes i do know how the observer block work. But it does work with other block update but not when the redstone ore block is being updated so it can glow. My phone is a samsung galaxy s4.
EDIT by Zeb: This bug is not with the observer, which is working fine. The bug is actually with all of the blocks/events listed below, because they actually don't cause block updates at all.
List of things not detected by Observer (Keep updated):
- Redstone ore glowing
- Fence Gates activated by redstone.
- Change the daylight sensor.
- Redstone torches changing state
- Growing Cocoa Pods
- Lighting Nether Portal
- Powering Activator Rails
- Placing Redstone Dust
- Piston activating (the body, not the head)
- Snow Layer Created by Snow Golem
- Water/lava flowing (referring to the liquid that is already there not receiving a block update when it spreads)
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicated comments. Post only NEW information regarding this bug.
What I expected to happen was...
On flicking the power switch in each example, the blue example shown would fire like the red example shown (end repeater lights up).
What actually happened was...
In the blue example, the output repeater doesn't fire. If you rapidly flick the switch back and forth, the blue repeater fires intermittently.
Steps to reproduce:
- Drive redstone current into a block on top of a piston to generate a 1-tick pulse (red example). Position a repeater to pick up the current from the piston block, but the redstone should flow directly from power source to the block.
- Turn on the power source; the piston will fire and the output repeater will light up for its pulse duration.
- Insert a repeater anywhere along the input line and toggle the power source. the output repeater will not fire.
- Rapidly toggle the power source (switch works best). The repeater will occasionally fire.
- replacing the relay with redstone torch inverters shows the same issue (the mechanism will fire when the torch is placed, but not when the mechanism is toggled).
- Using an observer block as the power source showed the same issue.
Minecraft pocket edition 0.15.0 (iOS - replicated on iPhone 6 and iPad air 2)
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Update by [Mojang] Tomas Alaeus, explaining the cause of the bug
Repeaters don't apply the delay properly in all cases. If the repeater was activated by another pure redstone component being ticked, then the delay will be correct. However, if it was activated by a world change (lever, piston modifying a circuit, pressure plates, buttons, etc) then the repeater will output a signal 1 tick too fast. A 1-delay repeater will act as a 0-delay repeater (that is, completely ignored). A 3-delay repeater will act as a 2-delay repeater.
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
The beam from a beacon is not rendering properly. It is black and has extra black 'edges' around it, and flashes.
Tested on LG Nexus 5 and Samsung TabPro
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Sometime the mob running/move too fast
Addition by [Mojang] Mega_Spud (Jay Wells)
It seems that mobs generated before the latest update (0.15.90.7) are affected by this, and will move at a much higher speed than normal.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
[Mojang] Adrian Östergård This also affects buttons, levers, tripwire hook and Redstone torch. This also works as intended? It's a bit strange but cool.
[Mojang] Adrian Östergård, as of 16w44a, the decision to make Java edition observers output activation power instead of strong power has been reverted, and observers in the Java edition now once again output strong power.
Should this issue be reopened? Changing MCPE observers to work differently wouldn't break any flying contraptions, since observers already act as if they powered pistons through blocks because of MCPE-16286.
So changing observers to output strong power would NOT break most flying contraptions, since the Java-edition behavior is already happening (when it comes to pistons) in MCPE because of a bug.
In 0.17.1 beta (aka 1.0.0) in the creative menu the dragon appears invisible, i have attached an image for proof that this glitch is real
Update by [Mojang] Adrian Östergård
This bug affects all heads (Steve, Creeper, Zombie, Wither Skeleton, Skeleton and Dragon Head).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
As said in Title. Either WiFi or Celluar Data makes game run correctly in such situation. Logging out from XBox also stops crash.
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
![[MCPE Mod] Dr.Awesome4333](../../../data/assets/gravatar/drawesome4333.png){kind=small}
Thanks for the report, however this has been reported before as MCPE-21210 which is currently working as intended. Please read [Mojang] Adrian Östergård's comment on that ticket for why it is working as intended. In the future, please search before reporting bugs as it is likely that someone else may have reported it before.
[Mojang] Adrian Östergård Isn't this rather a "Won't fix"?
This is fixed in a very sneaky way [1]: The achievement is now "Kill a Skeleton from more than 50 meters away" - it doesn't say anymore with what weapon...
See https://crowdin.com/translate/minecraft/9389/enus-de#5171353
[1] [Mojang] Adrian Östergård: I saw what you did there
@[Mojang] Adrian Östergård, yes but anyway. It is fixed in 1.13-pre6. 
[Mojang] Adrian Östergård, you removed 1.13-pre6 from the Fix versions list.
Working as Intended because of this comment from MC-126085; by [Mojang] Agnes Larsson (and [Mojang] Adrian Östergård):
Invisible players will still get hurt by inflated puffer fishes if they get too close, that's WAI.
![[Mod] Sonicwave](../../../data/avatars/users/94627.png){kind=small}
This is considered intentional; see MC-146256 (which was resolved as "Works as Intended" by [Mojang] Adrian Östergård).
[Mojang] Adrian Östergård I absolutely agree with Fabian Röling and also want to state that this is an inconsistency.
If this bugpost would have been resolved as WAI without giving any reason, I would have assumed something which is intel I've gotten several years ago though.
Back then I asked a dev regarding textures such as foliage, (custom) sky, environment etc., and he wrote something along the lines of, that some things related to texturepacks would require a massive rewrite. That he actually already tried to implement something which is currently hardcoded, but it didn't work out with that code base (don't nail me down 100% to those words, it's saved similar like this in my memory, I mainly recall that he wanted to give texturepack makers more possibilities, but it was not possible at that time).
From what I know so far about this bugtracker, is, that in some cases "works as intended" can also mean something like "we can't currently do this, it may be fixed one day, it also might not be on the top of our priority list, and it may very well be that, if it will be possible one day, it may not be in the format this bugpost refers to, so we might as well close it, and as we must not reveal specific future plans for Minecraft to the public, we sadly can't tell you that this will be possible one day.", but this is apparently not the case here by closing the bugpost as a "feature request".
To emphasize again: Closing this bugpost as a feature request seems wrong, as it's also for me an inconsistency.
I am aware that since the acquisition by Microsoft, plans may have changed tremendously, which is not the Devs' fault, but, regardless, I want to link again a Redditpost by Mr. Broes:
https://www.reddit.com/r/Minecraft/comments/66gcg9/comment/dgiy1xb
It would be very kind of you, Mr. Östergård, to ask the developer who would be currently responsible for theoretically implementing it into Vanilla, so you could re-evaluate to possibly leave this bugpost open, or, if you are allowed to, to give us any intel about future plans regarding this.
Thank you!
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
Fabric basically does what Forge does, but since they work differently internally, Forge mods nor Forge itself are not compatible with it, unless the mod author explicitly provides a Fabric version (which essentially means writing everything twice, so it's understandable that many authors choose to not be doing that).
There is also things like OptiFabric which somehow makes OptiFine compatible with Fabric.
Installing Fabric is as easy as it as for Forge. Just download the version for the vanilla launcher and run it. The setup will install Fabric and create a new profile/installation in your launcher.
Also, [Mojang] Adrian Östergård just set the priority of this ticket to important, so fingers crossed they fix it during the 1.15 snapshot phase 
The light will shine through glass cubes and damage the mobs. [Mojang] Adrian Östergård
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
WAI as per [Mojang] Adrian Östergård's comment in MC-170900.
Nylium and the vines are supposed to work without Silk Touch.
"A hypha is a single strand of material. The blocks are definitely hyphae, a dense mass of many strands." - [Mojang] Adrian Östergård
[Mojang] Adrian Östergård made a comment on MC-147516 that these issues relating to the attack ranges of mobs could be related to this issue.
I attempted to make an individual issue to the bug shown in the video. MC-184710
If you think that this issue does not address the above, you should reopen my issue. Now that it seems this issue might be fixed in 1.16 (It was assigned to Searge 4 hours ago) you might as well get to fixing the issue in the videos as its very similar.
[Mojang] Adrian Östergård This is not about world generation, it's about bonemeal/randomTick.
We only accept parity issues as of Buzzy Bees or later.
[Mojang] Adrian Östergård stated this at MC-182668.
This will stay as "Works As Intended" unless the rules for parity change or if this gets added.
Endermen can spawn in the Nether for a long time; and the warped forest is supposed to be a place where only endermen can spawn.
Endermen started invading another dimension, no idea what they are up to
https://www.mojang.com/2016/05/minecraft-snapshot-16w20a/
See also this comment by [Mojang] Adrian Östergård.
@[Mojang] Adrian Östergård so, this will occur even worlds that weren't open in 28a, but will be opened in, for example, 20w29a?
[Mojang] Adrian Östergård just curious on why this one is WAI when MC-194396 isn't?
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
This is intentional based on a message by [Mojang] Adrian Östergård in the Mojira Discord.
@[Mojang] Adrian Östergård all done.
[Mojang] Adrian Östergård I choose you!!
[Mojang] Adrian Östergård you're up!
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
[Mojang] Adrian Östergård, this ticket is describing the odd smooth lighting behavior that produces shadows in illogical places. For example, in one of the screenshots attached to this report (MC-95515.png), you can see that shadows are produced right beside some light sources, and this doesn't make much sense, as a light source is present, therefore no shadow should be produced. I hope this helps clears any confusion. Also can confirm that this issue is present in 21w05b.
Assigned [Mojang] Adrian Östergård since he is the author of the blog post.
Duplicate of MC-220690, which was later resolved as invalid. See [Mojang] Adrian Östergård's comment on that ticket.
Duplicate of MC-214816, which was later resolved as invalid. See [Mojang] Adrian Östergård's comment on this ticket for an explanation.
The Bug:
The word "ingot" within the "Serious Dedication" advancement description is improperly capitalized.
This word should indeed be capitalized as stated in this comment by [Mojang] Adrian Östergård.
This report was created based on this comment by [Mojang] Adrian Östergård.
| Translation Key | Current String | Expected String |
|---|---|---|
| advancements.husbandry.netherite_hoe.description | Use a Netherite ingot to upgrade a hoe, and then reevaluate your life choices | Use a Netherite Ingot to upgrade a hoe, and then reevaluate your life choices |
Steps to Reproduce:
- Change your language to English, United States (EN_US), if you haven't already.
- Revoke and grant this particular advancement from yourself.
/advancement revoke @s only minecraft:husbandry/obtain_netherite_hoe /advancement grant @s only minecraft:husbandry/obtain_netherite_hoe
- Hover over the purple "[Serious Dedication]" text displayed in the chat.
- Take note as to whether or not the word "ingot" within the "Serious Dedication" advancement description is improperly capitalized.
Observed Behavior:
The word "ingot" within the "Serious Dedication" advancement description is improperly capitalized.
Expected Behavior:
The word "ingot" within the "Serious Dedication" advancement description would be capitalized. It should be "Ingot" instead of "ingot".
The Bug:
The "Bullseye" advancement description is improperly capitalized.
Description:
The word "block" within the "Bullseye" advancement description isn't capitalized. This word should indeed be capitalized as stated in this comment by [Mojang] Adrian Östergård.
| Translation Key | Current String | Expected String |
|---|---|---|
| advancements.adventure.bullseye.description | Hit the bullseye of a Target block from at least 30 meters away | Hit the bullseye of a Target Block from at least 30 meters away |
Steps to Reproduce:
- Change your language to English, United States (EN_US), if you haven't already.
- Revoke and grant this particular advancement from yourself.
/advancement grant @s only minecraft:adventure/bullseye /advancement revoke @s only minecraft:adventure/bullseye
- Hover over the purple text displayed in the chat.
→
Notice how the "Bullseye" advancement description is improperly capitalized.
Information:
This report was created based on this comment by [Mojang] Adrian Östergård.
Link to this particular crowdin string: https://crowdin.com/translate/minecraft/9435/enus-engb#5226300
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
According to [Mojang] Adrian Östergård in this comment, in-game names such as "Bee Nest" and "Glass Bottle" should be capitalized, so Avoma's strings are correct. Except the "Light as a Rabbit" advancement should be "Walk on Powder Snow... without sinking in it", with a space after the ellipsis, to be consistent with the "Tactical Fishing" advancement (MC-226454).
Duplicate of MC-214816, which was later resolved as invalid. See [Mojang] Adrian Östergård's comment on this ticket for an explanation.
Duplicate of MC-223975 which was later resolved as invalid. For more information regarding this issue, see this comment by [Mojang] Adrian Östergård on the parent ticket.
[Mojang] Adrian Östergård, those villages are still at edges, the edge is with a biome variant of the biome that the village generates in, for example: desert next to desert hills or savannas next to savanna plateaus.
Can confirm this in 21w39a. Here are some extra details regarding this problem.
The Bug:
The words "honey" and "block" within the "Sliding down a honey block" subtitle are improperly capitalized.
These words should indeed be capitalized as stated in this comment by [Mojang] Adrian Östergård.
Steps to Reproduce:
- Ensure that you have subtitles enabled in your accessibility settings.
- Play the "minecraft:block.honey_block.slide" sound.
/playsound minecraft:block.honey_block.slide master @a
- Look at the subtitles overlay and pay close attention to the "Sliding down a honey block" subtitle.
Observed Behavior:
The words "honey" and "block" within the "Sliding down a honey block" subtitle are improperly capitalized.
Expected Behavior:
The words "honey" and "block" within the "Sliding down a honey block" subtitle would be capitalized. Instead, the subtitle should be "Sliding down a Honey Block" and not "Sliding down a honey block".
This is intended see comment by [Mojang] Adrian Östergård here
[Mojang] Adrian Östergård moved this report from the Minecraft: Java Edition project to the Minecraft Launcher project, so it must be something that will need to be fixed on the launcher side. Additionally, the report has been assigned an ADO number, meaning the launcher developers are tracking the issue internally.
aceplante: [Mojang] Adrian Östergård mentioned that there are no expectations given for cave air, which appears to mean that we should not expect cave air to be used in any manner other than how it currently is used. (It's not considered a bug by the developers.)
Not a bug. It is considered a feature request for Feedback and Suggestions per [Mojang] Adrian Östergård.
This is a feature request, stated by [Mojang] Adrian Östergård in the linked issue.
Reports can be marked as a duplicate of reports that are WAI. In this case, see [Mojang] Adrian Östergård's comment on the parent report for why it was resolved as such.
This ticket is very difficult to comprehend, please use the Bug Report Guidelines here when posting issues.
This was reported for a test and fix.
Reported for a fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
I can not reproduce this. Could you please provide a seed?
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for a fix.
Reported for test and fix.
Reported for test and fix.
Reported for a fix.
Reported for test and fix.
Does this happen with all chests or is it just with the specific configuration as shown in the screenshot? Please elaborate as much as possible as to when this occurs.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Could you please check which time format you're using on your device? If you're using the 12-hour format, please change to the 24-hour format and then try again.
Please respond and add the current version if you can reproduce this issue. If you can reproduce, please also provide details about the issue you are experiencing using the Bug Report Guidelines Here.
Reported for test and fix.
Please respond and add the current version if you can reproduce this issue.
Please respond and add the current version if you can reproduce this issue.
Reported for test and fix.
Reported for a fix.
Please respond and add the current version if you can reproduce this issue.
This ticket is incomplete, please open a new ticket and provide details about the issue you are experiencing using the Bug Report Guidelines Here.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Please respond and add the current version if you can reproduce this issue.
Please respond and add the current version if you can reproduce this issue.
Please respond and add the current version if you can reproduce this issue.
Reported for test and fix.
Reported for test and fix.
Reported for review.
Reported for review.
Reported for review and fix.
Reported for test and fix.
Reported for test and fix.
Seed -511137450 is a Mesa Plateau F (http://i.imgur.com/bRy7q5k.jpg).
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
Please respond and add the current version if you can reproduce this issue.
Reported for test and fix.
Reported for test and fix.
Reported for test and fix.
This ticket is incomplete, please open a new ticket and provide details about the issue you are experiencing using the Bug Report Guidelines Here.
This site is for bug reports only. For feature suggestions or changes please see: Minecraft Suggestions on Reddit.
Reported for review and fix.
Reported for test and fix.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please update affected versions if this bug still occurs.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This was fixed in a future release, which means that it's currently not fixed, but that it will be fixed in a future version.
Are you saying that there's an issue with any of these items, or do you want to make a suggestion? For suggestions, please go to our feedback site.
Please reply and update affected version(s) if the issue still exists.
This bug has been reported to our internal bug tracker for further testing and a fix.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
We could not reproduce this issue. Please add step by step instructions on how to reproduce.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Duplicate of
MCPE-17040– If you have not, please use the search function in the future, to see if your bug has already been submitted.This ticket is incomplete, please open a new ticket and provide details about the issue you are experiencing using the Bug Report Guidelines Here.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This ticket is incomplete, please open a new ticket and provide details about the issue you are experiencing using the Bug Report Guidelines Here.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Duplicate of
MCPE-17040– If you have not, please use the search function in the future, to see if your bug has already been submitted.This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Closed in favour of
MCPE-17069which is contains several other mobs (including the Wither)This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
Alex Sebastian: What device are you using? Please be as specific as possible.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please note that this bug has been reported to our internal bug tracker for further testing and a fix, and the developers are aware it. It is scheduled to be fixed in one of the future updates (no specific date can be provided). Additionally, post only NEW information regarding this bug. This is not a forum for discussion.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please note that this is not a discussion forum. Post only NEW information regarding this bug. This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided). .
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This is working as intended.
MC-107749was incorrectly resolved.This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This ticket is incomplete, please open a new ticket and provide details about the issue you are experiencing using the Bug Report Guidelines Here.
This ticket is incomplete, please open a new ticket and provide details about the issue you are experiencing using the Bug Report Guidelines Here.
This ticket is incomplete, please open a new ticket and provide details about the issue you are experiencing using the Bug Report Guidelines Here.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
As with
MC-107749,MC-107783was incorrectly resolved.This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Joe barnes Are you able to reproduce this in the latest Minecraft beta build on Android (0.15.90.8)?
Bug reports are only accepted in English, sorry. If you speak English, feel free to create a new ticket.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply if you're still able to reproduce this issue in the latest beta build (0.15.90.8)
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
Duplicate of
MCPE-17442– If you have not, please use the search function in the future, to see if your bug has already been submitted.This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
In Minecraft: Pocket Edition/Win10 Edition, this is working as intended.
I've marked this as duplicate and added this to the list in
MCPE-14710.This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.
You're able to create old worlds in 0.15.90.8, and you're able to convert them into infinite worlds. The crash you're mentioning would be a different bug, so please make a new report for that issue using the Bug Report Guidelines Here.
Please reply and update affected versions if you're still able to reproduce this issue.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please reply and update affected versions if you're still able to reproduce this issue.