Easy Chapter Generator
EnglishEspañol

A destination occupancy helper

PlacementTrigger reports whether one expected object occupies one destination owned by an ObjectPlacementObjective. It is a supporting component, not an Objective: it has no Objective Link, cannot advance a Chapter, and should not be treated as another ordered position.

The owning ObjectPlacementObjective usually finds or creates it at Start and calls Configure(owner, object, fallbackName). Add it manually only when the destination needs a preconfigured helper or an external placement system will control its state.

State, ownership, and matching

FieldMeaningNotes
Is TriggeredRead-only occupancy flagReset by the owning Objective
Managed ExternallyIgnores automatic physics callbacksExternal code must call SetTriggered
OwnerThe ObjectPlacementObjective that reads this helperAssigned by Configure
Accepted ObjectExact root; child colliders matchPreferred over name fallback
Accepted Object NameExact collider object nameUsed only without a reference

Automatic or externally managed occupancy

In automatic mode, enter and stay set the flag true and exit sets it false, but only while an owner exists, the owner is incomplete, and the collider matches. In external mode, physics messages are ignored. Call SetTriggered(true) only after the external system has accepted the placement, and false when it becomes invalid.

Configure always clears existing occupancy. If several placement objectives share a destination, each requires an available helper with the corresponding owner; a single occupancy flag cannot represent several expected objects safely.

Troubleshooting and reset

Flag never becomes true

Confirm an owner was assigned, the destination collider is a trigger, physics messages are available, and Managed Externally is not enabled accidentally.

Wrong object is accepted

Assign an exact Accepted Object. Name fallback compares only the collider GameObject name.

Flag remains true after reset

The owning Objective calls SetTriggered(false). If another external integration immediately writes true, coordinate reset order in that integration.

See ObjectPlacementObjective for the complete multi-destination lifecycle.