跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

bevy-app-resources

Bevy ECS skill for app-wide resources and schedules. Keywords: Bevy, Resource, App, Schedule, Plugin.

thedivergentai · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill bevy-app-resources

技能说明


name: bevy-app-resources description: "Bevy ECS skill for app-wide resources and schedules. Keywords: Bevy, Resource, App, Schedule, Plugin."

Bevy app resources

When to use

Load this when data or logic must exist for the whole app: one clock, one ruleset, startup spawn, or an ordered pair of systems. Pair with bevy-data-resources for the component-versus-resource split.

ECS shape

  • App. The Apps page: an App contains a World and the outer loop. It initializes resources (one copy), adds systems to a Schedule, and imports other App changes through plugins.
  • Resources. Resource, Res, ResMut, and insert_resource (Resources page). Time arrives from add_plugins(DefaultPlugins).
  • Plugins. The Resources page implements Plugin and inserts the resource inside build. DefaultPlugins is the plugin set that adds Time. Name only the plugins this page documents.
  • Schedules. add_systems(Startup, ...) runs once before other systems. add_systems(Update, ...) is the repeating schedule in the ECS page. .chain() orders systems that must see each other's writes. bevy::ecs::message names FixedUpdate only as the schedule after which signal_message_update_system runs. Fixed-timestep clock types stay in bevy-character-movement.
  • States. App-wide modes are bevy::state, not a global node. See bevy-state-machines.

App choices

NeedBevy idiom
One copy for the whole appA Resource inserted on the App
Logic that ticks every frameA system on Update (or a chained pair)
Boot setupA Startup system or insert_resource in a Plugin
One-shot noticeA message or event. See bevy-events-messaging.

Scope

  • Insert app-wide data with insert_resource inside Plugin::build, or from a Startup system.
  • Order two systems that both mutably use the same resource with .chain().
  • Save files are a Resource you serialize yourself. The running copy stays in the World.

Examples

[package]
name = "app_resources"
version = "0.1.0"
edition = "2021"

[dependencies]
bevy = "0.20"

One rules resource, one startup spawn, and a pair of systems that must not race on Score.

#[derive(Resource)]
struct Ruleset {
    gravity: f32,
}

#[derive(Resource, Default)]
struct Score(u32);

#[derive(Component)]
struct Falling;

fn spawn_session(mut commands: Commands) {
    commands.spawn((Name::new("session"), Transform::default(), Falling));
}

fn apply_gravity(
    rules: Res<Ruleset>,
    time: Res<Time>,
    mut bodies: Query<&mut Transform, With<Falling>>,
) {
    let step = rules.gravity * time.delta_secs();
    for mut transform in &mut bodies {
        transform.translation.y += step;
    }
}

fn award(mut score: ResMut<Score>) {
    score.0 = score.0.saturating_add(1);
}

fn publish(score: Res<Score>, mut bodies: Query<&mut Transform, With<Falling>>) {
    let lift = score.0 as f32;
    for mut transform in &mut bodies {
        transform.translation.x = lift;
    }
}

pub struct RulesPlugin;

impl Plugin for RulesPlugin {
    fn build(&self, app: &mut App) {
        app.insert_resource(Ruleset { gravity: -9.8 })
            .init_resource::<Score>()
            .add_systems(Startup, spawn_session)
            .add_systems(Update, (apply_gravity, award, publish).chain());
    }
}

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_plugins(RulesPlugin)
        .run();
}

award and publish both touch Score or Transform. apply_gravity also writes Transform, so the three systems stay in one chain.

A second plugin only reads the rules resource.

#[derive(Resource)]
struct Ruleset {
    gravity: f32,
}

fn log_rules(rules: Res<Ruleset>) {
    let _gravity = rules.gravity;
}

pub struct HudPlugin;

impl Plugin for HudPlugin {
    fn build(&self, app: &mut App) {
        app.add_systems(Update, log_rules);
    }
}

Fixed-step simulation reads Time<Fixed> and stays on FixedUpdate.

#[derive(Component)]
struct Falling;

fn fixed_step(time: Res<Time<Fixed>>, mut bodies: Query<&mut Transform, With<Falling>>) {
    let step = time.delta_secs();
    for mut transform in &mut bodies {
        transform.translation.z += step;
    }
}

pub struct FixedRulesPlugin;

impl Plugin for FixedRulesPlugin {
    fn build(&self, app: &mut App) {
        app.add_systems(FixedUpdate, fixed_step);
    }
}

fixed_step owns Falling in this module. The startup example uses its own Falling marker.

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 value stored off the entity
App-wide config or clockResourceCopy the value onto every entity
Stable simulation step`Fi
阅读完整来源 ↗