Open Tournament is a first-person shooter game built on Unreal Engine, inspired by classic arena shooters like Unreal Tournament and Quake. The game implements comprehensive systems for player movement, combat, AI, user interface, audio, and networking. It features a modular architecture using Unreal Engine's plugin system, with extensive use of the Gameplay Ability System (GAS), Enhanced Input, and replication for multiplayer functionality. The codebase shows thoughtful architectural design in several reusable systems, particularly in settings management, UI composition, messaging, and loading screen handling.
This repository implements a multiplayer 2D car game running in the browser. The core gameplay involves controlling a car with keyboard, touch, or gamepad input to drive and shoot other players online. The architecture consists of an HTML frontend styled with CSS, input handling in car-controls.js, and game logic/physics/rendering/networking in car.js. Key features include real-time multiplayer via Socket.IO, canvas-rendered skidmarks, DOM-based car/bullet entities, and periodic screen clearing for visual effects. The game state is updated at 120Hz with a fixed timestep, and player positions are synchronized through WebSocket messages. External dependencies are limited to the Socket.IO client loaded from a CDN.
This is the open.mp launcher, a desktop application for browsing and connecting to SA-MP/open.mp multiplayer servers for Grand Theft Auto: San Andreas. Built with Tauri (Rust backend) and a React frontend using react-native-web, it provides a server browser with internet, favorites, and recently joined tabs, real-time server querying via UDP, game process injection, and local settings management. The architecture is a typical Tauri app: the Rust backend handles DLL injection, IPC with the game, deeplink registration, and server querying, while the React frontend manages state with Zustand, provides a custom UI component library, and supports 30+ languages. The application is Windows-only due to heavy reliance on Windows-specific APIs and DLL injection. While functional and feature-rich, the codebase shows signs of technical drift (Tauri v1, multiple Rust crate versions, commented migration code, and fragile file validation logic). It is actively maintained but has medium technical drift risk.