📘 Scenario:

The Justice League Command Center is equipped with a high-tech Control Panel (Invoker). Each button on this panel is wired to a Command object that knows what action to take and which superhero (Receiver) to call upon. When danger strikes, the panel simply triggers the right command—heroes leap into action without the panel knowing how it all works.

• 🦸‍♂️ Superman – flies in to handle large-scale threats
• 🦇 Batman – uses tech and tactics to handle chaos
• ⚡ Flash – speeds in for rescue and recovery missions

⚠️ Problem:

• The Control Panel must handle dozens of mission types and heroes, leading to tightly coupled code.
• Adding new buttons or actions requires altering core control logic.
• No uniform way to trigger complex sequences like undo, queue, or log.

💡 Command Pattern Solution:

Each action is wrapped in a Command object that decouples the invoker (panel) from the receiver (hero). The Control Panel doesn't need to know how Superman flies or how Batman throws his batarang. All it does is call execute() on the command—and the magic happens behind the scenes.

🖥️ Output:

=== Crisis: Alien Drone Attack ===

[ControlPanel] Activating command...
[Superman] Flying at hypersonic speed to Metropolis!
[Superman] Rescuing civilians from collapsing buildings!

=== Crisis: Joker’s Drone Swarm ===

[ControlPanel] Activating command...
[Batman] Launching Batarang to disable the drone swarm!

=== Crisis: Collapsed Subway Tunnel ===

[ControlPanel] Activating command...
[Flash] Speed-blur rescuing victims in seconds!