In the environment section, put your PC specs, like from a crash report, and don't just put something like "This really happened, they just spawn constantly"
Well, this would be hard to solve, but it won't be because they don't really care if a minor glitch happens at that amplifier. Considering that with this effect you don't fall at all, and also considering that damage actually causes the player to go up, almost like jumping, the fact that you go up and don't fall back down is expected. I know it's annoying, but technically the fact that level 255 does what it does should be considered a glitch, and, as such, they won't fix the glitch caused while under a glitch.
As cool as that would be, FVbico is correct, they are intended to act like a solid block and have different collision mechanics. While normal mobs slightly push you and you slightly push them, shulkers won't be pushed and don't push you, they just stop you. Because the collision rule applies to the normal mob pushing mechanic, it doesn't affect the shulker.
We need all the information from the crash log, not just a bit of the console output. What are the specs of your computer? How much dedicated RAM do you have?
If your language calls the shovel a spade and the server's (if you're on a server) calls it shovel, it would be like renaming it to the exact same thing, which Minecraft avoids, usually so that when combining tools, ect. you're not also renaming it if you don't want to.
The environment field is for your computer environment, such as OS and hardware, not for where in-game the bug happened. You also should be more specific about the issue and try to find the items or check the log and things like that. There is simply not enough information to work with, please be more specific and check to see if it actually is a bug first before reporting it.
This is caused because the item is losing durability. When ever the selected item changes, such as switching to a different item, changing it's nbt data, or changing the data/damage value, Minecraft will run the raising-an-item animation you see when switching items. You should update this report to the issue that damaging tools plays the animation. Also, the reason people don't take damage while blocking is because that was added as a feature.
In order to figure out the issue and how to fix it, you must attach a crash log. Also, try to see if it's some other problem that can be easily fixed before reporting it as a Minecraft bug when it may not be.
This is due to quasi-connectivity: Pistons can be powered by blocks 2 blocks above them, such as the redstone block it's pushing. This used to be unintended, but the redstone community used it for so many things that Mojang kept it to keep redstone machines working. While this is unintended, it will not be fixed because it will break many other things.
Then you'd have to make every block a tile entity, which is unfeasible. I believe using CanPlaceOn:[] lets you interact with the block, although that requires an item to be held.
The firework stays attached to the player even after death/landing from my testing. This is obvious when giving yourself a firework with flight duration 127 (/give @s minecraft:firework_rocket{Fireworks:{Flight:127}}). This also occurs in 1.12.2.
The armor stand is probably in unloaded chunks, try loading the chunks (just move the player where the armor stand is) and see if the command succeeds then.
I'm pretty sure the item does not retain any of the NBT of the item frame so it would not retain the potion effects either. Maybe edit your datapack to make item frames invulnerable.
Conner McKay
MC-94455
I used code from a generator too, you'd think it would work, but no...
I've also noticed that if you put nothing in the Text1 (such as Text1:"") it doesn't do this
I've noticed this with more than just torches, it also affects blocks
In the environment section, put your PC specs, like from a crash report, and don't just put something like "This really happened, they just spawn constantly"
Well, this would be hard to solve, but it won't be because they don't really care if a minor glitch happens at that amplifier. Considering that with this effect you don't fall at all, and also considering that damage actually causes the player to go up, almost like jumping, the fact that you go up and don't fall back down is expected. I know it's annoying, but technically the fact that level 255 does what it does should be considered a glitch, and, as such, they won't fix the glitch caused while under a glitch.
In the environment, please add more specs about your computer than just it's operating system, as these factors can affect processes.
As cool as that would be, FVbico is correct, they are intended to act like a solid block and have different collision mechanics. While normal mobs slightly push you and you slightly push them, shulkers won't be pushed and don't push you, they just stop you. Because the collision rule applies to the normal mob pushing mechanic, it doesn't affect the shulker.
1.9 changes certain NBT tags, causing the pig spawners and empty chests.
That is a modded server, please contact the server owner or support to fix the issue.
This may be a server problem, and, if so, it is invalid because it is a modded server.
You need at least 2GB from my experience and you may need to change some server properties and gamerules so it doesn't have to process as much.
They won't fix it... there is no good reason to... facepalm
Well, it seems that there is an error connecting to the authentication servers and then it lags for 2.5 seconds
Can confirm for 1.10
I'm not exactly a tech expert, but I don't think this is very good, "Dedicated Memory: 64 MB"
1) You should explain the bug as best as possible on the bug tracker even if you have a video. 2) The video is not linked in your report
We need all the information from the crash log, not just a bit of the console output. What are the specs of your computer? How much dedicated RAM do you have?
If your language calls the shovel a spade and the server's (if you're on a server) calls it shovel, it would be like renaming it to the exact same thing, which Minecraft avoids, usually so that when combining tools, ect. you're not also renaming it if you don't want to.
Can you force a crash by holding (Fn) F3 + C for 10 seconds and attach the crash report so that we can get more information?
I'm pretty sure that this was intentional, but if you don't like it you can change it with a resource pack (if you can find one)
English please
Applies to any entity with a player passenger
Please provide a crash log
The environment field is for your computer environment, such as OS and hardware, not for where in-game the bug happened. You also should be more specific about the issue and try to find the items or check the log and things like that. There is simply not enough information to work with, please be more specific and check to see if it actually is a bug first before reporting it.
This is caused because the item is losing durability. When ever the selected item changes, such as switching to a different item, changing it's nbt data, or changing the data/damage value, Minecraft will run the raising-an-item animation you see when switching items. You should update this report to the issue that damaging tools plays the animation. Also, the reason people don't take damage while blocking is because that was added as a feature.
In order to figure out the issue and how to fix it, you must attach a crash log. Also, try to see if it's some other problem that can be easily fixed before reporting it as a Minecraft bug when it may not be.
This is due to quasi-connectivity: Pistons can be powered by blocks 2 blocks above them, such as the redstone block it's pushing. This used to be unintended, but the redstone community used it for so many things that Mojang kept it to keep redstone machines working. While this is unintended, it will not be fixed because it will break many other things.
Then you'd have to make every block a tile entity, which is unfeasible. I believe using CanPlaceOn:[] lets you interact with the block, although that requires an item to be held.
I don't believe this is a bug
WAI, they won't fix this because that spawning works on random ticks and it would be to complicated and unnecessary to change it for this case.
This is probably due to render distance fog
The firework stays attached to the player even after death/landing from my testing. This is obvious when giving yourself a firework with flight duration 127 (/give @s minecraft:firework_rocket{Fireworks:{Flight:127}}). This also occurs in 1.12.2.
More information please
WAI
Could you attach the crash log?
Duplicate of
MC-102641Is there a water source block below the flowing water? If I remember correctly water sources cannot form on top of flowing water.
Seems related to
MC-190598Seems related to
MC-190576The armor stand is probably in unloaded chunks, try loading the chunks (just move the player where the armor stand is) and see if the command succeeds then.
I'm pretty sure the item does not retain any of the NBT of the item frame so it would not retain the potion effects either. Maybe edit your datapack to make item frames invulnerable.
It seems likely they spawned during chunk population.