MC-184335Placing blocks triggers item_used_on_block, affecting "Not Quite 'Nine' Lives" advancement
The bug
The item_used_on_block trigger also works when placing blocks. This causes the "Not Quite 'Nine' Lives" vanilla advancement to be granted when placing glowstone on the respawn anchor instead of charging the respawn anchor.
This could be intended, but then there should at least be a condition to check whether this was a block placement or a block altering.
How to reproduce
Using the vanilla advancement
- Set a respawn anchor with charges state set to 4
/setblock ~ ~ ~ respawn_anchor[charges=4]
- Shift right click on it with glowstone
The "Not Quite 'Nine' Lives" advancement is granted
Using a generic advancement
- Create an advancement with the item_used_on_block trigger and a function
{ "criteria": { "place": { "trigger": "minecraft:item_used_on_block", } }, "rewards": { "function": "test:use_item" } } - Create a function that prints a message every time this advancement is granted
advancement revoke @s only test:use_item say used item!
The advancement triggers every time you place a block
Attachments2
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
LowCreated Issue:
Placing blocks triggers item_used_on_block, affecting "Not Quite 'Nine' Lives" advancement
The bug
The item_used_on_block trigger also works when placing blocks. This causes the "Not Quite 'Nine' Lives" vanilla advancement to be granted when placing glowstone on the respawn anchor instead of charging the respawn anchor.
This could be intended, but then there should at least be a condition to check whether this was a block placement or a block altering.
How to reproduce
Using the vanilla advancement
- Set a respawn anchor with charges state set to 4
/setblock ~ ~ ~ respawn_anchor[charges=4]- Shift right click on it with glowstone
Using a generic advancement
- Create an advancement with the item_used_on_block trigger and a function
{ "criteria": { "place": { "trigger": "minecraft:item_used_on_block", } }, "rewards": { "function": "test:use_item" } }- Create a function that prints a message every time this advancement is granted
advancement revoke @s only test:use_item say used item!
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Please change Confirmation Status to Confirmed!
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
There should also be a trigger inspired by the bug that occurs when placing a block on a certain block. Or if it is not added, ray casting or block traversal would still be fine.
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
The bug
The item_used_on_block trigger also works when placing blocks. This causes the "Not Quite 'Nine' Lives" vanilla advancement to be granted when placing glowstone on the respawn anchor instead of charging the respawn anchor.
This could be intended, but then there should at least be a condition to check whether this was a block placement or a block altering.
How to reproduce
Using the vanilla advancement
- Set a respawn anchor with charges state set to 4
- Shift right click on it with glowstone
Using a generic advancement
- Create an advancement with the item_used_on_block trigger and a function
{ "criteria": { "place": { "trigger": "minecraft:item_used_on_block", } }, "rewards": { "function": "test:use_item" } }- Create a function that prints a message every time this advancement is granted
advancement revoke @s only test:use_item say used item!
The bug
The item_used_on_block trigger also works when placing blocks. This causes the "Not Quite 'Nine' Lives" vanilla advancement to be granted when placing glowstone on the respawn anchor instead of charging the respawn anchor.
This could be intended, but then there should at least be a condition to check whether this was a block placement or a block altering.
How to reproduce
Using the vanilla advancement
- Set a respawn anchor with charges state set to 4
/setblock ~ ~ ~ respawn_anchor[charges=4]- Shift right click on it with glowstone
Using a generic advancement
- Create an advancement with the item_used_on_block trigger and a function
{ "criteria": { "place": { "trigger": "minecraft:item_used_on_block", } }, "rewards": { "function": "test:use_item" } }- Create a function that prints a message every time this advancement is granted
advancement revoke @s only test:use_item say used item!
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Confirmed in 1.16 Pre-release 2.
Confirmed in 1.16 Pre-release 4.
Confirmed for 20w30a. This overlap of functionality is annoying. I can't detect a player removing a music disc from a jukebox without also detecting when a player places a block against an empty jukebox.
Confirmed for 1.16.2 pre-1. I don't know if this is a separate issue, but placing the block itself will trigger the item_used_on_block criteria if the item is not defined and if you are replacing a non-air block by placing it (like grass or fern).
Can confirm in 20w49a.
Can confirm in 21w03a.
Can confirm in 21w06a.
Can confirm in 21w15a.
Can confirm in 1.17.
Can confirm in 1.17.1.
Can confirm in 1.18.1.
Can confirm in 1.18.2 and 22w15a.
Can confirm in 1.19.2.
Despite the fix for
MC-266055and the new bugMC-267456, this bug still exists in 21w51b.