From 7db5dc03f1a1e7874122522f66bf2de74de5c14b Mon Sep 17 00:00:00 2001 From: SpecificProtagonist Date: Mon, 8 Jul 2024 03:19:05 +0200 Subject: [PATCH] Fix state example urls (#14209) Doc was still pointing to old location of state examples Co-authored-by: Alice Cecile --- crates/bevy_state/src/lib.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/crates/bevy_state/src/lib.rs b/crates/bevy_state/src/lib.rs index a64a34a04e..363a97e64e 100644 --- a/crates/bevy_state/src/lib.rs +++ b/crates/bevy_state/src/lib.rs @@ -4,15 +4,15 @@ //! //! - Standard [`States`](state::States) can only be changed by manually setting the [`NextState`](state::NextState) resource. //! These states are the baseline on which the other state types are built, and can be used on -//! their own for many simple patterns. See the [state example](https://github.com/bevyengine/bevy/blob/latest/examples/ecs/state.rs) +//! their own for many simple patterns. See the [state example](https://github.com/bevyengine/bevy/blob/latest/examples/state/state.rs) //! for a simple use case. //! - [`SubStates`](state::SubStates) are children of other states - they can be changed manually using [`NextState`](state::NextState), -//! but are removed from the [`World`](bevy_ecs::prelude::World) if the source states aren't in the right state. See the [sub_states example](https://github.com/bevyengine/bevy/blob/latest/examples/ecs/sub_states.rs) +//! but are removed from the [`World`](bevy_ecs::prelude::World) if the source states aren't in the right state. See the [sub_states example](https://github.com/bevyengine/bevy/blob/latest/examples/state/sub_states.rs) //! for a simple use case based on the derive macro, or read the trait docs for more complex scenarios. //! - [`ComputedStates`](state::ComputedStates) are fully derived from other states - they provide a [`compute`](state::ComputedStates::compute) method //! that takes in the source states and returns their derived value. They are particularly useful for situations //! where a simplified view of the source states is necessary - such as having an `InAMenu` computed state, derived -//! from a source state that defines multiple distinct menus. See the [computed state example](https://github.com/bevyengine/bevy/blob/latest/examples/ecs/computed_states.rs) +//! from a source state that defines multiple distinct menus. See the [computed state example](https://github.com/bevyengine/bevy/blob/latest/examples/state/computed_states.rs) //! to see usage samples for these states. //! //! Most of the utilities around state involve running systems during transitions between states, or