bevy-timers

Bevy timers manage time-based actions by tracking the progression and completion of timer objects using tick(time.delta()). You can model countdowns, cooldowns, and recurring actions by checking finished() or just_finished() states every frame.

TimerMode::Once runs a single countdown cycle and stops, while TimerMode::Repeat automatically resets the timer upon completion. These modes allow you to drive both one-time delayed events and continuous recurring actions within your Bevy systems.

You can attach a timer as a component to individual entities to manage per-entity cooldowns. Ticking the component-stored timer each frame allows you to independently track and trigger time-based actions specific to that entity.

Yes, Local timers enable frame-scoped timing within individual Bevy systems. By inserting a Local<Timer> and calling tick(time.delta()), you can manage system-internal timing logic without needing global resources or entity components.

Yes, Bevy timers expose duration, reset, and fraction access for precise control. You can query the elapsed fraction to drive continuous animations or progress bars alongside standard finished and just_finished state checks.

A Bevy timer as a resource drives global time-based events across the entire app, whereas component timers manage per-entity cooldowns. Resources are ideal for centralized scheduling where multiple systems need to react to a single shared countdown.