MC-94016Glass panes and iron bars connect to barrier blocks
The bug
Glass panes and iron bars connect to barrier blocks.
Suggested fix
Based off of Minecraft 1.11, MCP 9.35
public final boolean canPaneConnectToBlock(Block blockIn) { //added "blockIn == Blocks.BARRIER ? false : " return blockIn == Blocks.BARRIER ? false : blockIn.getDefaultState().isFullCube() || blockIn == this || blockIn == Blocks.GLASS || blockIn == Blocks.STAINED_GLASS || blockIn == Blocks.STAINED_GLASS_PANE || blockIn instanceof BlockPane; }
This fixes all glass panes and iron bars.
Linked Issues
is duplicated by3
Created Issue:
barrier can connect any glass pane or iron bars
barrier can connect any glass pane or iron bars
Attachments3
is duplicated by
is duplicated by
structure void and barrier can connect any glass pane or iron bars
is duplicated by
barrier and structure voids can connect any glass pane or iron bars
barrier
and structure voidscan connect any glass pane or iron bars
structure void andbarrier can connect any glass pane or iron bars
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
barrier can connect any glass pane or iron barsBarrier can connect any glass pane or iron bars
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
barrier can connect any glass pane or iron barsBarrier can connect any glass pane or iron bars.
Fix: ( Based off of Minecraft 1.11, MCP 9.35 )
net.minecraft.block.BlockPane.canPaneConnectToBlock(Block blockIn)public final boolean canPaneConnectToBlock(Block blockIn) { //added "blockIn == Blocks.BARRIER ? false : " return blockIn == Blocks.BARRIER ? false : blockIn.getDefaultState().isFullCube() || blockIn == this || blockIn == Blocks.GLASS || blockIn == Blocks.STAINED_GLASS || blockIn == Blocks.STAINED_GLASS_PANE || blockIn instanceof BlockPane; }This fixes all glass panes and iron bars.
Barrier can connect any glass pane or iron barsGlass panes and iron bars connect to barrier block
Barrier can connect any glass pane or iron bars.
Fix: (Based off of Minecraft 1.11, MCP 9.35)
net.minecraft.block.BlockPane.canPaneConnectToBlock(Block blockIn)public final boolean canPaneConnectToBlock(Block blockIn) { //added "blockIn == Blocks.BARRIER ? false : " return blockIn == Blocks.BARRIER ? false : blockIn.getDefaultState().isFullCube() || blockIn == this || blockIn == Blocks.GLASS || blockIn == Blocks.STAINED_GLASS || blockIn == Blocks.STAINED_GLASS_PANE || blockIn instanceof BlockPane; }This fixes all glass panes and iron bars.
The bug
Glass panes and iron bars connect to barrier blocks.
Suggested fix
Based off of Minecraft 1.11, MCP 9.35
net.minecraft.block.BlockPane.canPaneConnectToBlock(Block blockIn)public final boolean canPaneConnectToBlock(Block blockIn) { //added "blockIn == Blocks.BARRIER ? false : " return blockIn == Blocks.BARRIER ? false : blockIn.getDefaultState().isFullCube() || blockIn == this || blockIn == Blocks.GLASS || blockIn == Blocks.STAINED_GLASS || blockIn == Blocks.STAINED_GLASS_PANE || blockIn instanceof BlockPane; }This fixes all glass panes and iron bars.
Glass panes and iron bars connect to barrier blocks
relates to
Maria Lemón
Was the fix of
MC-48150/MC-46432make fences and walls not to connect or to make glass and iron bars connect ?it's meant to be an invisible barrier; it doesn't make any sense for the glass pane/iron bars to connect to what appears to be air
Looks nice if you want fences or iron bars connecting to nothing (to... just nothing).
Confirmed for 15w49b.
Confirmed for 16w15a and 16w15b
Confirm for 1.9.3 pre-2
Confirmed for 1.9.4
Confirmed for 16w20a
They no longer seem to connect to structure voids in 1.10.2.
Confirmed for 17w13b
problem: how would you get the original result (the panes appearing to connect to nothing) rather then then this? someone asked about this on planetminecraft and its a good point... some people want/need the panes to connect to the barries (i built a flag pole that i used barriers to make it connect and look imo better and more realistic)
its like quasi connectivity (layer 1,2,3 blocks piston,air,redstone block update the piston itll change) where although its a bug the problems made by removing it would be worse then keeping it (again flagpoles, the pmc post talks about power cables/wires)
what if you want a 1.5 wide glass door? cant make that if nothing invisible connects to the glass
what if you want a pathway for the player to go but it goes by glass? cant do if glass connects
so although better for both you cant do that as itd be impossible to make glass connect only when wanted... or it would be if you only want one option:
why not something like how you have wet sponge and sponge use the same id but have seperate damage values? aka connecting is 0 (so people dont have to replace all the already used barriers) while not connecting means it has damage of 1? (also yes im calling it damage as thats basically what it is and im used to it thx to wool and too many items) this would be extremely useful as youre not sticking to one side and making the other side more annoyed then people who prefer it not connecting
if youd like i can post the link to the pmc forum post k
You couldn't in the first place without having one of the sides a full block; the barrier would be in the way.
Data values are being phrased out in favor of block states; the connecting states will be saved states later.
Barriers are supposed to be invisible blockades; having fences, glass panes and iron bars connect to them make them visible; likely unwanted visible.