| Name | Description |
|---|---|
| itch.io | Free & paid assets |
| OpenGameArt.org | Free assets |
| Kenney | CC0 assets |
| /r/gameassets | Free assets |
| Name | Type | Description | License |
The Bevy Remote Protocol (BRP) is a transport-agnostic and serialization-agnostic protocol for communication between a Bevy application (acting as a server) and a remote (or local) client. It's a request/response-style protocol (similar to HTTP), meaning that every communication is always initiated by the client, and the server only responds to the client's requests.
- A editor/inspector, allowing the user to inspect and modify the Bevy application's state in real time, both locally and remotely;
- “Gameshark“-style cheats, allowing the user to modify a game's state in real time;
- JS/HTML-based UI interacting with an embedded Bevy application running in a browser;
- Non-Bevy/Rust applications (e.g. a C++/Python/Java application) interacting with embedded Bevy modules;
This is a list of "prerequisite" tasks needed to bringing the Bevy UI to a level of quality suitable for production games and tools. It is not a UI framework, but rather a set of features which a UI framework can build on.
Caveat: this started out as an attempt to objectively assess each issue, but I found I couldn't resist putting in my own opinions about things.