SnookerGameEx

SnookerGameEx: Real-Time Multiplayer Snooker Game

SnookerGameEx is a dynamic multiplayer snooker game developed using the Phoenix Framework and Elixir. This project harnesses the principles of functional programming and numerical computing to create an engaging and interactive gaming experience.

Project Highlights

• OTP Supervision Tree: The application is built on OTP principles, leveraging supervisors to manage the lifecycle of dynamic processes, which enhances robustness and fault tolerance.

• Fixed-Step Game Loop: The CollisionEngine operates on a fixed-step loop independent of the rendering frame rate. This methodology guarantees that the simulation remains deterministic, ensuring consistent gameplay regardless of client performance or network conditions.

• Stateful Processes: Each ball on the snooker table is represented by an independent GenServer process, referred to as Particle, which maintains its own state (position, velocity, etc.).

• Optimized Collision Detection: The game employs advanced spatial partitioning techniques such as Quadtree or SpatialHash to enhance collision detection efficiency, thus mitigating the performance hit associated with O(n²) checks.

• Numerical Elixir (Nx): Heavy computational tasks related to collision detection and response are offloaded to Nx, enabling just-in-time compilation and GPU acceleration, resulting in superior performance.

• Real-time Updates: Utilization of Phoenix.PubSub allows for real-time broadcasting of game state changes to the LiveView, ensuring players receive immediate feedback within their browsers.

Architecture Overview

Core Modules:

• SnookerGameEx.Application: Acts as the entry point of the application, responsible for bootstrapping the web endpoint, PubSub, and the supervisors handling game simulations.

• SnookerGameEx.ParticleSupervisor: A dynamic supervisor that manages the lifecycle of all ball processes, including creation and initialization.

• SnookerGameEx.CollisionEngine: This central simulation engine, implemented as a GenServer, runs the main game loop, dictates particle movements, detects collisions, and computes resolutions.

• SnookerGameEx.Particle: Represents each snooker ball as a GenServer, capable of storing and updating its own state while communicating with the frontend during state changes.

• SnookerGameEx.Physics: A stateless module that employs Nx.Defn for JIT-compiled CPU/GPU operations, managing narrow-phase collision detection and resolution.

Data Structures:

• SnookerGameEx.Quadtree / SnookerGameEx.SpatialHash: Employed for spatial partitioning, these structures optimize collision detection by filtering only relevant particles based on proximity.

Web Interface:

• SnookerGameExWeb.SnookerGameLive: The core LiveView module that handles rendering of the game, user interactions, and subscriptions to game updates through PubSub.

• assets/js/app.js: Client-side JavaScript featuring a CanvasHook that facilitates HTML5 canvas rendering, allowing the game board, cue, and balls to come alive on the screen while managing updates from the backend.

Further Exploration

To learn more about implementing and deploying this game, visit the Phoenix deployment guides for production-ready configurations. For those interested in understanding more about the Phoenix framework, the official website and documentation are available at phoenixframework.org and the related guides can be found at hexdocs.pm/phoenix/overview.html. Join the community discussions on the Elixir Forum - Phoenix for support and insights.