GLOBAL.MACHINE
- 1 Devlogs
- 1 Total hours
Global.Machine is a Text based Co-Op game. You and a dozen (give or take) other people across the world work together to solve tasks, gain points, and scale the leaderboard!
##Dev Log - 01
Building a Real Time Cooperative Terminal UI
Phase 1: The Vision & Core Interface Architecture
The G.M project began with a clear idea: create an immersive, retro-style cooperative multiplayer hacking game that runs directly inside a web browser terminal.
The baseline architecture was laid down using simple HTML5, custom CSS layout wrappers, and raw JavaScript. To power the global backend state without spinning up a heavy node server, I integrated Supabase as the serverless infrastructure layer. I built the first core data channel using a global_logs table, allowing players to type commands into their local console and broadcast them into a shared feed.
Phase 2: Live Streams & The Synchronized Puzzle Concept
With global text casting established, I shifted focus to core multiplayer mechanics. I wanted to move beyond basic chat boxes and introduce cooperative puzzles that require active collaboration.
I had introduced
-The Biometric Mainframe Bypass.
The goal was simple but mechanically tricky: force 5 distinct players to hold down the [ H ] key simultaneously to progress. To handle this without constant database thrashing, I tapped into Supabase Presence, tracking ephemeral user states on websocket layers rather than continuous disk updates.
Phase 3: Rolling a Custom, Cryptographic Auth Pipeline
For identification and eventual leaderboards, I needed a login and registration system, but traditional email/password validation didn’t match the command-line immersion of the project (and to be fair you wouldn’t want to give out your email to a random website either would you?). So of course I built a custom, pure-game registration process from scratch.
Now of course in respect to security, storing plain-text passwords was out of the question. I engineered a secure frontend hashing pipeline using the browser’s native Web Crypto API (crypto.subtle). When a player logs in or registers, their raw passcode is processed instantly through a SHA-256 one way cryptographic hash. The raw password never leaves the client machine; only the un-reversible hash string is sent to our custom players table in Supabase.
I am currently working on debugging game logic, H key detection, and fixing relative optimization issues.
The game lies incomplete. 👁️
