Well, the Java version fits better with Minecraft redstone mechanics, but the Pocket Edition had the block first and may use a weak power for a reason.
If the way the cross hair was created was by making a mostly transparent image then adding the cross hair in the corner, the problem is that minecraft will move the field of view depending on the screen size. The cross hair texture is working as intended, as the game renders it from the player's hand. The problem is that the window places the regular cross hair at the center and the texture's cross hair dependent on the player.
This should be marked as works as intended, as there is no bug on Minecraft's part, but instead an issue with player texturings, unless the cross hair texture was created in a different manner then described.
Part of this seems to be a priority level issue. There could be a priority for the wolves to chase skeletons compared to breeding. The chasing skeletons when out of sight could be a separate glitch though.
I just tested in 1.12. Pushing a primed TNT entity north and/or west with water visually shows the TNT going through solid blocks in the same y coordinate. The primed TNT entity will also visually snap back to its actual position. Using a repeating teleport command, the player is not teleported to the entity as it phases through blocks, so it's just a visual glitch. The TNT entity does not phase through the blocks immediately, but instead waits a random interval of time of about 2-3 seconds. The TNT entity cannot change y coordinates it appears. The fuse timer is unaffected by this glitch too.
This isn't a bug. Instead, the command summons the item frame within the block above. Change the command by adding or subtracting 1 from the x or z coordinate. For example: "/summon item_frame ~1 ~1 ~" works in the shown setup. The black item frame comes from the entity being mostly inside the block and the other one looking normal is because it's inside a transparent block. A side view would reveal that there is no 3d shape to the entity on the side the player is viewing the item frames.
If this is correct, this report should be marked as resolved.
Your screenshots are available by finding your .minecraft folder after searching for %appdata% . After opening .minecraft , just open the screenshots folder. We really need a picture.
After some testing, this only creates items when an extended piston with its base is cloned to a second location along with a power source. It doesn't matter if the second piston is powered by a block not being replaced, the piston still drops items. The question is if the arm or the base is the piece getting destroyed and dropping the item. I'd bet the arm.
That's interesting. I doubt it's Minecraft's fault, but instead the computer's. Fixing the problem each time should be as simple as pressing F11 twice.
A) This sounds like a problem with the launcher, not the game. In fact, it's probably actually a problem with your computer setup.
B) This problem would best have gone on a forums page, but I'll do what I can now.
C) Try updating Java.
D) Che k if the file exists at the location described. The file in question is the code which runs Minecraft. Not having it in the right place could be causing problems.
E) Reinstall Minecraft.
I'm betting that one of those folders got moved. Reinstalling Minecraft recreate the needed folder chain. Good luck!
This isn't a bug. If you'd like a fix to this problem, try suggesting it on the reddit page! Another group brought up the same problem. A suggestion of removing lava blocks within a certain pares of the Mansion would fix issues, but only as a suggestion, not a bug fix.
I believe this is not a duplicate of the before mentioned bug, as the bug MC53915 describes TNT as clipping through a block while this bug instead s observes the TNT visually appearing to clip through a block, while it actually remains in place.
How is this proved a duplicate? It appears instead to be related to the two issues, but more information is needed before judging if this is a valid bug or not.
If the creator of this page could add more information, it would be very beneficial. If not, then we'll have to assume that one of the suggested duplicate bugs is a duplicate.
Both mobs that burn in sunlight and mobs hurt by healing potions are the same category of mobs: undead. Undead Nether mobs are just supposed to not be on fire.
I believe the monostable circuit pictured only works if the redstone dust and repeater are switched. The pictured design doesn't work because a monostable circuit needs a one gametick signal and repeaters give a minimum of a two gametick signal.
I think this mostly has to do with the fact that the Ender Dragon is not meant to be renamed. Perhaps the bug is then that the Ender Dragon can be renamed with commands.
Dylan
MC-107756![[Mojang] Brandon Pearce](../../../data/avatars/users/40932.png){kind=small}
Well, the Java version fits better with Minecraft redstone mechanics, but the Pocket Edition had the block first and may use a weak power for a reason.
Also confirmed on ocean exploration maps.
I don't see the issue. Could you elaborate what part of the skin is going transparent?
Should someone then change the status to "resolved"?
If the way the cross hair was created was by making a mostly transparent image then adding the cross hair in the corner, the problem is that minecraft will move the field of view depending on the screen size. The cross hair texture is working as intended, as the game renders it from the player's hand. The problem is that the window places the regular cross hair at the center and the texture's cross hair dependent on the player.
This should be marked as works as intended, as there is no bug on Minecraft's part, but instead an issue with player texturings, unless the cross hair texture was created in a different manner then described.
Part of this seems to be a priority level issue. There could be a priority for the wolves to chase skeletons compared to breeding. The chasing skeletons when out of sight could be a separate glitch though.
This sounds difficult to reproduce. If any good way to reproduce could be provided, this issue might be easier to fix.
What types of items work?
I just tested in 1.12. Pushing a primed TNT entity north and/or west with water visually shows the TNT going through solid blocks in the same y coordinate. The primed TNT entity will also visually snap back to its actual position. Using a repeating teleport command, the player is not teleported to the entity as it phases through blocks, so it's just a visual glitch. The TNT entity does not phase through the blocks immediately, but instead waits a random interval of time of about 2-3 seconds. The TNT entity cannot change y coordinates it appears. The fuse timer is unaffected by this glitch too.
This actually does appear to work as intended. A set of 8 snow layers has almost all the same properties as 1 snow layer.
I can say that with command blocks the chunks still load. I don't know about functions though.
Could polar bears spawn on a different block than grass?
My testing revealed the same results in 1.12.
I was unable to replicate in 1.12 vanilla on a single player world by the second seed of -4589128118707775879. The mansion appeared as normal.
This isn't a bug. Instead, the command summons the item frame within the block above. Change the command by adding or subtracting 1 from the x or z coordinate. For example: "/summon item_frame ~1 ~1 ~" works in the shown setup. The black item frame comes from the entity being mostly inside the block and the other one looking normal is because it's inside a transparent block. A side view would reveal that there is no 3d shape to the entity on the side the player is viewing the item frames.
If this is correct, this report should be marked as resolved.
Your screenshots are available by finding your .minecraft folder after searching for %appdata% . After opening .minecraft , just open the screenshots folder. We really need a picture.
A temporary fix would be to go to "Options...>Video Settings..." then change the GUI scale from Auto to Medium.
This still appears to be a bug though.
After some testing, this only creates items when an extended piston with its base is cloned to a second location along with a power source. It doesn't matter if the second piston is powered by a block not being replaced, the piston still drops items. The question is if the arm or the base is the piece getting destroyed and dropping the item. I'd bet the arm.
That's interesting. I doubt it's Minecraft's fault, but instead the computer's. Fixing the problem each time should be as simple as pressing F11 twice.
Confirmed for 1.12.
Is the minecart just not affected by gravity?
I cannot reproduce without more information. Try detailing better how to create the glitch.
Is this not intended? Any enderman about to be hit with a projectile takes no damage, does not become aggravated, and teleports away.
There's a copy of this issue somewhere else that needs to be redound.
A) This sounds like a problem with the launcher, not the game. In fact, it's probably actually a problem with your computer setup.
B) This problem would best have gone on a forums page, but I'll do what I can now.
C) Try updating Java.
D) Che k if the file exists at the location described. The file in question is the code which runs Minecraft. Not having it in the right place could be causing problems.
E) Reinstall Minecraft.
I'm betting that one of those folders got moved. Reinstalling Minecraft recreate the needed folder chain. Good luck!
This should be placed as a suggestion on reddit. This isn't a bug, but instead a fantastic suggestion.
This isn't a bug. If you'd like a fix to this problem, try suggesting it on the reddit page! Another group brought up the same problem. A suggestion of removing lava blocks within a certain pares of the Mansion would fix issues, but only as a suggestion, not a bug fix.
I think these are copies, but that's not for me to judge: 107399, 110551, 111992, 108285, 108324, 110586, 96998. Sorry about not linking...
This needs to be tested by others to verify. I'll do so soon.
I believe this is not a duplicate of the before mentioned bug, as the bug MC53915 describes TNT as clipping through a block while this bug instead s observes the TNT visually appearing to clip through a block, while it actually remains in place.
Please correct me if I'm wrong.
How is this proved a duplicate? It appears instead to be related to the two issues, but more information is needed before judging if this is a valid bug or not.
If the creator of this page could add more information, it would be very beneficial. If not, then we'll have to assume that one of the suggested duplicate bugs is a duplicate.
Random order of updates to redstone dust still exists in 1.13-Pre4
https://bugs.mojang.com/browse/MC-119754?focusedCommentId=417578&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-417578
Probably a new bug report. Just make sure everyone knows where it links to
Also, this bug still exists in 1.13-pre4
The player can still activate this in survival mode with a duration 3 rocket.
Also, the bug is still active in 1.13-pre4
Can confirm for 1.13-pre4
Can confirm for 1.13-pre4
This appears to be related to
MC-125511This appears to be related to 125495 - https://bugs.mojang.com/projects/MC/issues/MC-125495?filter=allopenissues
Both mobs that burn in sunlight and mobs hurt by healing potions are the same category of mobs: undead. Undead Nether mobs are just supposed to not be on fire.
Oh yeah, I forgot about those. Baby zombies are also the same way. I was wrong then. Thanks for fixing that.
I believe the monostable circuit pictured only works if the redstone dust and repeater are switched. The pictured design doesn't work because a monostable circuit needs a one gametick signal and repeaters give a minimum of a two gametick signal.
Aren't cauldrons, pistons (head and base), and hoppers all partial blocks?
Water particles probably don't show up with this bug because water is no longer really a block and is instead more of just a block tag.
I think this mostly has to do with the fact that the Ender Dragon is not meant to be renamed. Perhaps the bug is then that the Ender Dragon can be renamed with commands.