Installation
Prepare an existing Altis Life database, install the marketplace ZIP, and create the first secure account.
Requirements
- A web server with PHP 8.2 or later and Apache
mod_rewriteenabled. - PHP extensions
pdo_mysql,mbstring,sodium,curl, andzip. The backup exporter can usemysqldumpwhen available. - A MySQL/MariaDB database already populated by Altis Life. The installer checks for at least
players,vehicles, andgangs. - An AltisControl license from Medel Platforms and temporary write access to create
config.phpandstorage/. - HTTPS for public deployments. The wizard offers a “Require HTTPS” setting.
Package contents
The ZIP generated by build.bat contains the application, installer, these static HTML docs, and database/panel.sql. It excludes config.php, the game database, demo data, tests, local backups, and uploaded logos. database/panel.sql creates only panel tables.
Step-by-step installation
- Extract AltisControl under your web root, for example at
/AltisControl. Keep the directory structure and enable its.htaccessrules. - Prepare an existing Altis Life database and a SQL user that can access it and create
ac_tables. - Open
/AltisControl/install/in a browser. Enter the SQL host, port, database name, username, and password. - Enter the license key, correct base path, owner name and email, and a password of 14–256 characters.
- Review “Require HTTPS” and choose “Verify and install.” The wizard validates the license before creating tables or writing configuration.
- Save the TOTP secret displayed at the end in an authenticator app. It is shown only once.
- Open
/AltisControl/adminand sign in with the email, password, and six-digit 2FA code.
Game database: do not import
altislife.sql over a production database. The SQL used during development is a reference; the marketplace package does not install it.What the installer creates
It writes config.php with the database connection and a local encryption key, creates the ac_ tables, registers the owner, stores the license in encrypted form, and writes storage/.installed. RCON starts in simulated mode and process control is disabled. The installer locks after an owner already exists.
After installation
- Configure live RCON under Settings → RCON and test the connection before enabling live actions.
- To enforce the allowlist and reconcile expired bans, keep
php bin/battle-eye.php --looprunning as a service. - For automatic backups, schedule
php bin/backup-scheduler.phpevery five minutes or supervise its--loopmode. - Create an initial backup under Settings → Backup and separately protect a copy of
config.php.