TheZaius

Mojang didn't address this properly and I had to find a solution elsewhere.

And your comment was only part right and only contributed to my confusion.

It only works the way one would naturally want it to work if the default game mode for a map is Adventure. It is only in that specific condition, as far as I know. Switching game mode to adventure in a map that's creative by default is not enough, apparently. It's still a ridiculous limitation but it's better than nothing.

Yes, debug stick works great but not on an automated, massive scale. Not even /clone works, as inconvenient a solution as that would be. It just sets everything to automatically connect, even if the cloned source has some blocks connecting and others not connecting.
1.16+ has a lot of great additions and options... but this bug completely holds it back in my view.

Yusufulus, nooooo, you don't understand this issue. The bug you brought up is easily fixed by specifying the states, as DutchMC mentioned in the comments of that bug, an option that was BROKEN by THIS current bug.
This bug is the single reason why I haven't updated to 1.16+. I am still on 1.15.2. I have scripts constantly running that use /setblock and /fill with specific block states that specify which blocks should have certain block states under which conditions. With this current bug, I no longer have control over that.
The issue you brought up has always been easily rectified.
This bug has no workaround whatsoever until Mojang fixes it.

Brevort, my initial comment back in June of last year mentioned seeing this with both /setblock and /fill.
Additionally, although this particular bug only mentions /setblock in the description, MC-191096, which mentions /setblock and /fill, is listed as a related bug.

Heh, I'm still on 1.15.2 because of this one bug. Completely ruins my adventure map I've been working on for over five years. I've just gotta hold out a little while longer.

Works as intended? Once the save has been opened in 1.16, what's the point in having Minecraft constantly remind me about custom worlds and then prompting me to save a backup? Why isn't one notification for the save file sufficient?

Brody, looks like it. Really, the adventure map I'm working on completely relies on these commands working so I'll have to wait until this bug is fixed before using 1.16. Back to 1.15.2, I guess.

I've observed this being an issue with /setblock and /fill commands and it also impacts fences and walls, specifically the east, west, north, south, and up states. I get a message saying "Could not set the block." It's as if when I type something like

/setblock 14 153 977 oak_fence[east=true,north=true]

The game just reads it like

/setblock 14 153 977 oak_fence

As if the [east=true,north=true] part was never typed.

Thanks for the clarification. I'm not quite sure how to use JSON text to edit books but if all I have to do to get this to work is to input the script each line in a Book and Quill, I think I can live with that.

Sorry, I'm new to this site. I was linked here by someone in the #minecrafthelp channel on IRC.
I noticed that the above mentioned bug was one that I was experiencing, except it's a problem with bold and random text scripts as well colored text. I'm currently using 1.8.1. I wasn't sure if I should create a new issue or just respond to an existing one.
I see that it says "Resolved" but is it resolved in the sense that it's supposed to be fixed or that it's acknowledged that it's a bug and that it's either going to be worked on or nothing can be done about it?