Chess Soul

Development Period: May 2025 - July 2025

Chess Soul is a networked multiplayer chess game, featuring TCP-based client-server architecture, complete chess rule validation, 3D piece rendering with multiple model sets, and real-time game state synchronization. The project demonstrates expertise in network programming, game state management, and 3D graphics.

Demo

Main Features

Network System

ChessSoul uses the NetworkSystem in IglooEngine, a TCP-based client-server architecture with unified codebase supporting both server and client modes, to support networked gameplay.

Dual-Mode Architecture

Single Executable Design: Same binary runs as either Server or Client based on startup configuration. Server listens on configurable port; Client connects to specified IP:Port.
NetworkSystem Manager: Central singleton handling socket initialization (WinSock2 WSAStartup), connection lifecycle, and mode switching. Provides IsServer()/IsClient() queries for game logic branching.
Non-Blocking I/O: Sockets configured with ioctlsocket(FIONBIO) for non-blocking operations. Game loop polls for data without stalling rendering.

NetworkConnection Structure

Socket Handle: Platform-specific SOCKET wrapper with connection state tracking (DISCONNECTED, CONNECTING, CONNECTED, ERROR).
Bidirectional Buffers: Dual std::deque<uint8_t> for send and receive queues. Outbound data queued immediately; flushed on next network tick. Inbound data accumulated until complete message received.
Message Framing: Length-prefixed protocol (4-byte header + payload). Handles TCP stream fragmentation—partial reads accumulated until full message available.
Heartbeat System: Periodic ping/pong messages detect stale connections. Timeout triggers automatic disconnect and reconnection attempt.

Server Implementation

Listen Socket: Binds to port, accepts incoming connections via accept(). Maximum 2 clients (White and Black players).
Client Management: Tracks connected clients with player assignment. First connection = White, second = Black. Spectator mode for additional connections (receive-only).
Authoritative Game State: Server validates all moves, maintains canonical board state, broadcasts state updates to all clients. Prevents cheating via client-side manipulation.
Broadcast System: Server relays validated moves and state changes to all connected clients simultaneously.

Client Implementation

Connection Flow: DNS resolution → TCP connect() → Handshake (send player info) → Wait for game start signal.
Optimistic Updates: Client applies moves locally for responsive feel, then validates against server response. Rollback on rejection.

Reconnection Logic: Automatic reconnection attempts on disconnect with exponential backoff. Rejoins game in progress if still active.

Command Protocol

Event-based message protocol with typed commands for all game operations.