>Several big functions may not fit 0.25s (a pulse time?).

That's why I'm tracking the data...to find out.

>Did you guys consider splitting them into several smaller
>pieces and spear across different pulses within a tick?

Right now, the functions that are causing things to be out of whack are because they are written poorly, and have been easily refactored into the existing infrastructure. If I get to a point where that is not the case, I'll think about it. I agree different != bad, but there are also things to keep in mind like "Will people be able to determine a tick is coming if XYZ always happens here", which used to be the case with some things.