I'm making a Skywars map that requires some areas always active, so I have to use "tickingarea" command. I put the following command: /tickingarea add 16 5 18 -28 100 -32 Lobby, but when I click Enter to execute the command, the coordinates of the Tickingarea that creates doesn’t match with the coordinates: when I put from 16 5 18 to -28 100 -32, it creates from -32 0 -32 to 31 0 31, area that doesn’t cover a single block of my area. I think it’s a bug because the feedback didn’t advise me of a syntax error or something like that. Here is the video:
MCPE-132759
My TickingArea size does not match with the size I put on the commands
Resolved
Cannot Reproduce
0
1. The Y coordinate for tickingarea does not matter, and it just stored as 0. The ticking area will cover the entire vertical extent of the chunk.
2. Ticking areas will always cover entire chunks. So the minimum X and Z values you enter will always be rounded down to the next multiple of 16. The minimum X value you entered was -28, which is rounded down to -32. The minimum Z value you entered was -32, so this remains unchanged.
3. Similarly, the maximum X and Z values will always be rounded up to the next multiple of 16 minus 1. So your minimum Z and Z values of 16 and 18 both get rounded up to (32-1) = 31.
It is generally easier to understand if you enter the lower coordinates of the ticking area first, which would make your command be:
/tickingarea add -28 100 -32 16 5 18 Lobby
though the result will be unchanged.
What range of X and Z values are you actually expecting your ticking area to have?
This ticket has been temporarily closed as Awaiting Response. It will automatically reopen when you comment with new information. Please be sure to answer all questions in a comment (not by editing the Description) so that the responses can be followed. Tickets that do not contain enough information may be closed as Incomplete.