Salasana
- Salasana
- salasana
- Europe/Helsinki
- Yes
- No
Confirmed for 1.14.3. It also happens inside buildings and when placing down glass blocks, so maybe lighting isn't to blame after all. Even opening a door causes a slight lag spike. My map is unplayable in survival because of this bug, so I'm hoping something will be done about it at some point.
Edit: Nevermind, I tested breaking and placing blocks in a completely sealed off space, and there was no lag. It must have something to do with lightning updates, now I'm 99% sure.
The ender dragon used to occasionally swoop down to melee attack the player. Now it doesn't seem to do that anymore. This makes the boss fight a lot easier, as the only thing you have to look out for is the dragon's breath.
I am not referring to the dragonlandingon its nest, which works correctly.The ender dragon used to occasionally swoop down to melee attack the player. Now it doesn't seem to do that anymore. This makes the boss fight a lot easier (even a bit boring), as the only thing you have to look out for is the dragon's breath.
Based on my tests, this bug has existed ever since the dragon fight was revamped in 1.9. It did hit me a couple of times in the 1.9 test, but that might have just been coincidence. In 20w12a it didn't hit me once, except when it took off from the nest.
To clarify: I am not talking about the dragon swooping down to land on its nest, which works correctly.
The ender dragon used to occasionally swoop down to melee attack the player. Now it doesn't seem to do that anymore. This makes the boss fight a lot easier (even a bit boring, especially when you run out of arrows), as the only thing you have to look out for is the dragon's breath.
Based on my tests, this bug has existed ever since the dragon fight was revamped in 1.9. It did hit me a couple of times in the 1.9 test, but that might have just been coincidence. In 20w12a (and later) it didn't hit me even once, except when it took off from the nest.
I tested this on Bedrock edition too, and there the dragon hit me quite a lot. It didn't swoop down like in Java 1.8, but it clearly targeted me many times, usually when I was climbing the obsidian pillars and high enough for it to be able to hit me. So as well as this probably being unintended and a bug, it seems to be a parity issue also.
To clarify: I am not talking about the dragon swooping down to land on its nest, which works correctly.
The ender dragon used to occasionally
swoopdown to melee attack the player. Now it doesn't seem to do that anymore. This makes the boss fight a lot easier (even a bit boring, especially when you run out of arrows), as the only thing you have to look out for is the dragon's breath.Based on my tests, this bug has existed ever since the dragon fight was revamped in 1.9. It did hit me a couple of times in the 1.9 test, but that might have just been coincidence. In 20w12a (and later) it didn't hit me even once, except when it took off from the nest.
I
tested this on Bedrock edition too, and there the dragon hit me quite a lot. It didn't swoop down like in Java 1.8, but it clearly targeted me many times, usually when I was climbing the obsidian pillars and high enough for it to be able to hit me. So as well as this probably being unintended and a bug, it seems to be a parity issue also.To clarify: I am not talking about the dragon swooping down to land on its nest, which works correctly.
The ender dragon used to occasionally dive down to melee attack the player. Now it doesn't seem to do that anymore. This makes the boss fight a lot easier (even a bit boring, especially when you run out of arrows), as the only thing you have to look out for is the dragon's breath.
Based on my tests, this bug has existed ever since the dragon fight was revamped in 1.9. It did hit me a couple of times in the 1.9 test, but that might have just been coincidence. In 20w12a (and later) it didn't hit me even once, except when it took off from the nest. A clear difference when compared to 1.8 and earlier, where the dragon would align itself towards the player and then start diving.
I've also paid attention to this in gameplay videos on the internet, and I haven't seen the dragon dive in any of them.
(This might be a different problem, but I tested this on Bedrock edition too, and there the dragon hit me quite a lot. It didn't swoop down like in Java 1.8, but it clearly targeted me many times, usually when I was climbing the obsidian pillars and high enough for it to be able to hit me. So this seems to be a parity issue also.)
To clarify: I am not talking about the dragon swooping down to land on its nest, which works correctly. In the Wiki (which of course isn't perfect) this is referred to as the diving state.
Ender dragon doesn't swoop down towards the playeranymoreEnder dragon doesn't swoop down towards the player (dive mechanic broken)
The ender dragon used to occasionally dive down to melee attack the player. Now it doesn't seem to do that anymore. This makes the boss fight a lot easier (even a bit boring, especially when you run out of arrows), as the only thing you have to look out for is the dragon's breath.
Based on my tests, this bug has existed ever since the dragon fight was revamped in 1.9. It did hit me a couple of times in the 1.9 test, but that might have just been coincidence. In 20w12a (and later) it didn't hit me even once, except when it took off from the nest. A clear difference when compared to 1.8 and earlier, where the dragon would align itself towards the player and then start diving.
I've also paid attention to this in gameplay videos on the internet, and I haven't seen the dragon dive in any of them.
(This might be a different problem, but I tested this on Bedrock edition too, and there the dragon hit me quite a lot. It didn'tswoop downlike in Java 1.8, but it clearly targeted me many times,usually when I was climbing the obsidian pillars andhighenough for it to be able to hit me. So this seems to be a parity issue also.)To clarify: I am not talking about the dragon swooping down to land on its nest, which works correctly. In the Wiki (which of course isn't perfect) this is referred to as the diving state.
The ender dragon used to occasionally dive down to melee attack the player. Now it doesn't seem to do that anymore. This makes the boss fight a lot easier (even a bit boring, especially when you run out of arrows), as the only thing you have to look out for is the dragon's breath.
Based on my tests, this bug has existed ever since the dragon fight was revamped in 1.9. It did hit me a couple of times in the 1.9 test, but that might have just been coincidence. In 20w12a (and later) it didn't hit me even once, except when it took off from the nest. A clear difference when compared to 1.8 and earlier, where the dragon would align itself towards the player and then start diving.
I've also paid attention to this in gameplay videos on the internet, and I haven't seen the dragon dive in any of them.
To clarify: I am not talking about the dragon swooping down to land on its nest, which works correctly. In the Wiki (which of course isn't perfect) this is referred to as the diving state.
Do you mean there is something wrong with the zombified piglin's texture? What trophy? Or do you mean that you can't find the new (non-zombified) piglins? Try to look more, they can be hard to find, since they look pretty similar to the zombified ones. If you still can't find them, then there might be a bug.
Since the Nether update, I noticed that while I was playing survival on Bedrock, there were a lot more ghasts attacking me in biomes where they could spawn in than what I was used to on Java (before 1.16). Then I tested it on Java 1.16, and there was a clear difference. It isn't uncommon to see two ghasts in close proximity on Bedrock, while on Java such a sight is very rare.
PS: This is just my personal opinion, but I much preferred the Bedrock spawn rates, as they made the Nether a lot more challenging, instead of the attacks just being a sporadic mosquito bite.
So I hope Mojang will consider increasing the Java spawn rates, and not lowering the Bedrock ones. (Though sometimes it felt as though as soon as I killed one of them, another would spawn to get me. Could've been me being tired too.)
Since the Nether update, I noticed that while I was playing survival on Bedrock, there were a lot more ghasts attacking me in biomes where they could spawn in than what I was used to on Java (before 1.16). Then I tested it on Java 1.16, and there was a clear difference. It isn't
uncommonto see two ghasts in close proximity on Bedrock, while on Java such a sight isvery rare.PS: This is just my personal opinion, but I much preferred the Bedrock spawn rates, as they made the Nether a lot more challenging, instead of the attacks just being a sporadic mosquito bite.
![]()
So I hope Mojang will consider increasing the Java spawn rates, and not lowering the Bedrock ones. (Though sometimes it felt as though as soon as I killed one of them, another would spawn to get me. Could've been me being tired too.)Since the Nether update, I noticed that while I was playing survival on Bedrock, there were a lot more ghasts attacking me in biomes where they could spawn in than what I was used to on Java (before 1.16). Then I tested it on Java 1.16, and there was a clear difference. It isn't rare to see two ghasts in close proximity on Bedrock, while on Java such a sight is more uncommon.
PS: This is just my personal opinion, but I much preferred the Bedrock spawn rates, as they made the Nether a lot more challenging, instead of the attacks just being a sporadic mosquito bite.
It was more exciting, so I hope Mojang will consider increasing the Java spawn rates, and not lowering the Bedrock ones. (Though sometimes it felt as though as soon as I killed one of them, another would spawn to get me. Could've been me being tired too.)
Custom structures in datapacks that modify worldgen ignore some entity NBTCustom structures ignore some entity NBT data if generated with worldgen
If you create a structure using structure blocks, entities can be saved with the structure. If you load the same structure, the entities will have the same
NBTdata as expected.If however you make the structure generate in the world with a datapack, some
NBTdata is ignored.I can confirm this happening with:
- "Size" for Magma cubes
- "HandItems" for Skeletons (NOTE: "ArmorItems" is saved correctly)
If you create a structure using structure blocks, entities can be saved with the structure. If you load the same structure, the entities will have the same entity data as expected.
If however you make the structure generate in the world with a datapack, some entity data is ignored.
I can confirm this happening with:
- "Size" for Magma cubes
- "HandItems" for Skeletons (NOTE: "ArmorItems" is saved correctly)
Custom structures ignore some entityNBTdata if generated with worldgen
Custom structures ignore some entity data if generated with worldgenStructures ignore some entity data if generated with worldgen
If you create a structure using structure blocks, entities can be saved with the structure. If you load the same structure, the entities will have the same entity data as expected.
If however you make the structure generate in the world with a datapack, some entity data is ignored.
I can confirm this happening with:
- "Size" for Magma cubes
- "HandItems" for Skeletons, Wither Skeletons and Strays (NOTE: "ArmorItems" is saved correctly)
Does not affect "HandItems" for Piglins, interestingly.
If you create a structure using structure blocks, entities can be saved with the structure. If you load the same structure, the entities will have the same entity data as expected.
If however you make the structure generate in the world with a datapack, some entity data is ignored.
I can confirm this happening with:
- "Size" for Magma cubes
- "HandItems" for Zombified Piglins, Skeletons, Wither Skeletons and Strays (NOTE: "ArmorItems" is saved correctly)
Does not affect "HandItems" for Piglins, interestingly.
If you create a structure using structure blocks, entities can be saved with the structure. If you load the same structure, the entities will have the same entity data as expected.
If however you make the structure generate in the world with a datapack, some entity data is ignored.
I can confirm this happening with:
- "Size" for Magma cubes
- "HandItems" for Zombified Piglins, Skeletons, Wither Skeletons and Strays (NOTE: "ArmorItems" is saved correctly)
- "Passengers" for Minecarts
Does not affect "HandItems" for Piglins, interestingly.
This is how they've always been, but I never understood why. Every other mob drops their food item every time. Rabbits are quite difficult to catch, and that's why there is even more reason to reward the player.
hi Salasana could not agree more
firework has been very long time ingame and can not make it without crafting table so Recipe should had it long time ago
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
hi could not agree more
Firework rockets are now in the recipe book as of snapshot 20w45a. see message send by Salasana added a comment - 05/Nov/20 12:28 AM https://bugs.mojang.com/browse/MC-115229?focusedCommentId=834614&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-834614
As mentioned by Salasana, farmers with a full inventory will only craft bread once they've composted seeds to fill up slots. Feel free to leave any feedback about composting mechanics on the Feedback Site or the Feedback Discord.


I have experienced this too in 1.14.2. It's especially noticeable on my custom map (vanilla, of course). The map has very dense rain forests, and if I break or place blocks, I get unbearable amounts of lag. When I break a tree trunk so that its leaves start to decay, the FPS graph's spikes on the debug screen go all the way up to the top of the window.
Interestingly, if the block being broken is tall grass, the lag is much less extreme. For this reason I believe that lighting updates are the primary cause of problems here (since tall grass lets light through), and leaf blocks in the jungle amplify the effect.
Edit: If lighting updates really are to blame, maybe they could also explain why fire causes lag.
I noticed severe lag while playing on a friend's realm when he was chopping down a tree in a plains biome. The effect was similar but not as extreme, and I am fairly sure that the cause is the same as here. So perhaps this bug report could be renamed or merged with another similar one. Do you agree?
Edit: what I previously mentioned about blocks being broken in jungles causing lag is no longer an issue in 1.14.4. Moving around still causes severe lag, so the issue is probably with leaf block updates.
I think MC-148095 is related to this. The lag is very similar, and could be caused by decaying or updating leaves.
Edit: removed my experiences with lighting updates, because they seem to have been fixed as of 1.14.4.
Can confirm. The hitbox is buggy and weird. This also happens even when the dragon is not on the nest. Trying to fight it with a sword (for example by chasing it with elytra) is almost impossible as the hits don't register correctly. When you hit the dragon, the weapon makes a sound and you can see particles if the weapon is enchanted (see pictures), but no damage is dealt. I've seen videos where people were very frustrated by this, as it feels inconsistent and buggy when compared to how hits normally work.
Still in 1.16.1
I reported
MCPE-85571(duplicate), which is about there being more ghasts on Bedrock than on Java. Now that I think about it, I had a lot of trouble with magma cubes as well in the basalt delta biome, which made me want to avoid the biome, and as a consequence I got lost for hours. This definitely needs to be fixed.I actually liked the increased amount of ghasts. They aren't that big a problem in my opinion (from what I've seen they used to be very common in ancient Java versions, and before this update I wished they were more common), but I can see why the other mobs can be overwhelming. And there were times when I would kill a ghast, and another one would spawn pretty close to the first one almost instantly.
How is this a WAI? Firework rockets are an important item gameplay wise, but the game doesn't even teach you how to get them. A major oversight in my opinion. For example in this video at 18:10 you can see the problem.
Obviously this is an extreme scenario, but this man had to walk 7 and a half hours to get back to his base at the end of a long bridge he is building after he had died. (Absurd, but I believe he really did walk there.) He didn't know about rockets since he is doing a blind play through. If only the game had explained to him how he could get back faster.
Silly bot. This is the original bug report, the new one is the duplicate.
MC-167052Was reported by me (apparently it is a duplicate even though it is the older report... Well at least somebody else has noticed this as well.) This was broken all the way back in 1.9, when the dragon fight was revamped.I was thinking that might be the reason. I'm glad Mojang know about this though.
Firework rockets are now in the recipe book as of snapshot 20w45a. I've seen some of the developers giving a shoutout to the channel I linked in my previous comment. Did his struggles inspire this change? Whatever the case, I thank you Mojang on behalf of Piropito. 🙂
@PotholedSea40 Are you sure? The Mojang priority says otherwise. This was never mentioned in any change log. I remember that they only said in a certain snapshot's changelog that the dragon will no longer stop its attack when it is hit, which had made it easy to avoid it before. That change would be useless if the divebomb attack was intentionally removed.
And if this was indeed intentional, it wasn't a very smart change, which you will understand if you've ever run out of arrows while fighting it. You have to wait for it to land, and that can take ages. And of course the dragon fight is a lot less challenging when it never charges at you.
This is a major oversight if there really is no way of preventing it from happening. I created a structure with redstone in it, but there is one stair block that gets waterlogged, and the water wipes out all the redstone.
@Dhranios Sure. I also attached images.
The problem is that the game seems to overwrite the mobs' data. I made a wither skeleton with a shield and a netherite sword. When generated with a structure, only its sword was changed, because wither skeletons have a stone sword by default. The same with Size for magma cubes I assume. The game chooses a random size, and ignores the one stored in the structure file.
I made a command that modifies a piglin's angry_at memory. As this command is repeated every tick, the piglin's inventory quickly fills up. I suppose I'll need to use the silly snowball method to make the mob angry at a specific mob without this bug happening. Hopefully this gets fixed, even though the report is marked invalid.
"i believe it may be due to the change you guys added where they put seeds into a composter, emptying their inventories of seeds, causing them to break the farm"
So it's not a bug then, but a feature request? Their inventories aren't full, only your farm is outdated. (To work around this change, simply prevent the villager from accessing the composter. From my quick test the villager doesn't actually need to use the composter.)
A couple of years ago I made an adventure map where some skeletons could see you from a long distance away. I noticed that they only did that if you first hurt them, i.e. shot them with a bow. Then they suddenly started sprinting towards you even from a hundred blocks away. It was unfortunate that the player had to provoke them, but it was also kind of funny and so I ignored it.
Now I tested this again, and the follow_range attribute doesn't work for me at all, even when I try to anger the skeleton from a distance.EDIT: Well, derr... I revisited my old adventure map, and it turns out it still worked. I just wrote the command incorrectly when I tested this. Still, hopefully Mojang can make it so mobs see you without you having to provoke them.
Here's the command:
/summon minecraft:skeleton ~ ~ ~ {Attributes:[{Name:"minecraft:generic.follow_range",Base:100.0d}],PersistenceRequired:1}Confirmed for hoglins.
Confirmed for 1.20.2. I was wondering why my skeletons kept missing...
Edit: If you need this fixed for map maker reasons, there is a workaround. Make every arrow belong to the player:
Confirmed for 1.21.1.