#bevy #sequence #command #action


A Bevy library for executing various actions in a sequence

7 releases (breaking)

0.7.0 Mar 7, 2023
0.6.0 Nov 15, 2022
0.5.0 Sep 8, 2022
0.4.0 Aug 19, 2022
0.1.0 May 12, 2022

#87 in Game dev

Download history 11/week @ 2022-12-03 6/week @ 2022-12-10 6/week @ 2022-12-17 45/week @ 2022-12-24 49/week @ 2022-12-31 39/week @ 2023-01-07 1/week @ 2023-01-14 10/week @ 2023-01-21 16/week @ 2023-01-28 14/week @ 2023-02-04 17/week @ 2023-02-11 19/week @ 2023-02-18 4/week @ 2023-02-25 29/week @ 2023-03-04 22/week @ 2023-03-11 10/week @ 2023-03-18

65 downloads per month


1.5K SLoC

Bevy Sequential Actions

A Bevy library that aims to execute a queue of various actions in a sequential manner. This generally means that one action runs at a time, and when it is done, the next action will start and so on until the queue is empty.


Getting Started


In order for everything to work, the SequentialActionsPlugin must be added to your App.

use bevy::prelude::*;
use bevy_sequential_actions::*;

fn main() {

Modifying Actions

An action is anything that implements the Action trait, and can be added to any Entity that contains the ActionsBundle. An entity with actions is referred to as an agent. See the ModifyActions trait for available methods.

fn setup(mut commands: Commands) {
    let agent = commands.spawn(ActionsBundle::new()).id();
        // ...

Implementing an Action

The Action trait contains two methods:

  • The on_start method which is called when an action is started.
  • The on_stop method which is called when an action is stopped.

In order for the action queue to advance, every action has to somehow signal when they are finished. There are two ways of doing this:

  • Using the ActionFinished component on an agent. By default, a system at the end of the frame will advance the queue if all active actions are finished. This is the typical approach as it composes well with other actions running in parallel.
  • Calling the next method on an agent. This simply advances the queue at the end of the current stage it was called in. Useful for short one-at-a-time actions.

A simple wait action follows.

pub struct WaitAction {
    duration: f32, // Seconds
    current: Option<f32>, // None

impl Action for WaitAction {
    fn on_start(&mut self, agent: Entity, world: &mut World, _commands: &mut ActionCommands) {
        // Take current duration (if paused), or use full duration
        let duration = self.current.take().unwrap_or(self.duration);

        // Run the wait system on the agent

    fn on_stop(&mut self, agent: Entity, world: &mut World, reason: StopReason) {
        // Remove the wait component from the agent
        let wait = world.entity_mut(agent).remove::<Wait>();

        // Store current duration when paused
        if let StopReason::Paused = reason {
            self.current = Some(wait.unwrap().0);

struct Wait(f32);

fn wait_system(mut wait_q: Query<(&mut Wait, &mut ActionFinished)>, time: Res<Time>) {
    for (mut wait, mut finished) in wait_q.iter_mut() {
        wait.0 -= time.delta_seconds();

        // Confirm finished state every frame
        if wait.0 <= 0.0 {


One thing to keep in mind is that you should not modify actions using World inside the Action trait. We cannot borrow a mutable action from an agent while also passing a mutable world to it. Since an action is detached from an agent when the trait methods are called, the logic for advancing the action queue will not work properly.

This is why ActionCommands was created, so you can modify actions inside the Action trait in a deferred way.

pub struct SetStateAction<S: States>(S);

impl<S: States> Action for SetStateAction<S> {
    fn on_start(&mut self, agent: Entity, world: &mut World, commands: &mut ActionCommands) {
        // Set state

        // Bad. The action queue will advance immediately.
        // Good. The action queue will advance a bit later.

        // Also good. Does the same as above.
        commands.add(move |w: &mut World| {

        // Also good. By default, the action queue will advance at the end of the frame.

    fn on_stop(&mut self, _agent: Entity, _world: &mut World, _reason: StopReason) {}


See the examples for more usage, specifically the shared actions. Each example can be run with cargo run --example <example>. Consider running with --release as debug builds can be quite slow.

Example Description
basic Shows the basic usage of the library by adding some actions and then quitting the app.
pause Shows how to pause and resume an action when pressing space.
repeat Shows how to add actions that repeat n times and forever.
parallel Shows how to add a collection of actions that run in parallel.
moba Shows how actions can be used to control a unit. Right click for movement, hold down left shift for queueing movements and press space for canceling everything.


bevy bevy-sequential-actions
0.10 0.7
0.9 0.6
0.8 0.3 — 0.5
0.7 0.1 — 0.2


~228K SLoC