WalkToObjective — Easy Chapter Generator

Purpose and fit

WalkToObjective detects an accepted collider entering the destination trigger. Use it for physical player arrival. Do not use it to confirm that an agent finished a route, measure distance without physics, or require NavMesh: route preview is independent from completion.

Requirements and minimum setup

1
Create the component from the row through Create Scene Component > Walk To, or add it to a GameObject under the Chapter.
2
Under Objective Link, choose the Ordered Objective and confirm Linked.
3
Add a Collider to the same GameObject and enable Is Trigger. Add Sphere Collider and Enable Is Trigger repair those requirements with Undo support.
4
Assign Player, at least one Accepted Player Layer, or a defined Player Tag. A match by reference, layer, or tag is sufficient.

Inspector fields

Field	Effect	Note
Invoke Arrival Only	Invokes On Player Arrived once without completion.	On Completed does not run from arrival in this mode.
Accepted Player Layers	Accepts colliders in the mask.	Can be used without a tag.
Player Tag	Accepts a GameObject with the defined tag.	An undefined tag produces a safe warning.
On Player Arrived	Runs on the first valid arrival in each cycle.	Also runs in Arrival Only mode.
Collider Enable Delay	Keeps the assigned collider disabled for the delay.	Requires Delayed Collider when positive.
Show Path	Draws a NavMesh-calculated route.	Never participates in arrival detection.
Refresh Path Continuously	Updates according to Path Refresh Interval.	Disable for static destinations.
Player / Path Probe / Path Renderer	Define route origin, calculation agent, and visible line.	Required only for preview.
Path Height Offset	Raises rendered path points.	Prevents z-fighting with the floor.

Runtime behavior and event order

Entry

OnTriggerEnter forwards a collider to HandleArrival.

Filter

Reference, layer, or tag must match, and arrival must not have fired.

Arrival

On Player Arrived runs once.

Request

When Arrival Only is off, TryComplete() requests advancement.

Acceptance

On Completed runs only when the Chapter accepts.

With and without NavMesh

Arrival always uses physics and works without NavMesh. The Path Preview is diagnostic: with Show Path enabled, the component uses NavMesh.CalculatePath and a LineRenderer. If no baked data exists, the Inspector warns that preview is unavailable; the Objective remains active and can still complete through the trigger.

Static destination

Disable Refresh Path Continuously and call RefreshPathPreview() only after the origin or destination changes.

Reset and Validation

ResetObjective() clears inherited completion, permits arrival to fire again, cancels pending delayed activation, and restores the delayed collider to its initial state. Validation identifies a broken link, missing trigger, impossible player filter, positive delay with no collider, or preview with no renderer.

Troubleshooting

The player is not detected

Confirm that both objects are active, at least one Rigidbody participates in the physics interaction, the destination collider is a trigger, and reference, layer, or tag matches.

Arrival fires but does not complete

Clear Invoke Arrival Only and confirm that the linked record is the active Objective.

No route is visible

Check Show Path, Player, Path Probe, Path Renderer, and baked NavMesh data. Missing preview never blocks completion.

Arrival appears twice

The component suppresses repeats per cycle. Search for a second WalkToObjective with the same ID or an additional external call.