Add possibility to retrieve info on last collided entities

[CalvinMT]

Saves the first collided entity while a move check.
The saved entity can then be accessed by the moving entity so it can get details on the entity it just collided with.

[CalvinMT]

I chose to change the wording because I couldn't find a way to efficiently reset both entity and otherEntity.
The getLastCollidedEntity has now, in my oppinion, more sense because it allows the user to get the last encounted entity.

[steffen-wilke]

Thank you for the PR!

For your information: Before reviewing this request: I've planned to introduce an event-based solution for this which would provide you with all the information about a collision that occurred. Also: It's possible that a single move collides with multiple entities within a single tick. I'll investigate the possibilities here next week when im on holiday :) Also there's a TODO in our PhysicsEngine about that topic which I recently added.

[CalvinMT]

I've planned to introduce an event-based solution for this which would provide you with all the information about a collision that occurred.

Events could be a good solution. To be honest, I was too lazy to take that road.

It's possible that a single move collides with multiple entities within a single tick.

I think it is possible, in the way I've done it, to take count of all entities colliding within a single tick. The only problem being that all entities which canCollide() will have to be checked for collision.
I'll update this branch with a solution for the above by next week.

Also there's a TODO in our PhysicsEngine about that topic which I recently added.

I saw, but did not understand the last line:
// We need to aggregate the delta X and delta Y for all collision boxes that the entity is colliding with.

[CalvinMT]

Hi @steffen-wilke !
Any news for that PR or same kind of feature?

[steffen-wilke]

@CalvinMT I was playing around with an implementation at the weekend. There is no state to share just yet but I think I'd like to go with the event-based approach because it seems like a cleaner solution. Your recent change from #281 is also a nice addition to this topic. I'll see what I can do this week.

[steffen-wilke]

I've implemented a collision event on the ICollisionEntity with commit d14fa49 which covers the functionality that was discussed in this PR.

@CalvinMT Thanks for providing your solution and triggering the discussion about that topic 👍