I'm very confused. It seems like 2 people are trying to tell me that C3 wraps "AngleOfMotion" between 0 to 360. But the C3 debugger proves that the value for the bullet's "AngleOfMotion" property is wrapped between a range of -180 to 180 degrees. So if you want to compare "AngleOfMotion" in any way you need to know that, or your comparisons won't work as expected.
Asking a feature request
You can maybe tag Laura_D or maybe suggest here:
I'm not requesting a feature. I'm asking that a piece of missing information be added to the documentation.
Laura_D What do you think? Should this note be added to the documentation for bullet angle of motion?
The thing is, the Construct Engine doesn't take input angles as raw data. It always processes it first and converts it to radians, then to angle. That is recommended and users too should always use either System Angle Comparators like the Is Between Angles or make their own calculations
from degrees to radian then back to an angle within a selected degree scope.
Yes the angle comparators are great, but if you're comparing a bullet's angle of motion property you still NEED to know the angle wraps between -180 to 180 to compare correctly.
It actually doesn't wrap the value from between -180 and 180
Yes it does.
If you dl and run this c3p file in C3 you can play with it yourself. Run it in the debugger, pause it, then start plugging in values into the "AngleOfMotion" property.
This gif shows me doing that exact thing with the above sample project.