trigger areas

[nearnshaw]

No description provided.

[cloudflare-workers-and-pages]

Deploying adr with    Cloudflare Pages

Latest commit:	e448293
Status:	🚫  Build failed.

View logs

[robtfm]

perhaps rather than requiring the trigger area to have a MeshCollider alongside it, we could add mesh and collision_mask fields to this new component (and maybe rename it to MeshTrigger).

then we can specify the default collision layers differently.

we could also update the gltf reader to specify that _trigger name means it's a MeshTrigger, in parallel to current the _collider -> MeshCollider?

that would avoid all changes on existing components / behaviours and would give us good default behaviour for the new component.

[robtfm]

• we should ensure that triggers are triggered even if the object "passes through" the target in a frame. this would require special handling for tweens. or explicitly say that this doesn't trigger (which would be a shame)
• we should report the position of the trigger as well (at first point of contact) for the case when the entity with the trigger has a tween
• if an entity has collision=physics and trigger=player set to the same mesh, should we fire the trigger when player touches? from the example it appears so, this should probably be explicitly mentioned either way

[robtfm]

i suggested using a transform directly here, but i'm not sure we can actually do that since we don't have a PbTransform message type...

[nearnshaw]

The same would apply to the fields triggeredEntityPosition and triggeredEntityRotation that I just added
If we change the 3 above fields for a Transform, then we should do the same with the triggered entity

[kuruk-mm]

Great job 🙌