thedivergentai/game-dev-agentic-skills

bevy-animation-graph

Bevy ECS skill for animation blending.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/thedivergentai/game-dev-agentic-skills --skill bevy-animation-graph

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Bevy animation graph

When to use

Load this when clips must blend, add, or mask. Single-clip playback stays on bevy-animation.

ECS shape

  • Assets: AnimationGraph describes how clips blend. add_clip parents a clip node. add_blend parents a blend node. add_clip_with_mask stores a u64 mask (bone groups you assign; 0 means no mask).
  • Components: AnimationGraphHandle is a handle to the graph used by the AnimationPlayer on the same entity. AnimationTransitions crossfades between nodes.
  • Weights: ActiveAnimation::set_weight on the player, after play, drives a node that is already in the graph.
  • Systems: evaluation still runs through the animation player systems. Do not add a second player.
rust
#[derive(Resource)]
struct LocomotionNodes {
    graph: Handle<AnimationGraph>,
    walk: AnimationNodeIndex,
    run: AnimationNodeIndex,
}

fn build_locomotion_graph(
    mut commands: Commands,
    asset_server: Res<AssetServer>,
    mut graphs: ResMut<Assets<AnimationGraph>>,
) {
    let mut graph = AnimationGraph::new();
    let blend = graph.add_blend(0.5, graph.root);
    let walk = graph.add_clip(
        asset_server.load(GltfAssetLabel::Animation(0).from_asset("models/fox.glb")),
        1.0,
        blend,
    );
    let run = graph.add_clip_with_mask(
        asset_server.load(GltfAssetLabel::Animation(1).from_asset("models/fox.glb")),
        0b0011,
        1.0,
        blend,
    );
    let handle = graphs.add(graph);
    commands.insert_resource(LocomotionNodes {
        graph: handle,
        walk,
        run,
    });
}
rust
#[derive(Resource)]
struct LocomotionNodes {
    graph: Handle<AnimationGraph>,
    walk: AnimationNodeIndex,
    run: AnimationNodeIndex,
}

fn attach_player(
    mut commands: Commands,
    nodes: Res<LocomotionNodes>,
    mut players: Query<(Entity, &mut AnimationPlayer), Without<AnimationGraphHandle>>,
) {
    for (entity, mut player) in &mut players {
        commands.entity(entity).insert((
            AnimationGraphHandle(nodes.graph.clone()),
            AnimationTransitions::new(),
        ));
        player.play(nodes.walk).repeat();
        player.play(nodes.run).repeat();
    }
}
rust
#[derive(Resource)]
struct LocomotionNodes {
    graph: Handle<AnimationGraph>,
    walk: AnimationNodeIndex,
    run: AnimationNodeIndex,
}

#[derive(Component)]
struct RunBlend(f32);

fn sync_blend(mut players: Query<(&mut AnimationPlayer, &RunBlend)>, nodes: Res<LocomotionNodes>) {
    for (mut player, blend) in &mut players {
        if let Some(active) = player.animation_mut(nodes.run) {
            active.set_weight(blend.0.clamp(0.0, 1.0));
        }
        if let Some(active) = player.animation_mut(nodes.walk) {
            active.set_weight(1.0 - blend.0.clamp(0.0, 1.0));
        }
    }
}
rust
use std::time::Duration;

#[derive(Resource)]
struct LocomotionNodes {
    graph: Handle<AnimationGraph>,
    walk: AnimationNodeIndex,
    run: AnimationNodeIndex,
}

#[derive(Component)]
struct RunBlend(f32);

fn fade_to_run(
    nodes: Res<LocomotionNodes>,
    mut query: Query<(&mut AnimationPlayer, &mut AnimationTransitions, &RunBlend)>,
) {
    for (mut player, mut transitions, blend) in &mut query {
        if blend.0 > 0.5 {
            transitions.play(&mut player, nodes.run, Duration::from_millis(180));
        }
    }
}
toml
[dependencies]
bevy = "0.20"

Graph choices

NeedBevy approach
Blend clipsAnimationGraph plus AnimationGraphHandle
Gameplay modeApp or entity states stay on bevy-state-machines. The graph is not that state type.
Additive layerAnimationGraph::add_additive_blend inserts AnimationNodeType::Add. Clip weights still go through ActiveAnimation::set_weight.

Scope

  • Crossfades use AnimationTransitions::play with a Duration, as in fade_to_run.
  • Persisting a graph is SerializedAnimationGraph plus ron. A 1D or 2D blend-space type is not part of AnimationGraph; blend with node weights.

Expert Knowledge Delta

Target: Bevy 0.20+.

Core ECS types: Component, Resource, Query, Commands, Startup, Update, Fixed / FixedMain (bevy::time), .chain(), Plugin, DefaultPlugins, MinimalPlugins. Messages and observers are an ownership slot. See bevy-events-messaging for their APIs. Systems run in parallel unless .chain() orders the ones that conflict.

Who owns state

PieceOwnerWho may mutateSchedule
Data on one entityComponentOne system via QueryUpdate or FixedMain
One value for the whole appResourceOne systemStartup to insert, then the schedule that reads it
SpawnCommandsThe spawning systemStartup for the initial world; later schedules for runtime spawn
Order that must not race.chain()The chained systems onlySame schedule
Plugin boundaryPluginbuild registers systems and resourcesBefore the app runs

Borrow rule: two systems that both mutably query the same component must be ordered (.chain()) or split so only one writes. Unrelated systems stay parallel. That is the ECS page rule, not a guess at a system-set API.

Decision

If you needDo thisDo not
Per-entity dataComponent + QueryA script field copied onto the entity
App-wide config or clockResourceCopy the value onto every entity
Stable simulation stepFixedMain and the Fixed clockTie simulation to raw frame Update
Startup spawnCommands in StartupSpawn from a render system
Cross-system notice that is not shared stateMessage or observer slot in bevy-events-messagingA new event type invented in this file
An API outside the documented setCheck the official docs firstA made-up crate or API

Load references/ecs-ownership.md for the ownership table.

NEVER

  • Do not pin /0.20.0/ in docs URLs. WHY: links stay on latest; the 0.20 target is stated once in prose.
  • Do not mutably query the same component from two unordered systems. WHY: the schedule runs systems in parallel unless .chain() orders them.
  • Do not invent a physics, navigation, networking, or XR crate here. WHY: this skill only names documented Bevy crates and modules.
  • No AnimationTree, BlendSpace, or scene-tree state-machine types in Bevy code. WHY: AnimationGraph, AnimationGraphHandle, and AnimationTransitions are the documented Bevy pieces.
  • No invented APIs or unnamed third-party crates as the chosen solver. WHY: Bevy code stays idiomatic ECS and uses only documented Bevy APIs.

Reference

Official links stay on bevy.org. The library pin on bevy-master stays 0.20.0.

Official Documentation

  • Assets - Official asset catalog. No third-party crate was selected.
  • Examples - Example tree on the latest branch.
  • ECS - Component, systems, Query, Startup, Update, and .chain().
  • Plugins - Plugin, DefaultPlugins, MinimalPlugins, and add_plugins.

Related Skills

Prerequisites

Complements

Downstream / consumers

  • None yet.

Master

来自同一仓库

更多 Skills

全部 Skills
thedivergentai
社区

godot-combat-system

Expert patterns for combat systems including hitbox/hurtbox architecture, damage calculation (DamageData class), health components, combat state machines, combo systems, ability cooldowns, and damage popups. Use for action games, RPGs, or fighting games. Trigger keywords: Hitbox, Hurtbox, DamageData, HealthComponent, combatstate, combosystem, abilitycooldown, invincibilityframes, damagepopup.

1小时安装量
1
GitHub Stars
977
最近更新
10月16日
thedivergentai
社区

godot-2d-animation

Expert patterns for 2D animation in Godot using AnimatedSprite2D and skeletal cutout rigs. Use when implementing sprite frame animations, procedural animation (squash/stretch), cutout bone hierarchies, or frame-perfect timing systems. Trigger keywords: AnimatedSprite2D, SpriteFrames, animationfinished, animationlooped, framechanged, frameprogress, setframeandprogress, cutout animation, skeletal 2D, Bone2D, procedural animation, animation state machine, advance(0).

1小时安装量
2
GitHub Stars
969
最近更新
10月16日
thedivergentai
社区

godot-camera-systems

Expert patterns for 2D/3D camera control including smooth following (lerp, positionsmoothing), camera shake (trauma system), screen shake with frequency parameters, deadzone/drag for platformers, look-ahead prediction, and camera transitions. Use for player cameras, cinematic sequences, or multi-camera systems. Trigger keywords: Camera2D, Camera3D, SpringArm3D, positionsmoothing, camerashake, traumasystem, lookahead, dragmargin, cameralimits, cameratransition.

1小时安装量
2
GitHub Stars
969
最近更新
10月16日
thedivergentai
社区

godot-dialogue-system

Expert patterns for branching dialogue systems including dialogue graphs (Resource-based), character portraits, player choices, conditional dialogue (flags/quests), typewriter effects, localization support, and voice acting integration. Use for narrative games, RPGs, or visual novels. Trigger keywords: DialogueLine, DialogueChoice, DialogueGraph, dialoguemanager, typewritereffect, branchingdialogue, dialogueflags, localization, voiceacting.

1小时安装量
2
GitHub Stars
969
最近更新
10月16日