MCPE-32690Cocoa beans, heads, ladders, tripwire hooks, and item frames cannot replace vines at all
When trying to place a cocoa bean, mob head, tripwire hook, ladder or item frame onto a block with a vine covering one of its faces, the placement will fail completely, instead of the block you're trying to place replacing the vine.
Linked Issues
Created Issue:
Heads, ladders, tripwire hooks an item frames cannot replace vines at all
When trying to place a mob head, tripwire hook, ladder or item frame onto a block with a vine covering one of its faces, the placement will fail completely, instead of the block you're trying to place replacing the vine.
Attachments4
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
![[MCPE Mod] Celesian](../../../data/avatars/users/81635.png){kind=small}
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
When trying to place a cocoa bean, mob head, tripwire hook, ladder or item frame onto a block with a vine covering one of its faces, the placement will fail completely, instead of the block you're trying to place replacing the vine.
Heads, ladders, tripwire hooks an item frames cannot replace vines at allCocoa beans, heads, ladders, tripwire hooks, and item frames cannot replace vines at all
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
If there is a floor block available, the button/lever will snap to it, otherwise the placement will fail completely.
Torches and redstone torches exhibit similar behaviour, but will still attach themselves to the side if no floor block is available.
Interestingly, heads are unaffected by this and instead exhibit MCPE-32690. Signs are affected by MCPE-32689.
In most cases, you can replace a vines block by placing any block while pointing to either the vines themselves or the surface of an adjacent block (below, above, or on any side). The exception is that when placing an "attaching block" (a block that attaches itself to an adjacent block), this only works the same way if you are not pointing at the vines themselves. If you attempt to place an attaching block while pointing at the vines, the behavior varies depending on what kind of attaching block you're placing. This deviation from the expected behavior causes confusion and frustration.
The following paragraphs list how the various kinds of attaching blocks behave when placed while pointing at the vines. The expected behavior in each case would be that the block would attach itself to the wall the vines were on.
Lever, Button, Item Frame, Bell:
If there is a solid block below the vines, the attaching block attaches to it. Otherwise, the vines remain and the block is not placed.
End Rod, Sign, Grindstone:
If there is a solid block below the vines, the attaching block attaches to it. Otherwise, the attaching block is placed as if there were a block there, which leaves it floating. (In the case of a sign, it will always have the standing_sign shape.)
Torch, Redstone Torch:
The attaching block searches for a block to attach to, in the order Below, South, West, North, East. (At least one of these must exist, the one the vines were attached to.)
Lantern:
The attaching block searches for a block to attach to, in the order Below, Above. If neither is found, the vines remain and no lantern is placed.
Banner, Tripwire Hook:
These cannot be placed while pointing at vines, but can be placed on an adjacent block in which case the vines are broken. Note that the banner is 2 blocks high. When placed, it will only break the vines in the upper half; the lower half can coexist with vines on another wall if they were already present.
Coral Fan, Dead Coral Fan:
These cannot be placed in a vines block, not even by pointing at an adjacent block.
Resolving as a duplicate of MCPE-32690.
Affects 1.2.16
Affects 1.4
Affects 1.16.0.64
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version?
If it is, please be sure to include steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Still an issue in 1.16.210.54 Beta.
Except with cocoa beans you can replace them by aiming at adjacent blocks, but not by aiming at the vine itself.
I can still reproduce it at 1.21.30.22
Note that there should be no adjacent blocks (like in MCPE-32691), and you should aim at the vines and not at the opposite blocks.
Confirmed in 1.21.44
Confirmed in 1.21.60.21