bevy_editor_pls VS bevy_ecs_tilemap

I think one part that makes this extra obvious is bevy UI and the attempts at an editor. I remember when https://github.com/jakobhellermann/bevy_editor_pls came along and I was very excited, but since then nothing has really happened on the editor front. Not that I need an editor personally, but what I find disappointing and telling is that this whole thing has been basically halted because of bevy's idea of having UI in the ECS.

Also, there is this Bevy plugin https://github.com/jakobhellermann/bevy_editor_pls/

It's on of the primary initiatives right now. Games are not developed by only programmers, we're well aware of that. There are a few ongoing existing ecossytem level efforts like bevy_editor_pls. For an official editor, we're just lacking the UI tooling to fully flesh it out right now. Like Godot, Bevy's dogfooding it's own UI solution for the official editor, but it's not quite there yet. Bevy isn't alone in this. There's a smorgasbord of ongoing work in the Rust for UI space, and there's quite a bit of greenfield efforts to develop a data-oriented or ECS style approach to UI layouting and management. Once we have this a bit more hammered down, it's just a matter of time before an official editor becomes available.

It is something we've been building toward for awhile. We've been focused on core systems like the renderer and ecs for awhile now, but we're finally at the point where we can start moving up the stack.

We will be focusing on scenes, asset workflows, ui, and the editor from here on out (with scenes, asset workflows, and UI being the focus for the next release).

I'd like to have some sort of editor MVP by the end of the year.

Until then, there are community efforts like: https://github.com/jakobhellermann/bevy_editor_pls

P.S. There is an effort to make an editor for Bevy if you're interested, though it's not complete.

For now though, bevy_editor_pls is a surprisingly useful third-party prototype.

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,