Due to the continuous nature of rotations being interrupted by the sudden switch from negative to positive, it was convenient that those arguments in selectors would be moduloed properly to wrap, so one could do something like this:
/testfor @a[rym=80,ry=-60]In the current version, the equivalent (/execute if entity @a[y_rotation=80..-60]) fails to build because "the minimum is greater than the maximum." In reality, it is not, because -60 should wrap to what amounts to 300.
Linked issues
is duplicated by 1
relates to 3
Comments 8
Can confirm for 18w01a.
Interestingly, y_rotation=170..190 behaves the same and gives the error that min cannot be bigger than max. So the parser seems to know that 190 = -170 in that case, so it actually shouldn't be that hard to fix this...
x rotation does not wrap, does it? and it's also logical it does not, as you cannot move your head over -90/90 degrees.
I think that using ! would be more intuitive... They should allow to use it to select outside a range (literally "not in this range").
michael
Confirmed for 17w50a