| Name | Description |
|---|---|
| itch.io | Free & paid assets |
| OpenGameArt.org | Free assets |
| Kenney | CC0 assets |
| /r/gameassets | Free assets |
| Name | Type | Description | License |
| [unstable] | |
| codegen-backend = true | |
| [profile.dev] | |
| # Compile using cranelift for massively faster compilation | |
| codegen-backend = "cranelift" | |
| # If you want to attach a debugger, set `debug = true` instead | |
| debug = "line-tables-only" | |
| # Assuming we don't do `catch_unwind`, we can safely abort on panics for some extra perf | |
| panic = "abort" |
| 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.
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.
| type: | |
| 0 - no relationship | |
| 1 - friend | |
| 2 - blocked | |
| 3 - incoming friend request | |
| 4 - outgoing friend request | |
| accepting FR triggers RELATIONSHIP_ADD 1 | |
| remove friend triggers RELATIONSHIP_REMOVE 1 | |
| block triggers RELATIONSHIP_ADD 2 |