How I Built a Modular Multiplayer Game Engine with Node.js and Socket.io

I recently completed a project called GuessGrid, a real-time "Guess the Secret" game. While the frontend is straightforward, the backend was a deep dive into state management and real-time permissions.

The Modular Approach

Instead of a monolithic spaghetti file, I followed a professional modular structure to keep the code clean and testable:

1. gameStore.js: Manages the persistent memory for rooms, players, and scores.

2. socketHandler.js: The Referee that handles all events and enforces the game rules.

3. server.js: The entry point that wires the Express server and the HTTP instance.

Enforcing Referee Rules

A core requirement was ensuring the Game Master (the person who sets the secret) couldn't cheat by guessing their own answer. I handled this via a simple yet effective server-side gatekeeper:

if (socket.id === session.gameMaster) {
    return socket.emit('error_message', "You are the GM! You can't guess your own secret.");
}

Key Technical Takeaways:

Server-Side Timers: To prevent players from manipulating the clock in the browser, the 60-second game timer runs strictly on the server.

Graceful Disconnection: I implemented a disconnecting listener to clean up memory and rotate the GM immediately if they leave mid-round.

UI State Sync: Ensuring that when a game starts, the GM sees a Monitoring screen while players see a Guess input.

Check out the project here:

GitHub: https://github.com/dillibs001/GuessGrid-

Live Demo: https://guessgrid-59sn.onrender.com

#javascript #nodejs #backend #webdev #socketio