Every time I try and use a fill command over a distance of more than 40x40 blocks (on the x and z axes, y doesnt seem affected) I get a "Cannot place blocks outside of the world" error message. This makes creative mode essentially unplayable. I'm aware there has always been a limit (for performance reasons, including both distance and number of blocks filled) but up until recently it was never such a ridiculously SHORT distance. The limit used to be, basically, whatever your render distance was set to. Mine is set to 16 chunks so I should easily be able to fill more than 40x40 blocks. Used to be able to fill something like 100x3x100 at a time.
Linked issues
Attachments
Comments 3
yeah there seems to be a problem when you go over a certain set of x or z cords its as if the game things that 0 and neg cords in the x or z pos are below world kill wall or at max height ive been playing around with it keeping one cord the same [the cord past the "world barrier"] and moving the other ~ ~ ~ cord closer and closer still says "Cannot place blocks outside of the world" this is a problem that needs to be fixed because why would i not be able to command a block why i commanded it to go ?
this shouldn't have intentional then, as there should have be a way to place blocks past what the game is thinking is the "world barrier" and its set of cords, there is a small chunk of land that you cannot place blocks using commands ive gone on an took at least an hour confirming over and over again that this small chunk from 12-0-"-12" on the x axis cannot have blocks commanded into no matter how big or small i made the two sets of cords from each other they all would work within the bounds of the error chunk. P.S. he wasn't talking about size rates he was confirming if this was a bug or not, saying the error was intentional is outrages lol, ive read all your other comments on other post and you think you know every bug in the games code and you are misinterpreting peoples bug fix request there are a lot of bugs now that have been passed because "someone" thought they were being useful
This is intentional its been that way, for performance reasons, there's always been a cap for how far you can use the fill command, this report should be closed.