When using direction detection (testfor and components rx, rxm, ry, and rym), the command argument fails if either rym or ry is over 180. However, the yRot component of the tp command will accept values over 180. So either I'm putting in the testfor components wrong, or this isn't working right.
Comments 3
Still an issue, not sure why this hasn't been looked at. Allowing the command to work up to 360 allows specific ry ranges to work. There's no way this is working as intended, as this is how it worked when it was first implemented. If it is, please change it back.
Cleaning up old tickets: This ticket has not been updated recently so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Also, we'd recommend making use of the search feature before writing a new bug report, as it's very likely that the issue has been mentioned already, and you can add a vote and any new information to the main ticket.
For any queries with your account or billing, you will need to contact Mojang Customer Support directly.
For feature requests or feedback, please head over to the Minecraft Feedback Site where you can search and vote for existing topics, or add a new thread if necessary.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
To avoid confusion, rx and rxm is looking between straight up and down, and its range is -90 - 90. ry and rym is looking N, E, S, and W and is suppsoed to to go from either -180 - 180 or 0 - 360. As I mentioned, ry is what's not working right.