MC-118850Vines use opposite facing value when trying to spread in corners
The bug
Vines use the opposite facing value when they try to spread in corners. This causes them to spread on blocks which would only support them on the opposite site or to not spread on blocks which should be able to support them on this side.
How to reproduce
- Build a setup as shown in Setup.png
(stair type does not matter) - Increase the randomTickSpeed gamerule value
/gamerule randomTickSpeed 1000
→ The vines spread on the stairs despite them not supporting the vines, updating blocks around the vines causes them to be removed from the stairs
Code analysis
Based on 1.12 decompiled using MCP 9.40 PRE 1
The method net.minecraft.block.BlockVine.updateTick(World, BlockPos, IBlockState, Random) does not call EnumFacing.getOpposite() in the following check:
else if (iblockstate3.func_193401_d(worldIn, blockpos4, enumfacing1) == BlockFaceShape.SOLID)
Linked Issues
Created Issue:
Vines use opposite facing value when trying to spread in corners
The bug
Vines use the opposite facing value when they try to spread in corners. This causes them to spread on blocks which would only support them on the opposite site or to not spread on blocks which should be able to support them on this side.
How to reproduce
- Build a setup as shown in Setup.png
- Increase the randomTickSpeed gamerule value
/gamerule randomTickSpeed 1000→ The vines spread on the stairs despite them not supporting the vines, updating blocks around the vines causes them to be removed from the stairs
Code analysis
Based on 1.12 decompiled using MCP 9.40 PRE 1
The method net.minecraft.block.BlockVine.updateTick(World, BlockPos, IBlockState, Random) does not call EnumFacing.getOpposite() in the following check:
else if (iblockstate3.func_193401_d(worldIn, blockpos4, enumfacing1) == BlockFaceShape.SOLID)
Attachments2
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
relates to
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Apparently this issue has been fixed in some 1.13 snapshot.