Enemy AI and NPC Systems

# CHAPTER 11

Enemy AI and NPC Systems #

1. Introduction #

2. Learning Objectives #

• Use an Area2D to create a "Line of Sight" or Detection radius.

• Understand the logic of an AI State Machine (Idle, Patrol, Chase, Attack).

• Implement basic "Follow the Player" vector math.

• Use the NavigationRegion2D to define walkable areas in a level.

• Use the NavigationAgent2D node for complex obstacle avoidance.

3. The Detection Zone (Vision) #

• Attach an Area2D as a child of the Enemy. Give it a large CollisionShape2D (Circle) to represent its vision radius.

• When the Player walks into this circle, the bodyentered signal fires. The Enemy script saves a reference to the Player object and switches its state from "Idle" to "Chase."

• When the Player runs out of the circle, bodyexited fires, and the Enemy switches back to "Idle."

4. Basic Chase Logic (Vector Math) #

1. 1. Find the direction pointing from the Enemy to the Player.

1. 2. Multiply that direction by the Enemy's speed to get velocity.

1. 3. Call moveandslide().

5. Pathfinding (NavigationAgent2D) #

• The Map (NavigationRegion2D): You add this to your Level and define the floor. It generates a "NavMesh" (a web of safe, walkable polygons).

• The Brain (NavigationAgent2D): You add this node to your Enemy. You give it a target (the Player's position). The Agent looks at the NavMesh, calculates the fastest route *around* the brick wall, and gives your Enemy script the exact vector to take the next step.

6. The State Machine (The AI Brain) #

• IDLE: Standing still, playing a breathing animation.

• PATROL: Walking between predefined points.

• CHASE: Running toward the player.

• ATTACK: Swinging a sword.

# A simple GDScript State Machine using an Enum
enum State { IDLE, CHASE, ATTACK }
var current_state = State.IDLE

func _physics_process(delta):
    match current_state:
        State.IDLE:
            play_animation("idle")
            # Wait for detection area signal to change state
        State.CHASE:
            play_animation("run")
            chase_player()
        State.ATTACK:
            swing_sword()

7. Visual Learning: State Machine Flow #

          [ State: IDLE ]
                 |                  ^
  (Player enters Detection Area)    | (Player exits Detection Area)
                 v                  |
          [ State: CHASE ] ---------+
                 |                  ^
(Player gets within Attack Range)   | (Player runs out of Attack Range)
                 v                  |
          [ State: ATTACK ] --------+

8. Best Practices #

• Use match Statements for State Machines: GDScript has a match keyword (similar to switch in C++). Always use match instead of long if/elif chains when building a State Machine. It is much cleaner, faster to read, and less prone to logic errors.

9. Common Mistakes #

• Memory Leaks from Stored References: If an Enemy detects the Player, it saves var target = body. If the Player is killed and deleted from the game (queuefree()), the Enemy's code will still try to chase the target. Because the target no longer exists, the game will crash with a "Null Instance" error. Always check if isinstancevalid(target): before chasing!

1. 3. In the Zombie script, create a variable: var playertarget = null.

1. 4. Connect the DetectionZone's bodyentered signal to the script:

1. 5. Connect bodyexited:

1. 6. In physicsprocess(delta), write:

if player_target != null:
    var direction = (player_target.global_position - global_position).normalized()
    velocity = direction * 100
else:
    velocity = Vector2.ZERO
move_and_slide()

1. 7. Place the Zombie in your level. Run near it, and it will chase you. Run away, and it will stop!

11. Practice Exercises #

1. 1. What math calculation is required to find the vector pointing from Object A to Object B?

1. 2. Explain the purpose of a State Machine in NPC programming.

12. MCQs with Answers #

13. Interview Questions #

• Q: Explain the relationship between NavigationRegion2D (the NavMesh) and NavigationAgent2D. How do they work together to achieve pathfinding?

• Q: Walk me through the GDScript implementation of a finite State Machine using Enums and the match statement. Why is this better than using nested if statements?

• Q: If an enemy is currently referencing the Player node to chase it, and the Player node is destroyed, the game crashes. How do you safely check if an object still exists in Godot before interacting with it?

14. FAQs #

15. Summary #

16. Next Chapter Recommendation #