| Crates.io | bevy_crossbeam_event |
| lib.rs | bevy_crossbeam_event |
| version | 0.10.0 |
| created_at | 2023-03-10 09:51:48.724736+00 |
| updated_at | 2026-01-17 09:02:49.678076+00 |
| description | Fire Bevy events from crossbeam channels |
| homepage | |
| repository | https://github.com/johanhelsing/bevy_crossbeam_event |
| max_upload_size | |
| id | 806318 |
| size | 53,763 |
Fire Bevy events from crossbeam channels.
Useful if you need to handle callbacks in 3rd party libraries etc. like
steamworks-rs, or getting events out of tracing layers.
Add add events to your app using .add_crossbeam_event::<EventType>:
#[derive(Event, Clone, Debug)]
struct LobbyJoined(Lobby);
impl Plugin for MyPlugin {
fn build(&self, app: &mut App) {
app.add_crossbeam_event::<LobbyJoined>();
app.add_startup_system(setup);
app.add_observer(handle_lobby_joined);
}
}
Fire events by using Res<CrossbeamEventSender<EventType>> (which can be
cloned and sent into callbacks):
fn setup(service: Res<ThirdPartyCode>, sender: Res<CrossbeamEventSender<LobbyJoined>>) {
let sender = sender.clone();
service.join_lobby(id, move |lobby| {
sender.send(LobbyJoined(lobby));
});
}
Handle the events with observers:
fn handle_lobby_joined(lobby_joined: On<LobbyJoined>) {
info!("lobby joined: {:?}", lobby_joined.0);
}
The main branch targets the latest bevy release.
| bevy | bevy_crossbeam_event |
|---|---|
| 0.18 | 0.10, main |
| 0.17 | 0.9 |
| 0.16 | 0.8 |
| 0.15 | 0.7 |
| 0.14 | 0.6 |
| 0.13 | 0.5 |
| 0.12 | 0.3 |
| 0.11 | 0.2 |
| 0.10 | 0.1 |
In Bevy 0.17, events changed functionality and became what was previously known as "triggers", if you prefer the old behavior with asyncronous messages, check out bevy_channel_message.
bevy_crossbeam_event is dual-licensed under either
at your option.
PRs welcome!