사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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:
AnimationGraphdescribes how clips blend.add_clipparents a clip node.add_blendparents a blend node.add_clip_with_maskstores au64mask (bone groups you assign;0means no mask). - Components:
AnimationGraphHandleis a handle to the graph used by theAnimationPlayeron the same entity.AnimationTransitionscrossfades between nodes. - Weights:
ActiveAnimation::set_weighton the player, afterplay, drives a node that is already in the graph. - Systems: evaluation still runs through the animation player systems. Do not add a second player.
#[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,
});
}#[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();
}
}#[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));
}
}
}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));
}
}
}[dependencies]
bevy = "0.20"Graph choices
| Need | Bevy approach |
|---|---|
| Blend clips | AnimationGraph plus AnimationGraphHandle |
| Gameplay mode | App or entity states stay on bevy-state-machines. The graph is not that state type. |
| Additive layer | AnimationGraph::add_additive_blend inserts AnimationNodeType::Add. Clip weights still go through ActiveAnimation::set_weight. |
Scope
- Crossfades use
AnimationTransitions::playwith aDuration, as infade_to_run. - Persisting a graph is
SerializedAnimationGraphplusron. A 1D or 2D blend-space type is not part ofAnimationGraph; 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
| Piece | Owner | Who may mutate | Schedule |
|---|---|---|---|
| Data on one entity | Component | One system via Query | Update or FixedMain |
| One value for the whole app | Resource | One system | Startup to insert, then the schedule that reads it |
| Spawn | Commands | The spawning system | Startup for the initial world; later schedules for runtime spawn |
| Order that must not race | .chain() | The chained systems only | Same schedule |
| Plugin boundary | Plugin | build registers systems and resources | Before 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 need | Do this | Do not |
|---|---|---|
| Per-entity data | Component + Query | A script field copied onto the entity |
| App-wide config or clock | Resource | Copy the value onto every entity |
| Stable simulation step | FixedMain and the Fixed clock | Tie simulation to raw frame Update |
| Startup spawn | Commands in Startup | Spawn from a render system |
| Cross-system notice that is not shared state | Message or observer slot in bevy-events-messaging | A new event type invented in this file |
| An API outside the documented set | Check the official docs first | A 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 onlatest; 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, andAnimationTransitionsare 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
latestbranch. - ECS -
Component, systems,Query,Startup,Update, and.chain(). - Plugins -
Plugin,DefaultPlugins,MinimalPlugins, andadd_plugins.
Related Skills
Prerequisites
- bevy-master - Hub and schedules.
- bevy-ecs-composition - Components and systems.
- bevy-animation - Player and clips the graph drives.
Complements
- bevy-state-machines - Gameplay mode is not an animation graph.
- godot-animation-tree-mastery - Same topic on the Godot track.
Downstream / consumers
- None yet.
Master
- bevy-master - Bevy router.