Lukas Klingsbo

> This sounds like a substantial architectural shift for Flame. I don't think it necessarily has to be, the only difference for the user would be that they optionally can...

Yeah, the documentation definitely needs improvement. If you're using it together with Flame there are quite a lot of examples here: https://examples.flame-engine.org/#/flame_forge2d_Blob_example And a little bit of docs here: https://docs.flame-engine.org/latest/bridge_packages/flame_forge2d/flame_forge2d.html

@colbymaloy if you're using a kinematic body you need to handle the bouncing yourself (standing on it should work out of the box though), see an explanation about kinematic bodies...

@luanpotter what were our concerns here again? I think it would be great to only have `TapCallbacks`.

> @spydon see my design doc for complete breakdown Where is the design doc? Would be good to have that linked here so that we can have a look at...

> @spydon should I reactivate this now that we have agreed on moving forward with this? Did you get a green light from @erickzanardo too? Because I think he was...

> @spydon @erickzanardo are we able to finally move forward with this and kickstart the event system migration as outlined on [my doc](https://docs.google.com/document/d/1nBUup9QCPioVwWL1zs79z1hWF882tAYfNywFMdye2Qc/edit?tab=t.0)? Sure, let's go! I don't think we...

@krispypen are you planning on finishing up this PR? :)

> @spydon @Gustl22 I don't think these failing tests are something to do with this change They don't indeed, we are looking into them. :) Thanks for updating the PR!

Since `PositionComponent`s most of the time aren't rectangular in how they are drawn on the canvas it might be a bit confusing to have this feature connected to the `PositionComponent`,...