CentralCorp Panel is the self-hosted web administration panel for CentralCorp Minecraft Launcher. It manages launcher configuration, Azuriom integration, Minecraft versions and loaders, game files, optional mods, access controls and interface settings from a Laravel application.
Documentation · Launcher · Installer · Panel guide
The panel stores launcher settings in its database and provides public endpoints consumed by CentralCorp Launcher. Administrators use authenticated web routes, while the launcher retrieves its configuration, file manifest and optional mod metadata.
This separation makes CentralCorp a self-hosted Minecraft Launcher Panel: the player uses the desktop launcher, and the server team manages it through the web panel.
- Azuriom URL and API-key configuration;
- synchronization of Azuriom servers, roles and users;
- default Minecraft server and server icon management;
- Minecraft version and Forge, Fabric, LegacyFabric, NeoForge or Quilt loader configuration;
- file manager and SHA-1 file manifest for launcher synchronization;
- ignored folders for file verification;
- optional mod names, descriptions, recommendations and images;
- launcher maintenance mode and user/role access lists;
- game directory, embedded Java, memory and verification settings;
- launcher accent color, alerts, video, splash text and role backgrounds;
- Discord Rich Presence configuration;
- settings import/export, administrator accounts and release-based panel updates.
| File management | Guided panel setup |
|---|---|
 |
 |
CentralCorp Launcher reads the panel configuration from /utils/api, distributed files from /data, and optional mod information from /utils/mods. The panel's administrative interface controls the values returned by those endpoints.
See the panel configuration guide for the documented file layout and launcher test flow.
The standalone panel requires a configured Azuriom website URL and API key. It uses the API-extender endpoints to retrieve server, role and user data. Launcher authentication also relies on Azuriom.
The launcher is intended for Azuriom-connected offline-mode Minecraft server infrastructure; Microsoft online-mode servers are not supported.
Administrators select a Minecraft version and a supported loader in the panel. The current configuration lists Forge, Fabric, LegacyFabric, NeoForge and Quilt; the launcher receives the saved values through the public configuration endpoint.
The file manager maintains launcher data and generates the SHA-1 manifest used for verification. Optional mod records provide names, descriptions, images and recommendation status so players can choose supported optional content in the launcher.
CentralCorp Panel requires PHP 8.2 or newer, a supported database, the PHP extensions checked by the installer, writable storage and a correctly configured web server.
The recommended deployment path uses CentralCorp Installer. Follow the panel installation guide for hosting and database steps.
For repository development, inspect composer.json and package.json before running the Laravel and Vite workflows. Frontend assets are built with:
npm install
npm run buildPHP dependencies and application tests use Composer and Artisan.
- Website and documentation — product pages and installation guides
- CentralCorp Launcher — customizable player application
- CentralCorp Panel — this self-hosted administration panel
- CentralCorp Installer — hosting checks and panel deployment
This repository's LICENSE file applies CC0 1.0 Universal. It dedicates the covered work to the public domain to the extent legally possible, with a permissive fallback license. Trademark, patent and third-party rights are not granted by CC0.