|How do you use documentation throughout your workflow? Share your experience with us by taking this survey.|
The Platform Effector 2D applies various “platform” behaviour such as one-way collisionsA collision occurs when the physics engine detects that the colliders of two GameObjects make contact or overlap, when at least one has a Rigidbody component and is in motion. More info
See in Glossary, removal of side-friction/bounce etc.
Colliders that you use with the effector would typically not be set as triggers so that other collidersAn invisible shape that is used to handle physical collisions for an object. A collider doesn’t need to be exactly the same shape as the object’s mesh - a rough approximation is often more efficient and indistinguishable in gameplay. More info
See in Glossary can collide with it.
|Use Collider Mask||Should the ‘Collider Mask’ property be used? If not then the global collision matrix will be used as is the default for all colliders.|
|Collider Mask||The mask used to select specific layers allowed to interact with the effector.|
|Use One Way||Should one-way collision behaviour be used?|
|Use One Way Grouping||Ensures that all contacts disabled by the one-way behaviour act on all colliders. This is useful when multiple colliders are used on the object passing through the platform and they all need to act together as a group.|
|Surface Arc||The angle of an arc centered on the local ‘up’ the defines the surface which doesn’t allow colliders to pass. Anything outside of this arc is considered for one-way collision.|
|Use Side Friction||Should friction should be used on the platform sides?|
|Use Side Bounce||Should bounce should be used on the platform sides?|
|Side Arc||The angle of an arc that defines the sides of the platform centered on the local ‘left’ and ‘right’ of the effector. Any collision normals within this arc are considered for the ‘side’ behaviours.|