collision-relationships

To set up collision relationships in FlatRedBall2, use AddCollisionRelationship to wire two entity groups together for per-frame overlap testing, then apply modifiers like MoveFirstOnCollision or BounceOnCollision to configure the physical response.

FlatRedBall2 collision relationships support tile-based geometry and one-way platforms, allowing you to define complex level geometry interactions like slope handling and tricky platformer movements directly within your Screen configuration.

You can trigger gameplay events during entity collisions in FlatRedBall2 by subscribing to collision lifecycle hooks such as CollisionStarted, CollisionOccurred, and CollisionEnded to execute damage, sounds, or state changes.

The best way to configure collision responses in FlatRedBall2 is by chaining fluent modifiers like BounceOnCollision, MoveFirstOnCollision, or MoveBothOnCollision onto your relationship definition to dictate how entities separate upon overlap.

FlatRedBall2 collision relationships operate across desktop and browser backends, providing per-frame collision testing and integration with both default and non-default collision shapes for 2D games.

Collision events in FlatRedBall2 require an explicit AddCollisionRelationship call between the specific entity factories in your Screen; without wiring this per-frame test, overlaps will not trigger CollisionStarted or CollisionEnded.