[Mojang] elvendorke
- elvendorke
- JIRAUSER715320
- Europe/Stockholm
- Yes
- No
Allay doesn'tpick upitems when mobGriefing is set to falseAllay doesn't ignore items when mobGriefing is set to false
blocks
is duplicated by
relates to
blocks
Sprinting whilst riding an entity,flying with elytra, or levitating changesyour field of viewSprinting whilst riding an entity or flying with elytra your field of view
The Bug:
Attempting to sprint whilst riding an entity
,flying with elytra, or levitating changes yourfield of view, but doesn't actually adjust your speed in any shape.Steps to Reproduce:
- Place down a boat.
- Begin moving forward in it and press the sprint button.
- Take note as to whether or not sprinting whilst riding an entity, flying with elytra, or levitating changes your field of view.
Observed Behavior:
Your field of view changes.
Expected Behavior:
Your field of view wouldn't change.
The Bug:
Attempting to sprint whilst riding an entity or flying with elytra field of view, but doesn't actually adjust your speed in any shape.
Steps to Reproduce:
- Place down a boat.
- Begin moving forward in it and press the sprint button.
- Take note as to whether or not sprinting whilst riding an entity, flying with elytra, or levitating changes your field of view.
Observed Behavior:
Your field of view changes.
Expected Behavior:
Your field of view wouldn't change.
Sprinting whilst riding an entity or flying with elytra changes your field of view
Sprinting whilst riding an entity, flying with elytra, or levitating changes your field of viewDismounting a rideable entity whilst sprinting does not reset sprinting.
The Bug:
Attempting to sprint whilst riding an entity, flying with elytra, or levitating changes your field of view, but doesn't actually adjust your speed in any shape.Additionally, when dismounting a rideable entity whilst your field of view is changed, your field of view will not reset despite the player no longer sprinting. It will only reset when the player sprints and stops sprinting again.
Steps to Reproduce:
Place down a boat.Begin moving forward in it and press the sprint button.Take note as to whether or not sprinting whilst riding an entity, flying with elytra, or levitating changes your field of view.Observed Behavior:
Your field of view changes.
Expected Behavior:Your field of view wouldn't change.
The Bug:
When dismounting a rideable entity whilst you are sprinting does not reset sprinting. You need to stop and start sprinting again to get it to reset.
- Summon horse
- Sprint while on horse
- Jump off while sprinting
- Player now continues to be in sprinting (With changed FOV) even if you slow down
- Press sprint button again and stop sprinting to get sprinting to stop and FOV to reset
Observed Behavior:
Player continues to be in sprinting while jumping off horse mid sprint even if you slow down
Expected Behavior:
Player should stop being in sprinting when you jump off horse mid sprint and then slow down
is blocked by
relates to
is blocked by
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
relates to
relates to
relates to
relates to
relates to
is duplicated by
duplicates
relates to
Hi [Mojang] elvendorke, thanks for your response. So initially in 22w16a, I recall the following warnings being printed into the game output console:
Unable to play unknown soundEvent: minecraft:entity.tadpole.step Unable to play unknown soundEvent: minecraft:entity.tadpole.eat
I'm not exactly sure what I was doing at the time when these messages were logged, so I apologize in advance about this, however, the presence of these warnings led me to believe that these sound events were still missing from the game, hence why I marked 22w16a as an affected version for this bug.
Just now, after launching an instance of 22w19a, these warnings no longer appear in the game output console. I summoned multiple tadpoles around me, fed them, and allowed them to produce their sounds (which I think was what I was doing at the time when these warnings were logged in the console in 22w16a), so I think it's safe to assume that this was fixed at some point judging by how you mentioned that this problem was resolved in this instance by removing these two sound events from the game.
The Bug:
Villagers don't ignore items when the "mobGriefing" gamerule is set to "false".
[Mojang] elvendorke recently changed the title of MC-250020 to "Allay doesn't ignore items when mobGriefing is set to false", therefore indicating that allays should ignore items under these circumstances. Since this same concept can also be seen with villagers, I'm inclined to believe that this behavior isn't intentional, hence my reasoning for creating this ticket.
Please also note that this report isn't a duplicate of MC-3370. This ticket (MC-253480) describes how villagers don't ignore items when the "mobGriefing" gamerule is set to "false", not actually the fact of how they cannot collect them.
Steps to Reproduce:
- Place down a composter and summon a villager nearby.
- Set the "mobGriefing" gamerule to "false".
/gamerule mobGriefing false
- Throw some items that the villager would normally be able to collect on the ground, for example, some carrots.
- Wait for the villager to notice the carrots and begin pathfinding towards them.
- Take note as to whether or not villagers ignore items when the "mobGriefing" gamerule is set to "false".
Observed Behavior:
Villagers don't ignore items.
Expected Behavior:
Villagers would ignore items.
Hmm... This report looks suspiciously familiar... Whoever wrote it must be an incredibly awesome individual...
Jokes aside, if it's okay with [Mojang] elvendorke, I'd be happy to take ownership of this report so that I can keep it up-to-date, just like how I did previously before changes were made to MC-30403. If not, it's completely fine. ![]()
Eyy; thank you [Mojang] elvendorke; I really appreciate that. You have both tickets (MC-30403 and this one (MC-257082)) in good hands. ![]()
[Mojang] elvendorke I tested this with a new world and you are correct. Updating the ticket with this information.
I'm restoring the previous resolution per [Mojang] elvendorke's comment. If you'd like this changed, try submitting this as a feature request on the feedback site, linked below. ![]()
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Hi [Mojang] elvendorke. Did you see my comment with table which clarifies the inconsistency? Surely that cannot be intended as the Bundle is not even consistent with itself.

Reopened to fix rotation only working in certain directions and fix mirroring.
Frog spawn rules don't follow temperature in biomes exactly, some of these frog variants are indeed a bug while some of these are as intended.
Tadpole step and tadpole eat should also have been fixed 22w16a, these sound events were removed. Are you trying to play these sounds when getting "Unable to play unknown soundEvent"?
Thank you for verifying and getting back to me. : ) Then it seems like it is resolved so I will update the issue.
Thanks you two!
haha! It's all yours [Mod] Avoma !
The issue for this world seems to be the order of the datapacks. The order of the datapacks can affect the behaviour of the features in those datapacks. The vanilla (Default) datapack should be the first datapack to get the expected behaviour and any experimental feature packs should be ordered after. In this case the 1.20 datapack is ordered before the vanilla datapack and the 1.20 netherite recipes are being overridden by the 1.19 recipes.
Pigstep is placed last in the creative menu due to being from the Nether. Within dimension group in menu the discs are sorted by redstone signal strength.
I was able to reproduce this without the fix done in
MC-189111, but when testing with the fix it made the bee fly out of the bush. So this should've been fixed as part of that bug.Will close this, but if anyone is able to reproduce another scenario of this happening feel free to reopen and add more details.
This seems to have been fixed, can't reproduce anymore.
Bedrock sizing is depending on different UI configurations per platform. Java sizing is as designed.