bevy-cheatbook VS bevy_ecs_ldtk

I've been using Bevy recently so here are some thoughts on this:

Firstly, the overall quality is high and seeing this attention being paid to the project's organization is another good sign.

Documentation is not great great. The Bevy book runs out of content very quickly. The "Cheat Book" has additional useful information: https://bevy-cheatbook.github.io/. With these plus the examples I've been able to figure out everything I need, but it's slow going.

I'm not 100% sold on ECS. It loses a lot of type safety and there doesn't seem to be any way to ensure cleanup of entities and their components.

This is quite helpful to cover the features of bevy with some code examples and explanations with links to git repositories as reference. Most of it appears to be from 0.9, but you can reference to the migration guide to see how to change from it. Ctrl-f is your friend to see which version changes what.

You can see working examples of nearly everything you asked about in the Bevy Cheatbook

The biggest source of wasted time for me was finding out that my shaders which were working on native didn’t work on webgl. For one of the more perplexing error messages, I opened this issue in the cheatbook a while ago.

wasm mostly works :) There's a nice PR open on the cheatbook that documents the process quite well that you can work off of.

Great! Are you okay if I submit this to the Unofficial Bevy Cheatbook? This question comes up pretty frequently and this is a great little snippet.

Collision detection - no auto-generated, you build your own manually. The LDtk integration has lots of examples here. Note that for 2D, if you only want rectangles bordering sprites, you can set the collider bounds equal to your sprite bounds, which gets you 99% of the way there

I've really enjoyed using ldtk for this kind of thing using this plugin https://github.com/Trouv/bevy_ecs_ldtk. The bevy setup for entities and collisions is a little verbose but there are solid examples in the repo that I was able to get working in my project very quickly by building from that code. It's pretty activity maintained and they've been responsive to bugs I file too.

However, I'm struggling with adding collider boxes to entities. In ecs_ldtk example (https://github.com/Trouv/bevy_ecs_ldtk/tree/main/examples/platformer) they spawn colliders automatically attached to entities. However, I would prefer to have them be slightly shifted (let's say, only 1-tile-sized collider attached to the player's legs or no collider on a tree crown), which means I need to spawn a child anchor to the entity and attach a collider to it. I guess one possible solution would be to have a system that does this for me on entity spawn, but maybe there's another solution I'm unaware of, and more experienced developers could help me here. Thanks in advance! :)