Tech Enthusiast | Data Explorer | Code Voyager 🚀
- 🔭 Working on Cloud-based ML / AI projects using Python
- 🌱 Learning Cloud platforms, Deep Learning, Scikit-learn, and PyTorch
- ⚡ Fun fact: Good code and good pasta both need the right balance 🍝
Cloud • ML/AI • DevOps • Embedded • Linux • Networking (TCP/UDP)
I invite you to step into a miniature escape room designed entirely within this README. Please allow a brief moment for the page to fully load, as the game relies on internal navigation links.
Your objective is to explore the environment, make informed decisions, and collect the required items to unlock the exit. Each choice you make will redirect you to a corresponding outcome within this document. Some paths lead to progress, others to failure, and a few to hidden endings.
There is no automated state tracking—your inventory exists only through careful reading and memory. Choose wisely, think like an engineer, and pay attention to system hints inspired by Linux, networking, DevOps, and embedded systems.
If at any point the navigation feels unresponsive or confusing, simply scroll back to the start of the game or refresh the page. Multiple endings are possible, but only a handful lead to a successful escape.
Good luck—and may your debugging instincts guide you. 🚀
You’re locked in a lab.
To escape, you must collect 2 items and choose the correct exit.
- 🔑 Keycard
- 🧩 Debug Token
- 🔌 Patch Cable
- 🤖 Microcontroller Chip
🖥️ Server Room • 🌐 Network Closet • 🛠️ Hardware Workshop
You see a Linux terminal left unlocked. A sticky note says:
“Only those who read logs shall pass.”
Choose:
- 📜 Check logs
- 🚀 Run a deployment
- 🧨 Run
rm -rf /(do NOT)
A switch is blinking. Two cables are on the floor. One label says TCP, the other UDP.
Choose:
An Arduino-based lock controls a side door. There’s a desk with parts.
Choose:
You open system logs and notice repeated failures:
auth: keycard requiredci: build failed due to missing token
You discover a hidden drawer with a 🧩 Debug Token.
✅ You obtained: Debug Token
Next move:
You trigger CI/CD… but the pipeline fails:
- “Permission denied. Keycard not found.”
You DO learn something useful: the exit system requires two-factor (Keycard + Token).
Next move:
Everything goes silent. The lab lights turn off.
A voice says: “Nice try.”
❌ Game Over (Chaotic Evil Ending)
Handshake succeeds: SYN → SYN/ACK → ACK ✅
A small panel opens and drops a 🔌 Patch Cable and a note:
“Reliable connection established. The exit scanner is online.”
✅ You obtained: Patch Cable
Next move:
You send a packet… maybe it arrives, maybe it doesn’t.
The switch blinks faster, then triggers an alarm.
❌ Game Over (Unreliable Ending)
You sniff traffic and catch a credential broadcast (bad security!).
You print a temporary 🔑 Keycard token from the panel.
✅ You obtained: Keycard
Next move:
Upload fails: “Brownout detected.”
You need stable power first.
Next move:
You replace a regulator. The board powers up ✅
A compartment opens and reveals a 🤖 Microcontroller Chip.
✅ You obtained: Microcontroller Chip
Next move:
Nice fix. The lock beeps and prints a tiny QR that acts like a 🔑 Keycard.
✅ You obtained: Keycard
Next move:
A scanner asks for:
- Keycard
- Debug Token
- (optional) Patch Cable for fast exit
Choose based on what you collected:
You scan the Keycard and present the Debug Token.
Door unlocks. Fresh air. You’re free. 🥳
🏆 YOU WIN (True Ending)
You scan Keycard + Debug Token, then plug in the Patch Cable.
The door unlocks instantly with a satisfying click. 🔥
🏆 YOU WIN (Speedrun Ending)
The scanner rejects you:
“Two-factor required.”
You’re not ready yet. Go collect what you’re missing.
You find a hidden door labeled:
“Insert MCU to override.”
You insert the chip. The system reboots into maintenance mode.
A hatch opens to the outside.
🏆 YOU WIN (Secret Hardware Ending)