: feature/p1-movement , feature/p2-attack , fix/latency
The key characteristic of GitLab 2 player games is that they are designed to be played collaboratively by two players. This can involve working together to solve puzzles, competing against each other in game-like challenges, or simply building and sharing games using GitLab's platform.
: A multiplayer team-based hero shooter developed as a university thesis. It features a basic player loop including match creation, character selection, and ability-based match functionality. Ticking Arena
GitLab compiles the code and hosts it on a private or public URL. gitlab 2 player games
# .gitlab-ci.yml excerpt pages: stage: deploy script: - cd frontend && npm run build - mv dist ../public artifacts: paths: - public only: - main
Each turn lasts exactly 60 seconds . Players use standard GitLab actions to perform moves:
Conclusion GitLab offers a fertile ground for two-player games that teach engineering practices while providing engaging, asynchronous play. By treating game state as code, leveraging CI as a rules engine, and designing clear workflows for turns and validation, you can create robust, auditable, and fun matches that scale from informal duels to tournament ladders. Whether for onboarding, team building, or just play, GitLab games turn the familiar tools of development into a creative playground. It features a basic player loop including match
One of the most valuable aspects of these open-source projects is the opportunity to learn from their code. The developers use a wide range of modern technologies to create their games. Here’s a breakdown of the tech stacks powering some of the projects mentioned.
Title it: 2-Player Game: Tic-Tac-Toe (Player 1 vs Player 2) . Step 2: Initialize the Board
Game archetypes suited to GitLab
A game.js file (handling the 2-player logic and keyboard inputs). A style.css file (for visual layouts). Step 3: Configure the GitLab CI/CD Pipeline
A game.js file (containing the game logic and multiplayer matchmaking code). Step 3: Configure the CI/CD Pipeline
This back-and-forth interaction creates a loop of feedback and iteration that feels strikingly similar to a strategy game. Each commit is a move; each pipeline run is a dice roll to see if the build survives. Players use standard GitLab actions to perform moves: