Do you think there's a similar restriction to how many collide callbacks as there are timer callbacks?
Even so, why add a new callback every time? Can't you still just use the original with "false" on the second last parameter or does that affect the functionality of it?
You know your script best, Behemoth
See if you can get that method up and running. But if you have to adjust every 60/30/10 timer loop you currently have to a 100 timer loop, you might have to implement some skipping. Perhaps store the values in, not SetInts but primitive
double variables? Ensure you have a large enough allocation ^^
100 loops per second is a strange number. 128 would make sense. Might be easiest to skip and split it into 50/25/10 if that's a desirable loop pace.