Bevy WASM
Mod your Bevy games with WebAssembly!
bevy_wasm |
For games | |
bevy_wasm_sys |
For mods | |
bevy_wasm_shared |
For protocols |
See examples/cubes for a comprehensive example of how to use this.
Protocol
Our protocol crate defines the two message types for communicating between the game and mods.
[]
= "0.10"
= { = "1.0", = ["derive"] }
use *;
use ;
/// The version of the protocol. Automatically set from the `CARGO_PKG_XXX` environment variables.
pub const PROTOCOL_VERSION: Version = version!;
/// A message to be sent Mod -> Game.
/// A message to be sent Game -> Mod.
Game
Our game will import WasmPlugin
from bevy_wasm
, and use it to automatically send and receive messages with the mods.
[]
= "0.10"
= "0.10"
= { = "https://github.com/username/my_game_protocol" }
use *;
use *;
use ;
Mod
Our mod will import FFIPlugin
from bevy_wasm_sys
, and use it to automatically send and receive messages with the game.
[]
= "0.10"
= { = "https://github.com/username/my_game_protocol" }
use *;
use ;
pub unsafe extern "C"
Sharing Resources
Protocol:
Game:
...
.add_resource
.add_plugin
.add_system
...
new
Mod:
...
.add_plugin
.add_startup_system
.add_system
...
new
See examples/shared_resources for a full example.
Roadmap
✅ | wasmtime runtime in games |
✅ | Send messages from mods to game |
✅ | Send messages from game to mods |
✅ | Multi-mod support |
✅ | Time keeping |
✅ | Protocol version checking |
✅ | Extern Resource |
✅ | Startup system mod loading |
✅ | Direct update control |
✅ | Mod unloading |
✅ | Mod discrimination (events aren't broadcast all) |
✅ | Browser support |
⬜ | Extern Query |
⬜ | Synced time |
⬜ | Mod hotloading |
⬜ | Automatic component syncing |
License
Bevy WASM is free, open source and permissively licensed! Except where noted (below and/or in individual files), all code in this repository is dual-licensed under either:
- MIT License (LICENSE-MIT or http://opensource.org/licenses/MIT)
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
at your option. This means you can select the license you prefer! This dual-licensing approach is the de-facto standard in the Rust ecosystem and there are very good reasons to include both.
Your contributions
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.