Can no longer place suspended cactus, sugar cane or bamboo via /setblock
Was working fine up to pre5 inclusive, but now they immediately break.
Fire, soul fire, redstone wire, detector rails, powered rails and activator rails have been bugged in a similar way for a considerably longer length of time.
Linked Issues
relates to4
MC-189867Cannot use /setblock and /fill to place blocks in positions they cannot normally be inFixedMC-191096Fences and walls can no longer be placed in invalid block states by using /setblock or /fillFixedMC-191698Cannot set "shape" block state of stairs with /setblockFixedMC-192498/fill and /setblock cannot set different directional block states of several blocks, such as glass panes and iron barsFixed
Created Issue:
Can no longer place suspended cactus, sugar cane or bamboo via /setblock
Was working fine up to pre5 inclusive, but now they immediately break.
Attachments3
Was working fine up to pre5 inclusive, but now they immediately break.
If you fix this, please also fix this for fire, soul fire, redstone dust, powered rails, detector rails and activator rails - these have been broken for far longer and not being able to manipulate these in the same way as other blocks severely hampers a lot of potential creative freedom.
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
relates to
Was working fine up to pre5 inclusive, but now they immediately break.
If you fix this, please also fix this for fire, soul fire, redstone dust, powered rails, detector rails and activator rails - these have been broken for far longer and not being able to manipulate these in the same way as other blocks severely hampers a lot of potential creative freedom.
Was working fine up to pre5 inclusive, but now they immediately break.
Fire, soul fire, redstone wire, detector rails, powered rails and activator rails have been bugged in a similar way for a considerably longer length of time.
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
relates to
Did you test in the 1.16 Pre-Release 7 before marking it as affected ? This Pre-Realease is supposed to fix the issue
Obviously I did, why are you assuming otherwise? Clearly it fixes all the other cases, otherwise I would have mentioned them here.
Do the other blocks mentioned have their own report(s)? If so, they should be marked as "relates to".