rust-game-ports VS bones

Regarding 2D development, you may want to have a look at the Rust Game Ports project, in order to have a hands-on understanding of how development with the Rust game engine actually is.

rust-game-ports is now officially supported by the Rust GameDev WG. By having this repo on neutral ground, we want to invite the Rust gamedev community to contribute additional game examples to this bundle, so we may collectively expand our comparison-matrix of similar/same games made in different engines. A bit like the realworld app taken one step further.

1 final announcement is I am taking the 2019 tutorial from u/thebracket and porting it to bevy (Bevy GitHub). I really enjoy working in bevy so this is a fun side project. I have been in the talks with 64kramsystem and adding the port to the Rust Game Dev game ports repo as an example to follow. I might make a book out of it, I have not decided yet. Fun stuff in the works!

In order to do that, I needed a solid way to bridge the gap between Bracket-lib and Bevy. 64kramsystems has done an amazing job of porting Hands-on Rust to Bevy - it's really great! It still uses bracket-lib for the rendering, but shows you how you can use Bevy as just the ECS. I decided to go a step further, and get bracket-lib running as a first-class Bevy citizen. Thus, bracket-bevy was born.

We support modding through our Bones framework, built on top of Bevy: https://fishfolk.org/development/bones/introduction/

It’s also worth mentioning our use case is a bit special because of our meta engine bones which is what sits on top of bevy and the core of Jumpy. While there arnt many things to upgrade in bones, that will be the first library to be updated and then we will move to jumpy. Most of the plug-ins we interface with upgrade pretty rapidly so we don’t usually have to wait long to make the migration jump.