You can use the item in your offhand if the lily pad in your mainhand cannot be placed
Since version 1.13 you can no longer use the item in your offhand if the block in your mainhand cannot be placed, which is intended per MC-126337. However, this doesn’t apply to lily pads. If you cannot place the lily pad because of an entity standing in the way or the targeted block not being applicable for placing lily pads, you will still be able to use the item in your offhand.
Steps to Reproduce:
- Hold a lily pad in your main hand
- Hold a snowball in your off-hand
- Try and place the lily pad on a block which is not normally applicable for placement
Expected & Observed Results:
- The snowball will be thrown.
- The player would not throw the snowball item, as they are currently attempting to use the main hand to place a block/item.
Screenshots/Videos:
Linked Issues
relates to6
Created Issue:
You can use the item in your offhand if the lily pad in your mainhand cannot be placed
The bug
Since version 1.13 you can no longer use the item in your offhand if the block in your mainhand cannot be placed, which is intended per
MC-126337. However this doesn’t apply to lily pads, so if you cannot place the lily pad, because there would be an entity inside of because the already is a block or there is no water, you will be able to use the item in your offhand. Relates toMC-126337, MC-135143 andMC-667.How to reproduce:
- Put an item with a right click action in your offhand, for example a snowball.
- Try to place a lily pad inside yourself or at a block that it cannot be placed on.
You will use the item in your offhand.
The bug
Since version 1.13 you can no longer use the item in your offhand if the block in your mainhand cannot be placed, which is intended per
MC-126337. However this doesn’t apply to lily pads, so if you cannot place the lily pad,becausethere would be an entity inside of because the already is a block or there is no water, you will be able to use the item in your offhand.Relates toMC-126337, MC-135143 andMC-667.
Howtoreproduce:
Put an item with a right click action in your offhand, for example a snowball.- Try to place a lily pad inside yourself or at a block that it cannot be placed on.
You will use the item in your offhand.
Since version 1.13 you can no longer use the item in your offhand if the block in your mainhand cannot be placed, which is intended per
MC-126337. However, this doesn’t apply to lily pads. If you cannot place the lily pad because of an entity standing in the way or the targeted block not being applicable for placing lily pads, you will still be able to use the item in your offhand.Steps to Reproduce:
- Hold a lily pad in your main hand
- Hold a snowball in your off-hand
- Try and place the lily pad on a block which is not normally applicable for placement
Expected & Observed Results:
- The snowball will be thrown.
- The player would not throw the snowball item, as they are currently attempting to use the main hand to place a block/item.
Screenshots/Videos:
Notes:
Related to these issues
MC-256407 MC-136405 MC-237476 MC-226518
relates to
Since version 1.13 you can no longer use the item in your offhand if the block in your mainhand cannot be placed, which is intended per
MC-126337. However, this doesn’t apply to lily pads. If you cannot place the lily pad because of an entity standing in the way or the targeted block not being applicable for placing lily pads, you will still be able to use the item in your offhand.Steps to Reproduce:
- Hold a lily pad in your main hand
- Hold a snowball in your off-hand
- Try and place the lily pad on a block which is not normally applicable for placement
Expected & Observed Results:
- The snowball will be thrown.
- The player would not throw the snowball item, as they are currently attempting to use the main hand to place a block/item.
Screenshots/Videos:
Notes:
Related to these issues
MC-256407 MC-136405 MC-237476 MC-226518
Interactions are based on an ordered system in the box below. The "+" means that multiple events are a part of the same interaction type and can happen if any mainhand event fails. The "-" means that multiple events are a part of the same interaction type and can only test one event before navigating to the next interaction type. Finally, the "→" denotes a separation of interaction types and the order that the system navigates in:
(armor + fishing rod + shield + bow + crossbow + food + boat + bucket + lily pad + throwables + hoe + ender eye on portal frame) → (minecart - armor stand - flint and steel - fire charge) → placed redstone ore (from MC-195094) → block → entity or placed block
As hinted at above, the interactions are navigated linearly. This means that once the list navigates forwards, there's no going backwards until escaping the in-game interaction attempt completely.
The system also has the following checks that are performed in the order below. If the interaction type is skipped, the next check is not assessed on the current interaction type either (meaning that if the interaction type is skipped, it's all over).
If the interaction type does not match the desired interaction type in the mainhand, the current interaction type is skipped. If the mainhand cannot perform the event, the current interaction type is skipped. If the offhand cannot perform the event, the current interaction type is skipped.
If MC-126337 truly is intended, and if MC-135143 is valid, then there are many more situations that should be added to this ticket (or multiple tickets addressing each issue). For example, when holding any of the items before the first arrow (say a boat) in the mainhand, and any of the items after the first arrow and before the last arrow (say a minecart) in the offhand, then if the mainhand fails, the offhand event will always be tested rather than skipped. If these items were swapped between the mainhand and offhand however, the entire interaction would cease as per MC-126337.
Extra information:
If a minecart is in the mainhand while a boat is in the offhand, the boat could never possibly be placed because the interaction type that performs the event is already skipped. If armor is in the mainhand and an block is in the offhand, the block could still be placed if and only if the armor event fails (which is the same case as MC-135143). If a bow and a lily pad are held at the same time, both have a full chance to be placed if whichever one that is in the mainhand fails (which is the same case as MC-218114). Finally, if a minecart and an armor stand are held at the same time, whichever one that is in the offhand could never possibly be placed since that specific interaction type stops testing more events after one fails.
When targeting a block which is a valid placement position for frogspawn or lily pads, the game will favor the camera/look direction's raycast and place the block in an unexpected or undesired position.
(By raycast, I mean a straight line created from the player's view to the first water source block it hits)
Steps to Reproduce:
- Create a 3x3x3 pond of water
- In the center-most position, place a block
- Stand on the edge of the pond (allowing space for placement on top of the water in front of you)
- Target the front-half of the block inside the pond
- Try and place a lily pad or frogspawn
Observed Behavior:
The block is placed on the water block closest to the player.
Expected Result:
The block would be placed above the center block, because it was targeted.
Screenshots/Videos:
In this example, I am trying to place the lily pad above the white wool. While this position is valid for placement, the lily pad is put on top of the water block my camera first views, instead of being placed on top of the block I am targeting.
water_blocks_place.mp4
Notes:
- To clarify; while this is very similar to MC-226518, it is different as that issue specifies the block is being placed when it otherwise should not be placed at all. In this instance, the block should be placed, but is put in the wrong position. The two however are closely related.
- Other related lily pad/frogspawn placement issues:
MC-237476 MC-256407 MC-136405 MC-245845 MC-218114 MC-206807
More information about these issues is posted in a comment on MC-135143:
https://bugs.mojang.com/browse/MC-135143?focusedCommentId=999080&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-999080
Requesting ownership of this issue