ServerEvents can be missed on clients using FixedUpdate about bevy_replicon

[RJ]

Could just document the workaround until bevy solves it for us 🤷‍♂️

[RJ]

Here's my workaround at the moment:

fn clear_events<T: Event>(mut events: ResMut<Events<T>>) {
    events.clear();
}

fn replicon_event_setup(app: &mut App) {
    // before replicon creates these with normal `add_event`, create them manually
    // so they will not be cleared before FixedUpdate can run
    // see: https://github.com/lifescapegame/bevy_replicon/pull/85
    #[cfg(feature = "is_client")]
    {
        app.init_resource::<Events<InitClientMessage>>();
        app.init_resource::<Events<PlayerInputsMessage>>();
        app.init_resource::<Events<TimingReportMessage>>();
        app.init_resource::<Events<EventMessages>>();
        // clear them at the end of fixedupdate:
        app.add_systems(
            FixedUpdate,
            (
                clear_events::<InitClientMessage>,
                clear_events::<PlayerInputsMessage>,
                clear_events::<TimingReportMessage>,
                clear_events::<EventMessages>,
            )
                .in_set(SpacepitSet::Last),
        );
    }
    // SERVER -> CLIENT EVENTS
    app.add_server_event::<InitClientMessage>(SendPolicy::Ordered);
    app.add_server_event::<PlayerInputsMessage>(SendPolicy::Unreliable);
    app.add_server_event::<TimingReportMessage>(SendPolicy::Unreliable);
    app.add_server_event::<EventMessages>(SendPolicy::Unreliable);
    // ...
}

[UkoeHB]

For reference, this is fixed in this bevy PR.

[Shatur]

Fixed in Bevy 0.12.1, closing.