bevy_dogoap - 将 dogoap 集成到 Bevy 的 ECS 模型中

完整的 Bevy + bevy_dogoap 示例

use bevy::prelude::*;
use bevy_dogoap::prelude::*;

// Define a DatumComponent as a struct with one member that can be either bool, f64 or u64
#[derive(Component, Clone, DatumComponent)]
struct IsHungry(bool);

// Define a ActionComponent as a struct without any fields
#[derive(Component, Reflect, Clone, Default, ActionComponent)]
struct EatAction;

fn startup(mut commands: Commands) {
    // Set our goal to be that we shouldn't be hungry
    let goal = Goal::from_reqs(&[IsHungry::is(false)]);

    // Create our action from EatAction
    let eat_action = EatAction::new()
        // Mutators define what happens when this action is executed
        // In this case, we set IsHungry to false
        .add_mutator(IsHungry::set(false));

    // Create our planner + required DatumComponents
    let (planner, components) = create_planner!({
        actions: [(EatAction, eat_action)],
        // We put our starting state to be IsHungry = true
        state: [IsHungry(true)],
        goals: [goal],
    });

    // Spawn a entity with our Planner component + the DatumComponents
    commands.spawn((Name::new("Planner"), planner, components));
}

// Create our system that handles executing of the EatAction
fn handle_eat_action(
    mut commands: Commands,
    mut query: Query<(Entity, &EatAction, &mut IsHungry)>,
) {
    for (entity, _eat_action, mut need) in query.iter_mut() {
        // We set IsHungry to false
        need.0 = false;
        // And remove the action from our entity as we're done with this action
        commands.entity(entity).remove::<EatAction>();
    }
}

fn main() {
    let mut app = App::new();

    // We need to register our components as DatumComponent, otherwise planner won't be able to find them
    // as we're using bevy_trait_query to be able to query for components implementing a trait
    register_components!(app, vec![IsHungry]);

    app.add_plugins(MinimalPlugins)
        // !!! Don't forget to add the plugin ;)
       .add_plugins(DogoapPlugin)
       .add_systems(Startup, startup)
       .add_systems(FixedUpdate, handle_eat_action);

    // Run a couple of updates to run forward the world
    for _i in 0..3 {
        app.update();
    }

    // Lets inspect the final state of our (one) Planner we have in the World
    let mut query = app.world_mut().query::<&Planner>();
    let planner = query.get_single(&app.world()).unwrap();

    // This should confirm that is_hungry and is_tired have been set to `false`
    println!("Final state in our planner:");
    println!("{:#?}", planner.state);
}

使用此示例，在计划者提出计划、添加 EatAction 组件、我们的系统处理动作并更改 DatumComponent 后，IsHungry 应该需要大约 2-3 帧，才能设置为 false

更多示例

• bevy_basic.rs - 快速入门 - 为 dogoap 和 Bevy 之间的集成提供基本设置
• miner.rs - 长计划 - 如何设置更复杂的交互
• sneaky.rs - 玩家交互 - 如何在具有玩家控制实体的世界中使用 dogoap
• villages.rs - 嵌套计划者 - 如何嵌套计划者以实现更智能的功能
• lemonade_stand.rs - 协作计划者 - 展示如何拥有两个具有两个非常不同的计划者的实体并“模拟”协作

支持的 Bevy 版本