rfcs VS bevy_ecs_tilemap

For some good real-world use cases, check out this thread: https://github.com/bevyengine/rfcs/pull/39

I'm the author of the draft Many Worlds RFC. Current plan is to get scheduling sorted out, then pick that work up again.

Yep, we do this, it works great! We stole it from hecs and Amethyst before us. There's a nice write-up of the theory in the scheduler rework the team has been working on for the past few months.

I can tell you right now that there’s an entire channel in the Bevy discord server dedicated to making an out of the box api for multiplayer. If you want the current state of it, check out this RFC. https://github.com/bevyengine/rfcs/pull/19 I’m really excited for it when it eventually comes out.

I think making it easier for systems to observe the effects of Commands from other systems is a critical missing piece of the Bevy ECS puzzle. "Stageless" is a solid, holistic solution to the problem and we're seeing the community slowly establish consensus on that design. There is already a draft implementation in the works. And I think "stageless" is most likely the solution we will land on.

Cool! Looks like a nice complement to the RFC about keyboard navigation!

This should be fairly feasible: although you'll probably want to wait on (or implement) the dynamic components RFC. The comments above are more to the effect of "writing Rust is easier and more convenient than you might expect".

You will be happy to know that better/updated documentation is planned. It was briefly mentioned as "the new Bevy Book effort" in this paragraph of the blog post and there are a ton more details in this RFC. Your participation would be more than welcome!

So, several of us have been working on a relations feature for Bevy: first-class support for those sort of "target another entity with a component" patterns that keep cropping up. There's a lot to be done, and it's at a point where it can be chunked out, so if you're interested in helping out come say hi on Discord :)

https://github.com/StarArawn/bevy_ecs_tilemap Consider thumbing through this code for ideas. Generally looks fine assuming you need to individually color tiles at some point in the future.

Yeah built in texture atlas requires that you manually manage the atlas and doesn't support swapping out textures on the fly (although I'm willing to consider adding support for that). I'm pretty sure the bevy_ecs_tilemap plugin uses the "texture array" approach to texture atlases. Its very possible that it will work for your usecase (or provide an example of how to do that in bevy).

I can only speak to Bevy from firsthand use and you won't find support for any of your bullets out of the box, but some of it is available in the surrounding package ecosystem. I liked working with bevy_ecs_tilemap. I highly recommend the Cheatbook as well.

you can check out https://github.com/StarArawn/bevy_ecs_tilemap,