Shearing a bogged spawns mushrooms at the bogged's feet
When shearing a mooshroom or sheep, the mushrooms or wool will fly out in all directions from the top of the relevant entity. However, when shearing a bogged, the mushrooms will barely fly out from the bogged's feet. I believe this to be an inconsistency in gameplay as players will expect the items to come from the relevant position on the entity (the bogged's head in this case) on all entities.
Note that Bedrock Edition spawns the mushrooms in the vertical center of the bogged.
Created Issue:
Shearing a bogged spawns mushrooms at the bogged's feet
When shearing a mooshroom or sheep, the mushrooms or wool will fly out in all directions from the top of the relevant entity. However, when shearing a bogged, the mushrooms will barely fly out from the bogged's feet. I believe this to be an inconsistency in gameplay as players will expect the items to come from the relevant position on the entity (the bogged's head in this case) on all entities.
When shearing a mooshroom or sheep, the mushrooms or wool will fly out in all directions from the top of the relevant entity. However, when shearing a bogged, the mushrooms will barely fly out from the bogged's feet. I believe this to be an inconsistency in gameplay as players will expect the items to come from the relevant position on the entity (the bogged's head in this case) on all entities.
Note that Bedrock Edition spawns the mushrooms in the vertical center of the bogged.
relates to
relates to
(This issue is not new to the most recent snapshot, it just does not affect 1.20.4)
Scutes from brushing an armadillo are spawned at the feet of the entity, which is unusual when compared to other items summoned from mob interactions. Specifically, see MC-269147.
Steps to Reproduce:
- Summon and armadillo
- Tick freeze the game
- Brush the armadillo
→
The scute spawns at the feet of the armadillo.
→
The scute would spawn on top of the entity.
Screenshots/Videos:
Notes:
Related to MC-269147
Scutes spawned from a baby turtle when they grow up will be positioned too high above the entity.
Steps to Reproduce:
- Tick freeze the game for observation:
/tick freeze
- Summon a turtle 1 tick away from growing up:
/summon minecraft:turtle ~ ~ ~ {NoAI:1b,Age:-1} - Advance the game by 1 tick
/tick step 1
Observed Behavior:
The scute will be positioned too high above the turtle entity.
Expected Result:
The scute would be positioned directly above the top of the turtle when it grows up, similar to other items created from entities by game events/interactions.
Screenshots/Videos:
Showcase of the scute item spawning compared to other items created by game events:
SpawnedItems.mp4
Notes:
I'd like to make a request to review the resolution of "Invalid / feature request" on this report.
Items spawning in unexpected locations from player interactions with entities (or items dropping from entities more generally) has been considered valid in previous reports, provided the fix for MC-269147, and the triage of MC-262667. On top of this, with the recent traige of MC-271974, it is further supported that items spawning in incorrect locations from entities makes for a valid report, and is not a change request.
With the current resolution of Invalid, it is said that this report aims to change how the scute drops at the feet of an armadillo instead of above its shell, but the report actually aims to address how the case with the armadillo scute is the one exception when compared to all other cases of entity item interactions (refer to AllEntityItemInteractions.mp4
). With the armadillo being a special exception to what is seemingly an established rule of gameplay, it would be expected that if the armadillo functioning differently is intentional, the issue would have been resolved as such (Working as Intended) instead of requesting a change.
With all this in mind, I would first and foremost request that this issue be reopened because the report is arguably about a valid issue comparatively to other reports. If the scutes dropping at the armadillo's feet is in fact intentional design, I would then request that the report be resolved as "Working as Intended" instead of "Invalid" for the sake of clarity to show that the current behavior is designed to be different from other entities.
Confirmed, also affects 1.20.4 pre-release 2.