Pathfinding basics in Unity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a variable for the target position.

Unity

public Vector3 [1];

Drag options to blanks, or click blank then click option'

AtargetPosition

BstartPosition

Cagent

Dspeed

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names unrelated to position like 'speed' or 'agent'.

The variable targetPosition is used to store the destination point for pathfinding.

2fill in blank

medium

Complete the code to get the NavMeshAgent component attached to the GameObject.

Unity

agent = GetComponent<[1]>();

Drag options to blanks, or click blank then click option'

ATransform

BNavMeshAgent

CCollider

DRigidbody

Attempts:

3 left

💡 Hint

Common Mistakes

Using Rigidbody or Collider which are unrelated to pathfinding.

The NavMeshAgent component controls the pathfinding and movement on the NavMesh.

3fill in blank

hard

Fix the error in setting the destination for the NavMeshAgent.

Unity

agent.[1](targetPosition);

Drag options to blanks, or click blank then click option'

ASetDestination

BGoTo

CMove

DNavigate

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like Move or GoTo.

The correct method to set the destination of a NavMeshAgent is SetDestination.

4fill in blank

hard

Fill both blanks to check if the agent has reached its destination.

Unity

if (agent.[1] <= agent.[2]) {
    Debug.Log("Destination reached");
}

Drag options to blanks, or click blank then click option'

AremainingDistance

BstoppingDistance

Cspeed

Dradius

Attempts:

3 left

💡 Hint

Common Mistakes

Using speed or radius instead of distance properties.

The remainingDistance property tells how far the agent is from the destination, and stoppingDistance is the distance at which the agent stops moving.

5fill in blank

hard

Fill all three blanks to create a dictionary mapping waypoint names to their positions, filtering only waypoints within 10 units.

Unity

var waypoints = new Dictionary<string, Vector3>() {
    {"Start", [1],
    {"Middle", [2],
    {"End", [3]
};

Drag options to blanks, or click blank then click option'

Anew Vector3(0, 0, 0)

Bnew Vector3(5, 0, 5)

Cnew Vector3(10, 0, 10)

Dnew Vector3(15, 0, 15)

Attempts:

3 left

💡 Hint

Common Mistakes

Including points too far away like (15,0,15).

The waypoints are positions represented by Vector3. Only points within 10 units are included, so positions at (0,0,0), (5,0,5), and (10,0,10) are correct.

Practice

1. What is the main purpose of pathfinding in Unity games?

easy

A. To help game objects move from one point to another avoiding obstacles

B. To create visual effects like explosions

C. To manage game audio settings

D. To design user interface layouts

Solution

1. Step 1: Understand pathfinding concept

   Pathfinding is used to find a route for characters or objects to move smartly in a game world.

2. Step 2: Identify Unity's use of pathfinding

   Unity uses pathfinding to move game objects from one point to another while avoiding obstacles.

3. Final Answer:

   To help game objects move from one point to another avoiding obstacles -> Option A

4. Quick Check:

   Pathfinding = smart movement [OK]

Hint: Pathfinding = smart movement avoiding obstacles [OK]

Common Mistakes:

• Confusing pathfinding with graphics or audio
• Thinking pathfinding manages UI
• Assuming pathfinding creates effects

2. Which of the following is the correct way to set a destination for a NavMeshAgent in Unity?

easy

A. agent.Navigate(target.position);

B. agent.MoveTo(target.position);

C. agent.GoTo(target.position);

D. agent.SetDestination(target.position);

Solution

1. Step 1: Recall NavMeshAgent method for setting destination

   The correct method to set a destination is SetDestination(Vector3 target).

2. Step 2: Match method names with options

   Only agent.SetDestination(target.position); uses SetDestination correctly; others are invalid method names.

3. Final Answer:

   agent.SetDestination(target.position); -> Option D

4. Quick Check:

   SetDestination sets target [OK]

Hint: Remember NavMeshAgent uses SetDestination() method [OK]

Common Mistakes:

• Using non-existent methods like MoveTo or GoTo
• Forgetting to pass target.position as Vector3
• Confusing method names with other APIs

3. What will be the output of this Unity C# code snippet?

using UnityEngine;
using UnityEngine.AI;

public class MoveAgent : MonoBehaviour {
    public Transform target;
    private NavMeshAgent agent;

    void Start() {
        agent = GetComponent<NavMeshAgent>();
        agent.SetDestination(target.position);
    }

    void Update() {
        if (agent.remainingDistance < 0.5f) {
            Debug.Log("Reached target");
        }
    }
}

medium

A. Logs "Reached target" immediately on start

B. Logs "Reached target" when agent is close to target

C. Throws a runtime error because NavMeshAgent is missing

D. Never logs anything

Solution

1. Step 1: Understand NavMeshAgent behavior in Start()

   The agent sets its destination to the target's position at start.

2. Step 2: Check Update() condition for logging

   When the agent is within 0.5 units of the target, it logs "Reached target".

3. Final Answer:

   Logs "Reached target" when agent is close to target -> Option B

4. Quick Check:

   Agent logs on close arrival [OK]

Hint: remainingDistance < 0.5 triggers log near target [OK]

Common Mistakes:

• Assuming log happens immediately
• Ignoring NavMeshAgent setup requirement
• Thinking it throws error without NavMeshAgent component

4. Identify the error in this Unity C# code for pathfinding:

public class AgentMover : MonoBehaviour {
    public Transform target;
    private NavMeshAgent agent;

    void Start() {
        agent = GetComponent<NavMeshAgent>();
        agent.SetDestination(target);
    }
}

medium

A. SetDestination requires a Vector3, not a Transform

B. NavMeshAgent component is not assigned

C. Missing Update method to move agent

D. target variable should be private

Solution

1. Step 1: Check SetDestination parameter type

   SetDestination expects a Vector3 position, but target is a Transform object.

2. Step 2: Correct usage of SetDestination

   Use target.position to pass Vector3 instead of target directly.

3. Final Answer:

   SetDestination requires a Vector3, not a Transform -> Option A

4. Quick Check:

   SetDestination needs Vector3 [OK]

Hint: Use target.position, not target, in SetDestination [OK]

Common Mistakes:

• Passing Transform instead of Vector3
• Assuming NavMeshAgent auto-assigns
• Thinking Update method is mandatory for movement

5. You want a NavMeshAgent to move to a target only if the path is valid and reachable. Which code snippet correctly checks this before moving?

hard

A. if (agent.CalculatePath(target.position, new NavMeshPath()) && agent.SetDestination(target.position)) { /* move */ }

B. agent.SetDestination(target.position); if (agent.pathStatus == NavMeshPathStatus.PathComplete) { /* move */ }

C. NavMeshPath path = new NavMeshPath(); if (agent.CalculatePath(target.position, path) && path.status == NavMeshPathStatus.PathComplete) { agent.SetDestination(target.position); }

D. if (agent.isOnNavMesh) { agent.SetDestination(target.position); }

Solution

1. Step 1: Understand path validation with CalculatePath

   CalculatePath fills a NavMeshPath object and returns true if path calculation succeeded.

2. Step 2: Check path status for completeness

   Only if path.status is PathComplete is the path valid and reachable.

3. Step 3: Set destination only if path is valid

   NavMeshPath path = new NavMeshPath(); if (agent.CalculatePath(target.position, path) && path.status == NavMeshPathStatus.PathComplete) { agent.SetDestination(target.position); } correctly creates a path, checks status, then sets destination.

4. Final Answer:

   NavMeshPath path = new NavMeshPath(); if (agent.CalculatePath(target.position, path) && path.status == NavMeshPathStatus.PathComplete) { agent.SetDestination(target.position); } -> Option C

5. Quick Check:

   CalculatePath + PathComplete check = safe move [OK]

Hint: Use CalculatePath and check PathComplete before SetDestination [OK]

Common Mistakes:

• Ignoring path status after CalculatePath
• Calling SetDestination without path check
• Using wrong method signatures