Live demo 🚀 • Installation 📦 • Contributing 💻

Open-source OGame redesign clone

[](https://github.com/lanedirt/OGameX/releases) [](https://github.com/lanedirt/OGameX/actions/workflows/run-tests-docker-compose.yml) [](https://github.com/lanedirt/OGameX/actions/workflows/run-tests-sqlite.yml) [](https://github.com/lanedirt/OGameX/actions/workflows/run-phpstan-code-analysis.yml) [](https://github.com/lanedirt/OGameX/actions/workflows/run-laravel-pint-code-style-checker.yml)

[](https://github.com/lanedirt/OGameX/issues?q=is%3Aopen+is%3Aissue+label%3A"good+first+issue") [](https://discord.gg/HJ4QRxxB5N)

OGameX is an open-source OGame redesign clone. This clone is built fully from scratch using the Laravel 11.x framework and uses modern PHP practices. All major functionality is covered by unit and feature tests which automatically run on every build.

We welcome any and all contributions to this project! If you want to help out, please read the contributing section. If you have any questions you can join the OGameX discord to get in touch with the maintainers and other contributors.

Disclaimer: this project is purely fan-based and does not contain any commercial features. All backend code is written from scratch. The rights and concepts for the artwork and frontend belong to the original creators: GameForge GmbH. Support them by checking out the official version: https://ogame.org.

🖥️ Live demo

• Main branch (nightly builds): https://main.ogamex.dev
• Latest stable release (0.8.0): https://release.ogamex.dev

📝 Table of Contents

• 1. Example screenshots
• 2. About the author
• 3. Goal
• 4. Current State of the Project
  • a) Upcoming Features
• 5. Contributing
• 6. Disclaimer
• 7. Installation
  • a) Development: Install OGameX using Docker
  • b) Production: Install OGameX using Docker
  • c) Tips for initial setup
• 8. Support
• 9. Sponsorship
• 10. License

🖥️ Example screenshots

✨ About the author

My (@lanedirt) journey into software development began in 2007 at the age of 14 when I discovered the source code for Ugamela, an early open-source PHP clone of OGame. I really liked running my own browser game server and dedicated myself to modifying this version and translating it to Dutch, leading to the launch of OGameX.nl. This server, active from 2007 to 2009, nurtured a small yet engaged community. This experience not only sparked my passion for software development but also laid the groundwork for my professional career. OGame has always held a special place in my heart, which is why now, 15 years later, I've decided to return to it and create this open-source clone from the ground up.

✨ Goal

The primary goal of this fan-based project is to engineer a faithful rendition of OGame, specifically reflecting its state prior to the Lifeforms update introduced in 2020. This initiative, purely fan-based and non-commercial, is pursued strictly for educational purposes.

🖥️ Current State of the Project

OGameX is under active development with several core features already implemented:

• Registration and login
• Planets and resource management (metal, crystal, deuterium, energy)
• Building and updating resources, facilities, shipyards, and defenses
• Galaxy overview
• Planet switching
• Highscore system
• Messages system
• Battle system
• Basic admin panel
• Fleet dispatch missions
  • Transport
  • Deployment
  • Colonisation
  • Espionage
  • Attack
  • Recycle

a) Upcoming Features

New features are continuously being added. Upcoming major features:

• Support for Moons
  • Moon creation through debris field after battle
  • Moon buildings
  • Phalanx
  • Moon destruction fleet dispatch mission
• Alliance system
• ACS fleet dispatch missions

🚀 Contributing

Contributions are warmly welcomed, whether in development, testing, or spreading the word. Feel free to submit pull requests or contact me for any other contributions.

A good starting point are issues labeled as "good first issue".

Read the CONTRIBUTING.md file for more information.

📓 Disclaimer

This project is a non-commercial hobby project. All rights and concepts related to OGame are owned by GameForge GmbH. We encourage supporters to try the official OGame at https://ogame.org to support its creators.

🖥️ Installation

The easiest way to get OGameX up and running on your own machine is by running the Docker containers via the docker-compose.yml file that is supplied in this repository.

Alternatively, you can also deploy this project manually on any host that supports at least the following:

• PHP >= 8.2
• MySQL/MariaDB
• Ability to enable specific PHP extensions (Ctype, cURL, DOM, Fileinfo and more...)

See the full list of requirements for Laravel 11.x and how to deploy to a server here: https://laravel.com/docs/11.x/deployment.

a) Development: Install OGameX using Docker

For local development you can run the default docker-compose file that is included in this repository. This configuration is optimized for development and includes several tools that are useful for debugging and testing.

1. Clone the repository.

   $ git clone https://github.com/lanedirt/OGameX.git
   $ cd OGameX

2. Copy .env.example to .env.

   $ cp .env.example .env

3. Launch the project using Docker Compose:

   $ docker compose up -d

   Note: The default setup binds to ports 80/443. Modify docker-compose.yml if needed. PhpMyAdmin is also included for database management and is bound to port 8080. Modify docker-compose.yml if needed.

4. Access the "ogame-app" Docker container:

   $ docker exec -it ogame-app /bin/bash

5. Run Laravel setup commands to download composer dependencies, generate an encryption key and prepare the database:

   $ composer install
   $ php artisan key:generate
   $ php artisan migrate

After completing the setup, visit http://localhost to access OGameX. You first need to create an account (no email validation), afterwards you can login using that account.

b) Production: Install OGameX using Docker

For production there is a separate docker-compose file that is used to run the application. This file is called docker-compose.prod.yml. This configuration contains several performance optimizations and security settings that are not present in the development configuration.

Caution: the production configuration is not yet fully optimized and should be used with caution. As an example, the database root user uses a default password which should be changed to something unique. You should review all settings before deploying this project to a publicly accessible server.

Note: The instructions below are for Linux. OGameX should also work under Docker for Windows but the steps might be a little bit different.

1. The OGameX docker containers are expected to be run under a separate (non-root) user. Create a new user (e.g., ogamex) and add it to the Docker group:

   $ sudo useradd -m ogamex
   $ sudo usermod -aG docker ogamex

2. Switch to the new user (ogamex):

   $ sudo su ogamex

3. Clone the git repo and run the Docker commands as the ogamex user to ensure all files are created with the correct permissions.

   $ git clone https://github.com/lanedirt/OGameX.git
   $ cd OGameX

4. Copy .env.example-prod to .env.

   $ cp .env.example-prod .env

5. Launch the project using Docker Compose:

   $ docker compose -f docker-compose.prod.yml up -d --build --force-recreate

   Note: The default setup binds to ports 80/443. Modify docker-compose.yml if needed.

6. Access the "ogame-app" Docker container:

   $ docker exec -it ogame-app /bin/bash

7. Run Laravel setup commands to download composer dependencies, generate an encryption key, cache configuration and prepare the database:

   $ composer install --no-dev
   $ php artisan key:generate --force
   $ php artisan migrate --force
   $ php artisan cache:clear && php artisan config:cache && php artisan route:cache && php artisan view:cache

   Note: The default setup binds to ports 80/443. PhpMyAdmin is also included for database management and is bound to port 8080, however to access it you need to explicitly specify your IP addresses via ./docker/phpmyadmin/.htaccess for safety purposes. Modify docker-compose.yml or .htaccess if needed.

After completing the setup, visit https://localhost to access OGameX. You first need to create an account (no email validation), afterwards you can login using that account.

Note: The production version runs in forced-HTTPS (redirect) mode by default using a self-signed SSL certificate. If you want to access the application via HTTP, open .env and change APP_ENV from production to local.

c) Tips for initial setup

• Admin account: By default, the first registered user is assigned the admin role which can see the admin bar and is able to change server settings. You can also assign the admin role manually via the command line:

  $ php artisan ogamex:assign-admin-role {username}

  To remove the admin role from a user, use the following command:

  $ php artisan ogamex:remove-admin-role {username}

📞 Support

Did you encounter issues in this project? Please open a ticket on GitHub and we'll try to help you out as soon as possible.

💰 Sponsorship

We thank the following parties for sponsoring this project:

JetBrains Providing free open-source licenses for PhpStorm, WebStorm, and DataGrip.

Interested in supporting OGameX? We welcome sponsorships of all sizes! Your support helps us maintain and improve this open-source project. Please get in touch with us via GitHub or Discord to discuss sponsorship opportunities.

📰 License

The OGameX Laravel source code is open-source software licensed under the MIT license. See the LICENSE file for more details. All rights and concepts related to OGame are owned by GameForge GmbH.