Bevy Platformer (thin router)

Genre router. Domain work lives in the Bevy skills below.

When to use

Load this to route a platformer to movement, camera, and tiles.

ECS shape

• Components hold the genre's per-entity flags as plain data. This file does not name new engine types.
• Resources hold run-wide counters (score, wave index, seed) via bevy-data-resources.
• Systems read those components on Update or the fixed timestep from bevy-master. Order them with .chain() when a later system must see the result.
• Schedule: gameplay mode changes go through bevy-state-machines. Do not invent a genre plugin.

Routing

• bevy-character-movement - Locomotion.
• bevy-camera-systems - Follow camera.
• bevy-tilemap - Ground tiles.
• bevy-2d-animation - Sprite clips.

Examples

[dependencies]
bevy = "0.20"

Coyote time and the jump buffer live on the mover. Gravity and the jump write velocity in one system so they cannot race.

#[derive(Component)]
struct Mover {
    velocity: Vec2,
    grounded: bool,
    coyote: f32,
    jump_buffer: f32,
}

fn arm_jump(keys: Res<ButtonInput<KeyCode>>, mut movers: Query<&mut Mover>) {
    if !keys.just_pressed(KeyCode::Space) {
        return;
    }
    for mut mover in &mut movers {
        mover.jump_buffer = 0.15;
    }
}