ct.flow, ct.u.wait, ct.tween should operate based on ct.delta, with optional setTimeout mode

Describe the current state of the problem ct.flow, ct.tween and the built-in method ct.u.wait all work with time. Internally, they use setTimeout, which is good for UI and most gameplay-related cases, but will fail if a game developer uses slo-mo effects or has, in the opposite, time acceleration controls (a la Sims), as these change ct.delta on which is based all the ct.js’ logic.

Describe the solution you’d like

All time-based methods should work with ct.delta by default. Optional parameters should be present to enable the old behavior, as it is needed for UI and other events that are off the main game loop. I think it is safe to name all these cases as UI actions.

For example:

• ct.tween.add gets a new parameter in its options, ignoreDelta;
• ct.flow.timer and others get an optional argument ignoreDelta.

[CosmoMyzrailGorynych]

@naturecodevoid, sure! I now think, though, that there should be pairs of methods instead of methods with additional options (ct.tween.add and ct.tween.addUi, for example), as it will be more readable and and uniform compared to existing methods in ct.mouse and ct.touch.

[CosmoMyzrailGorynych]

Edit: Would you mind if I try to create ct.timer?

@naturecodevoid better expand ct.js’ core library, as timers are pretty essential to gamemaking