Struct rust_action_heroes::system::grab::GrabSystem

pub(crate) struct GrabSystem {
    reader: ReaderId<TransformedInputEvent>,
}

Grab System

The grab system was an interesting challenge.

The mechanic in One Action Heroes is that all entities touching Grabaron get toggled into a "Grab" state. Not only that, but all entities touching those entities get toggled to the "Grab" state, and so on.

I decided to implement it by having a Holding component which tags a component as holdable. These are the player characters, crates, and keys mostly.

The crux of the solution then was to start with Grabaron and iteratively process all entities it, and all entities touching those entities, etc. It's not performant, but it gets the job done.

Fields

reader: ReaderId<TransformedInputEvent>

Implementations

impl GrabSystem

pub(crate) fn new(reader: ReaderId<TransformedInputEvent>) -> Self

Trait Implementations

impl<'s> System<'s> for GrabSystem

type SystemData = (Read<'s, EventChannel<TransformedInputEvent>>, ReadStorage<'s, Position>, WriteStorage<'s, Holding>, ReadStorage<'s, Named>)

The resource bundle required to execute this system.

fn run(&mut self, (channel, positions, holdings, nameds): Self::SystemData)

Executes the system with the required system data.

fn running_time(&self) -> RunningTime

Returns a hint how long the system needs for running. This is used to optimize the way they're executed (might allow more parallelization).

fn accessor(&'b self) -> AccessorCow<'a, 'b, Self>

Return the accessor from the [SystemData].

fn setup(&mut self, world: &mut World)

Sets up the World using Self::SystemData::setup.

fn dispose(self, world: &mut World)

Performs clean up that requires resources from the World. This commonly removes components from world which depend on external resources.

impl<'system_desc_a, 'system_desc_b> SystemDesc<'system_desc_a, 'system_desc_b, GrabSystem> for GrabSystem

fn build(self, world: &mut World) -> GrabSystem

Builds and returns a System.