returning angles in different ways

[behind_you]

ok I am making a code that requires self.angles_y.

self.angles_y is ranged between -180 and 180

how can i make it so that it has no range (ie it increases when you turn right, decrease when you turn left). using the -180 180 range or the 0 360 range causes problems. when your angle is 180 and it increases, it instantly becomes -180.

any help is appreciated

[Spike]

you may need to consider quadrants and to possibly add 360 to one angle if you're comparing them.

otherwise, avoid the use of writeangle even in engine code. good luck with that...

[behind_you]

hmm. what are quadrants?

i could add 360 every time it hits 359. not the best way..

[Spirit]

Not sure if this is what spike means but quadrants are what you get when you divide the circle into 4 parts, eg 0-90, 90-180 and so on. What quadrant is called what might differ on context so I won't mention that.

[behind_you]

Not sure if this is what spike means but quadrants are what you get when you divide the circle into 4 parts, eg 0-90, 90-180 and so on. What quadrant is called what might differ on context so I won't mention that.

i remember this in math class. thanks spirit.

So i guess there's no type of .movement vector but for turning? bummer...

[Spike]

diff = new - old;
if (diff > 180)
diff -= 360;
if (diff < -180)
diff += 360;

of course, if they do manage to do a 180 degree turn in the span of a single frame, your mod will think they're turning the other way around. If your framerate is 72fps+, that's not really a likely situation (unless they're using various rj/turn scripts).