The bug
The /fill and /setblock commands are broken when used with iron bars, glass panes, stairs and fences. As you can see, iron bars don't attach to nearby blocks, this is the same with fences.
Linked issues
is duplicated by 20
MC-123097
/setblock and /fill do not update block states
Resolved
MC-129184
Glass panes and Irob Bars don't update
Resolved
MC-129971
ironbars act funny (fill command)
Resolved
MC-130478
/fill doesn't connect glass panes to other blocks
Resolved
MC-131606
fiil and setblock command with iron bars, glass pane and stained glass pane does not behave properly
Resolved
MC-132564
After using fill command to fill iron railings, iron railings will not be connected.
Resolved
MC-133235
Fences Not Connecting With /Fill
Resolved
MC-135271
Glass pane bug
Resolved
MC-135335
Fill command doesn't connect glass panes
Resolved
MC-135992
Glass panes don't connect to blocks when using /fill or /setblock
Resolved
MC-137951
"Broken" glass panel
Resolved
MC-145336
Glass Pane Bug
Resolved
MC-146232
Command block placing
Resolved
MC-147245
Glass Not Generating Properly with /fill Command
Resolved
MC-154849
/fill command on glass pane doesn't connect to the sides.
Resolved
MC-156936
Iron bars fill command
Resolved
MC-157044
Fences don't connect together
Resolved
MC-157832
Error loading glass pane with "fill" command
Resolved
MC-162659
there is a problem with "/fill" command
Resolved
MC-169934
fill command bug with glass_panes, fences...
Resolved
relates to 3
Attachments
Comments 9
you could also add facing to it, for example /fill 2 4 2 6 6 6 orange_stained_glass_pane[north=true,south=true]
Confirmed for 1.13.1.
This seems to be a duplicate of MC-123097.
Occurs in 1.13.2 too!
[media]They also don't trigger observers when a tree grows next to them despite visually changing. This used to work (via bud mechanics) until extended block states were introduced, but since the flattening removed fences extended state, this should once again work.
I'm not sure if this deserves it's own post or just as a note on this one, they seem very similar.
CAnnot reproduce in 20w30a
I am no longer able to reproduce this issue in 20w51a.
I think this was fixed in 1.16 pre-release 6, same version when MC-191096 and other similar issues became a thing.
Most probably same cause as MC-123087