Bot Gone Rogue

Inspiration

I was heavily inspired by the recent videos of advanced humanoid robots (like Neo, the humanoid robot). They’re incredibly capable — but it sparked a thought: What happens when such a powerful, automated AI misunderstands a simple command? I’ve always been fascinated by 2D game mechanics, and I wanted to explore this idea of “rogue automation” not as a sci-fi epic, but as a chaotic, pixel-style arcade simulation.

What it does

"Bot Gone Rogue" puts you in the operator's chair. You are tasked with managing an AI office assistant that has... started to misinterpret things. The Mission: Issue commands like "Clean Desk" or "Fix Computer" to get work done and score points. The Mayhem: Every command is a gamble. A success earns you points and lowers the Chaos Level. A failure sends the Chaos Level skyrocketing. The Goal: You must survive long enough (10 commands) to unlock the "Shutdown" function. The only way to win the mission is to hit "Shutdown" while the Chaos Level is safely below 40%. If chaos hits 100%, it's game over—the office is destroyed in true "Car Crash Recognition" style.

How I built it

This is a pure JavaScript and HTML5 game built on the Phaser 3 framework, all written during the jam. Engine: Phaser 3 Graphics: All game assets (the "bot" and "glitch" effect) were generated using the AI tool Nano. Audio: The "beep" and "explosion" sounds were sourced from Pixabay. Code: The core logic—managing the chaos, risk, and dynamic personality state of the bot—is all handled with JavaScript.

Challenges I ran into

The biggest challenge was balancing chaos. How much randomness feels fun versus unfair? I spent time tuning the risk percentages for each command, adjusting score rewards, and refining easy mode so that every run feels a bit different but always winnable. Other challenges included:

Implementing keyboard accessibility alongside mouse control.
Managing game states (Intro → Gameplay → Game Over) cleanly.
Ensuring sound, visuals, and personality shifts all sync smoothly.

Accomplishments that I'm proud of

I'm really proud of the Chaos Level as a central mechanic. It's not just a score; it actively changes the game:

It provides a 1.5x score bonus when it's low (rewarding good management).
It's the primary win/lose condition for the 'Shutdown' command.
It dynamically changes the bot's 'personality' (from neutral to sassy to grumpy), which makes the bot feel more alive and, well, more rogue.

What I learned

I learned a lot about rapid prototyping with Phaser 3. More importantly, I learned that a single, simple mechanic (like a 'chaos' variable) can be used to drive the entire game loop, the risk/reward system, and even the game's narrative.

What's next for Bot Gone Rogue

More commands: each with unique risks, rewards, and failure animations.
More modes: like Survival, Story, or Endless Chaos.
A real time leaderboard integration to compete for highest score/the best (or luckiest) operator.
Expanded bot personalities (sarcastic, lazy, overhelpful).
A mobile version of the game.