modulo on non integer numbers

ID:2250559
 
May 24 2017, 6:05 pm
Applies to:Dream Daemon
Status: Open
Issue hasn't been assigned a status value.
11:58 oranges !dm var/x = 371.3 % 360.0; world.log << x;;
11:58 Bot32 oranges: 11

python example
370.5 % 360
10.5

This would be useful to have for pixel projectiles and etc where that extra decimal value makes a difference over longer ranges and causes deflections

Otherwise we have to manually subtract 360 until it's normalised within the 360-0 range
May 24 2017, 6:09 pm
I realise we can work around this by figuring out the diff between the item and the rounded item and then readding it at the end, but it would be a nice convenience to have.
May 24 2017, 6:09 pm
Here's how I clamp (normalize?) angles:
angle + round(-angle, 360) // (-180, 180]
// or
angle - round(angle, 360) // [-180, 180)


Also, this is a duplicate: http://www.byond.com/forum/?post=1664849
May 24 2017, 6:12 pm
I don't search because byond forum search is sucky, but good spotting
May 24 2017, 6:13 pm
Also, pixel projectiles work better by scaling the vector from source to target, eliminating the need for angles in most cases.
May 24 2017, 6:13 pm
In response to Optimumtact
Optimumtact wrote:
I don't search because byond forum search is sucky, but good spotting

There's always Google.
May 24 2017, 6:17 pm
I guess an new operator that does it might be nice, %% or similar perhaps.
May 24 2017, 6:18 pm
In response to Kaiochao
I agree but unfortunately our implementation is usually just an angle of travel calculated by the vector between the source and target which is then discarded.

The use case for this is calculating the angle of incidence for reflections