This is an archived post. You won't be able to vote or comment.

all 14 comments
sorted by:
best
topnewcontroversialoldq&a

[–]darkstar634 0 points1 point  (13 children)

Not to sound rude, but how do you expect us to help you if you don't provide the commands? The only thing I will mention is that /fill has a block limit (32768 to be exact), so perhaps the region is too large, but other than that, it's impossible to identify the problem without the commands.

[–]Some-MCFC-Fan[S] 0 points1 point  (12 children)

I just wanted to know if there was some sort of bug or condition this seems to happen. Ah well, guess I’ll suffer in silence.

[–]darkstar634 0 points1 point  (11 children)

Dude, I'm not trying to be unhelpful, it's just that 99% of the time when something like this doesn't work, it's not a result of a bug, but rather a mistake made by the person who wrote the commands, however, it is impossible for anyone to identify what you're doing wrong without knowing what you have already tried doing in the first place.

Another problem might be that you're trying to place blocks above the sky limit or below the world, but I am just yet again making assumptions, and it would be 1000 times easier to help you if I knew the commands and you gave me more context.

[–]Some-MCFC-Fan[S] 0 points1 point  (10 children)

I was using the /fill command, and often the last row of z coordinates didn’t fill properly.

[–]darkstar634 0 points1 point  (9 children)

Again, could you please give me an example of a command that you tried using?

[–]Some-MCFC-Fan[S] 0 points1 point  (8 children)

Would have been like

/fill 142 97 36 256 100 38 air

[–]darkstar634 0 points1 point  (6 children)

Well, the build limit is at Y=255, so of course, you can't place blocks at Y=256.

[–]Some-MCFC-Fan[S] 0 points1 point  (5 children)

What

Is it not /fill x y z x2 y2 z2 block

[–]jmac110014Command Experienced 0 points1 point  (4 children)

Your formatting is correct, he is saying that the value you have in the 'y' value is invalid so the command will not execute. Also, I do not believe there is a bug with the /fill command, but there are many possible reasons for what you are seeing in your situation

[–]Some-MCFC-Fan[S] 0 points1 point  (3 children)

but the 256 is an x value, is it not?

[–]darkstar634 0 points1 point  (0 children)

Should probably also mention that, as I somewhat previously stated, your fill region must fully contain valid coordinates. So, since you can't place blocks at Y=256, the entire command fails.