catter1
- catter1
- JIRAUSER604889
- Europe/Stockholm
- Yes
- No
MC-249968![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg){kind=small}
Normal
Description:
When powering a beacon with an ingot, the user is disconnected.
The Bug:
Upon powering the beacon, the use is disconnected with an io.netty.handler.codec.EncoderException. This behavior is observed in a server environment, but not in singleplayer. Base blocks, ingot used to power beacon, level of beacon, and effect chosen does not seem to matter. Upon joining, beacon does not gain its chosen effect, and user is refunded their ingot. See the video attached for process, and screenshot for full disconnect message.
Steps to Reproduce:
- Join a Vanilla server in 22w14a
- Place a beacon (with at least 3x3 of a refined ore underneath)
- Grab an ore of your choice and open beacon UI
- Place ingot of choice in beacon UI slot, select an effect, and push the "check" button
Observed Result:
User is disconnected from server with an error. Beacon remains effect-less upon rejoining.
Expected Result:
Beacon gains its effect and user does not crash.
When powering a beacon with an ingot, the user is disconnected.
The Bug:
Upon powering the beacon, the use is disconnected with an io.netty.handler.codec.EncoderException. This behavior is observed in a server environment, but not in singleplayer. Base blocks, ingot used to power beacon, level of beacon, and effect chosen does not seem to matter. Upon joining, beacon does not gain its chosen effect, and user is refunded their ingot. See the video attached for process, and screenshot for full disconnect message.
Steps to Reproduce:
- Join a Vanilla server in 22w14a
- Place a beacon (with at least 3x3 of a refined ore block underneath)
- Grab an ore of your choice and open beacon UI
- Place ingot of choice in beacon UI slot, select an effect, and push the "check" button
Observed Result:
User is disconnected from server with an error. Beacon remains effect-less upon rejoining.
Expected Result:
Beacon gains its effect and user does not crash.
This bug is about the knockback created by the `explode` entity effect used in enchantment components, also affecting the `knockback_multiplier` field by proxy. Specifically, this issue can occur when `explode` is used in the `hit_block` component, with a projectile such as an arrow.
The Bug
The `explode` entity effect is supposed to provide a knockback within the `radius` of the explosion, scaled by `knockback_multiplier`. However, if this explosion originates in a solid block (which can happen when an arrow hits the block), then the block will completely eat the knockback suppsoed to be provided by the explosion. This assumes the usage of `block_interaction` set to `none` or `trigger`, which would not break the block.
Steps to Reproduce
- Create a datapack with a custom bow/crossbow enchantment that applies an explosion when the arrow hits the block. See the codeblock below for an example `hit_block` component. Alternatively, use the datapack I have already created and attached to this report.
... "effects": { "minecraft:hit_block": [ { "effect": { "type": "minecraft:explode", "radius": 4, "block_interaction": "none", "small_particle": { "type": "minecraft:explosion" }, "large_particle": { "type": "minecraft:explosion" }, "sound": "entity.cat.hurt", "knockback_multiplier": 3, "attribute_to_user": true, "create_fire": false } } ] } ...
- Go in game and apply the enchantment to a bow (`/enchant @s test:knockback_arrow` if using the sample datapack).
- Summon mobs, or use yourself for testing.
- Shoot a solid block near a mob within the radius of the enchantment. Observe how no knockback is applied.
- Shoot a non-solid block near a mob within the radius of the enchantment, such as a fencepost. Observe that the knockback is properly applied.
A video of the process has also been attached to this report.
Expected Behavior
Regardless if the arrow (or other projectile where applicable) hits a solid or non-solid block, knockback should be applied. As an extra note, if the optional `damage_type` field is provided with the enchantment, you will notice a little bit of knockback. This is simply due to the default knockback taken from damage in general, rather than the actual knockback expected to be taken from an explosion.
This bug is about the knockback created by the explode entity effect used in enchantment components, also affecting the knockback_multiplier field by proxy. Specifically, this issue can occur when explode is used in the hit_block component, with a projectile such as an arrow.
The Bug
The explode entity effect is supposed to provide a knockback within the radius of the explosion, scaled by knockback_multiplier. However, if this explosion originates in a solid block (which can happen when an arrow hits the block), then the block will completely eat the knockback suppsoed to be provided by the explosion. This assumes the usage of block_interaction set to none or trigger, which would not break the block.
Steps to Reproduce
- Create a datapack with a custom bow/crossbow enchantment that applies an explosion when the arrow hits the block. See the codeblock below for an example hit_block component. Alternatively, use the datapack I have already created and attached to this report.
... "effects": { "minecraft:hit_block": [ { "effect": { "type": "minecraft:explode", "radius": 4, "block_interaction": "none", "small_particle": { "type": "minecraft:explosion" }, "large_particle": { "type": "minecraft:explosion" }, "sound": "entity.cat.hurt", "knockback_multiplier": 3, "attribute_to_user": true, "create_fire": false } } ] } ...
- Go in game and apply the enchantment to a bow (/enchant @s test:knockback_arrow if using the sample datapack).
- Summon mobs, or use yourself for testing.
- Shoot a solid block near a mob within the radius of the enchantment. Observe how no knockback is applied.
- Shoot a non-solid block near a mob within the radius of the enchantment, such as a fencepost. Observe that the knockback is properly applied.
A video of the process has also been attached to this report.
Expected Behavior
Regardless if the arrow (or other projectile where applicable) hits a solid or non-solid block, knockback should be applied. As an extra note, if the optional damage_type field is provided with the enchantment, you will notice a little bit of knockback. This is simply due to the default knockback taken from damage in general, rather than the actual knockback expected to be taken from an explosion.
Doesn't seem to apply to all blocks - sand and stone are the ones I noticed. Does not seem to do so on grass blocks. When spreading, it spreads a lot, and in an ugly cube shape. Seems unintentional. Is the same in 21w05b.
Can confirm in 22w18a.
Can confirm
Can confirm this still is an issue in 1.21.2 and 1.21.3.
Can confirm this issue.
Can confirm in 1.21.4