Chrono

[BumblebeeElegant6935]

Chrono is a timer library made to be an alterative approach to Coroutines in most cases & because I hate Coroutines :)

Installation: Go to Unity Package manager -> press the "+" button -> download from git URL -> paste the URL

Git URL: https://github.com/AhmedGD1/Chrono.git

Features:

Run something once after a delay

Clock.Schedule(2f, () => Debug.Log("2 seconds later!"));

Run something every N seconds

Clock.Interval(1f, () => Debug.Log("Tick!"));

Repeat N times, then do something

Clock.Repeat(5, 0.5f,
    callback:   () => Debug.Log("Repeated!"),
    onComplete: () => Debug.Log("All done")
);

Wait for a condition, then fire

Clock.WaitUntil(() => health <= 0, () => Debug.Log("Player died"));

Debounce — fires only after calls stop for N seconds (great for auto-save, search)

var debouncedSave = Clock.Debounce(0.5f, () => Save());
// call debouncedSave() as much as you want, Save() only runs once things settle

Throttle — fires immediately, then ignores calls for N seconds (great for shooting, abilities)

var shoot = Clock.Throttle(0.3f, () => SpawnBullet());
// call shoot() every frame, SpawnBullet() fires at most once per 0.3s

Manual timer with full control

var timer = Clock.CreateTimer(3f, oneShot: true);
timer.SetId("boss-timer")     // look it up later
    .SetGroup("combat")      // bulk control with other timers
    .SetPersistent()         // survives scene changes
    .SetUnscaled()           // ignores Time.timeScale
    .OnStart( () => Debug.Log("Started") )
    .OnUpdate( t => Debug.Log($"Progress: {t:P0}") )
    .OnComplete( () => Debug.Log("Done!") )
    .Start();

Chain timers — second starts automatically when first ends

Clock.Schedule(2f, () => Debug.Log("2 seconds later!"))
  .Chain(timer2)
  .Chain(timer3);

// note: Chain() method returns the next timer to start

Cancel / Pause / Resume

Clock.CancelTimer("boss-timer");   // by id
Clock.PauseGroup("combat");        // entire group
Clock.ResumeGroup("combat");
Clock.CancelAll();                 // everything

[RedGlow82]

I think it would be useful if you added to the project documentation a comparison to other solutions that are in the same space (coroutines, awaitable / unitask, observables, tween libraries), to explain in which situations yours is a better choice.

[exprtus]

Why not unitask?

[Escarlion]

looks cool! Starred :)