bevy_gauge 0.2.0

A crate designed to provide an opinionated solution to handling stats, effects, abilities and tags
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88

use bevy::{app::MainScheduleOrder, prelude::*};
use bevy_ecs::schedule::ScheduleLabel;

/// Order goes StatsUpdate -> CompositeStatsUpdate -> SideEffectsUpdate
/// All of this happens in PreUpdate so that by Update stats are ready to be
/// used.
/// 
/// If a system manipulates Stats, it should be inside of StatsUpdate.
/// 
/// We could support "..WriteBack" style stuff with proper scheduling
/// Say we processed writeback components and their changes in one step
/// and then processed Stat changes in another. 
/// 
/// StatComponentUpdate - Life.current updated
/// > WriteBackWrite - Life.current written to "Life.current"
/// StatsUpdate - "Life.current" updated
/// > StatsUpdateWrite - "Life.current" written to Life.current
/// StatsReady - Canonical value for "Life.current" and Life.current available
///     for use elsewhere
/// 
/// All of this allows you to treat "Life.current" and Life.current as the
/// same value. This is handy because we might want to handle some effects 
/// via the components value like dealing damage via a hit. We might also 
/// want to be able to access "Life.current" via a 1-shot stat effect.
/// 
/// Gotta think on it.
pub fn plugin(app: &mut App) {
    
    app.init_schedule(AddStatComponent)
        .world_mut()
        .resource_mut::<MainScheduleOrder>()
        .insert_after(PreUpdate, AddStatComponent);
    
    app.init_schedule(StatComponentUpdate)
        .world_mut()
        .resource_mut::<MainScheduleOrder>()
        .insert_after(AddStatComponent, StatComponentUpdate);

    app.init_schedule(StatComponentWrite)
        .world_mut()
        .resource_mut::<MainScheduleOrder>()
        .insert_after(StatComponentUpdate, StatComponentWrite);

    app.init_schedule(StatsUpdate)
        .world_mut()
        .resource_mut::<MainScheduleOrder>()
        .insert_after(StatComponentWrite, StatsUpdate);

    app.init_schedule(StatsWrite)
        .world_mut()
        .resource_mut::<MainScheduleOrder>()
        .insert_after(StatsUpdate, StatsWrite);

    app.init_schedule(StatsReady)
        .world_mut()
        .resource_mut::<MainScheduleOrder>()
        .insert_after(StatsWrite, StatsReady);
}

#[derive(ScheduleLabel, Debug, Clone, PartialEq, Eq, Hash)]
pub struct AddStatComponent;

#[derive(ScheduleLabel, Debug, Clone, PartialEq, Eq, Hash)]
pub struct StatComponentUpdate;

#[derive(ScheduleLabel, Debug, Clone, PartialEq, Eq, Hash)]
pub(crate) struct StatComponentWrite;

#[derive(ScheduleLabel, Debug, Clone, PartialEq, Eq, Hash)]
pub struct StatsUpdate;

#[derive(ScheduleLabel, Debug, Clone, PartialEq, Eq, Hash)]
pub(crate) struct StatsWrite;

#[derive(ScheduleLabel, Debug, Clone, PartialEq, Eq, Hash)]
pub struct StatsReady;

// pub fn debug_dump(app: &mut App) {

//     let add_stat_component = bevy_mod_debugdump::schedule_graph_dot(app, AddStatComponent, &bevy_mod_debugdump::schedule_graph::Settings::default());
//     let stat_component_update = bevy_mod_debugdump::schedule_graph_dot(app, StatComponentUpdate, &bevy_mod_debugdump::schedule_graph::Settings::default());
//     let stat_component_write = bevy_mod_debugdump::schedule_graph_dot(app, StatComponentWrite, &bevy_mod_debugdump::schedule_graph::Settings::default());
//     let stats_update = bevy_mod_debugdump::schedule_graph_dot(app, StatsUpdate, &bevy_mod_debugdump::schedule_graph::Settings::default());
//     let stats_write = bevy_mod_debugdump::schedule_graph_dot(app, StatsWrite, &bevy_mod_debugdump::schedule_graph::Settings::default());
//     let stats_ready = bevy_mod_debugdump::schedule_graph_dot(app, StatsReady, &bevy_mod_debugdump::schedule_graph::Settings::default());

//     std::fs::write("stats.dot", stats_ready).expect("Failed to write schedule graph"); // stat_component_update + "\n" + &stat_component_write + "\n" + &stats_update + "\n" + &stats_write + "\n" + &
// }