First spawning after the startup set

[EmiOnGit]

I think it is common to spawn some entities in startup systems and then assume that they get spawned before other systems are spawned.

Following example:

use bevy::prelude::*;
use spew::prelude::*;
#[derive(Debug, PartialEq, Eq)]
enum Objects {
    Player,
}
fn main() {
    App::new()
        .add_plugin(SpewPlugin::<Objects, ()>::default())
        .add_spawner((Objects::Player, spawn_player))
        .add_system(player_state)
        .add_startup_system(setup)
        .run();
}
#[derive(Component)]
struct PlayerMarker;
fn spawn_player(world: &mut World, _input: ()) {
      world.spawn(PlayerMarker);

}
fn setup(mut spawn_events: EventWriter<SpawnEvent<Objects, ()>>) {
      spawn_events.send(SpawnEvent {
            object: Objects::Player,
            data: (),
      });
}
fn player_state(player: Query<&PlayerLabel>) {
     let _player_label = player.single();
}

This would crash since the event would only be processed after the first frame
since the event will first be processed in the first frame and entity spawns are only processed in the last stage (I think) .

It would be nice to have some kind of new CoreSet which checks if any startup system send spawn events and already spawns them accordingly before the normal systems begin to run

[janhohenheim]

Hmm, I agree. I have no idea how I would implement that though :/

[janhohenheim]

Thanks for your feedback btw, I very much appreciate it :)

[janhohenheim]

Update: Figured it out, your example works now: https://github.com/janhohenheim/spew/blob/main/examples/query_after_spawn.rs 😄

[EmiOnGit]

Wow, you completely smashed the issues I opened! :D