This is such an extremely complex and specific bug that would basically require in-depth testing to even begin to understand how it happens, let alone fixing it. I have absolutely no idea how it works and I've tried everything.
So for example. A repeating command block that works is “gamemode a @a[x=10,y=-40,z=0,dx=10000000,dy=10000,dz=0,m=!a]” This causing any player who goes through that region of a world to turn to gamemode a. Replace “gamemode a” with “clear” and the same thing happens, proving it’s a general command issue, not an issue to gamemode like I originally thought.
Now doing “gamemode a @a[x=-9,y=-40,z=0,dx=-9,dy=181,dz=0,m=!a]” dosen’t work at all or it dosen’t have the precise location. Switching the x and dx variables sometimes causes weird undesirable effects and switching the y and dy variables can sometimes cause the specific location to just break all together and effect areas around the boundaries specified, usually above the limit stated.
The command “gamemode a @a[x=0,y=192,z=0,dx=0,dy=193,dz=0,m=!a]” effects the entire area above y=192 instead of exclusively the two blocks stated. Switching the two commands only makes the starting point of the effect begin at y=193 instead, completely ignoring y=192, yet still effecting everything above y=193.
I’m still learning the basics of command blocks but all this seems to me like glitches. I read online in a Minecraft guide that the way this command should word is the lowest number is x, y, z, and higher is dx, dy, dz, yet even that I have proof that isn’t the case since -10000000 is lower then -10 yet I had to use in a different command -10 first before -10000000.
Comments 2
One thing I can see you're doing wrong is that dx/dy/dz are not the coordinates of the opposite corner of the area, they're distances from (x,y,z) along each axis. Also, the large magnitudes you've given for some parameters might be causing a problem. I know from experience that many commands are rejected with an error if their effective area includes chunks that haven't been generated yet.
Because these misunderstandings give you incorrect expectations, I can't tell whether you've found a bug, so I have to close this report as Invalid. If, when you understand the parameters better, you still see evidence of a bug, feel free to create a new report to describe it.
You might want to consider looking to other forums for community support to help you understand the commands and their parameters. Unfortunately, the bug tracker can only accept bug reports; we don't have the resources to provide community support.
One thing I can see you're doing wrong is that dx/dy/dz are not the coordinates of the opposite corner of the area, they're distances from (x,y,z) along each axis. Also, the large magnitudes you've given for some parameters might be causing a problem. I know from experience that many commands are rejected with an error if their effective area includes chunks that haven't been generated yet.
Because these misunderstandings give you incorrect expectations, I can't tell whether you've found a bug, so I have to close this report as Invalid. If, when you understand the parameters better, you still see evidence of a bug, feel free to create a new report to describe it.
You might want to consider looking to other forums for community support to help you understand the commands and their parameters. Unfortunately, the bug tracker can only accept bug reports; we don't have the resources to provide community support.