📘 Scenario:

In the neon-lit city of Neo Aegis, stealth drones patrol government facilities. Each drone (the Context) operates in three distinct modes:

• Patrol – quietly navigates preset paths
• Alert – takes cover and scans after noticing unusual activity
• Attack – opens fire when an intruder is fully detected

As events occur—like seeEnemy(), hearNoise(), enemyInRange(), or loseEnemy()—the drone’s behavior shifts accordingly.

⚠️ Problem:

• Managing state transitions with if-else or switch logic clutters the code.
• All state-specific behavior lives inside one massive class.
• Adding new states or transitions becomes error-prone.

💡 State Pattern Solution:

Each drone mode is encapsulated as a separate class implementing a common State interface. The drone switches its internal currentState dynamically based on real-time input. This keeps state-specific logic modular, extensible, and easy to maintain.

🖥️ Output:

[PatrolState] Guard is patrolling the area.
[PatrolState] Intruder spotted! Switching to ALERT state.
[AlertState] Guard is taking cover and surveying the area.

[AlertState] Target in range! Switching to ATTACK state.
[AttackState] Guard is engaging the enemy aggressively.

[AttackState] Target escaped! Switching to PATROL state.
[PatrolState] Guard is patrolling the area.