iTX TechnologiesMirai ecosystem
MCL
Mirai Console Loader
A lightweight, modular, and customizable loader for Mirai.
Legacy project- Brand
- iTX Technologies
- Platforms / runtime
- Java 11+
- Technologies
- Java
About the project
MCL, short for Mirai Console Loader, organizes packages, configuration, and startup for a console environment. It makes downloading, updating, and loading manageable steps, so users can maintain an installation through a shared configuration instead of finding and replacing individual files by hand each time.
MCL Installer can help prepare Java and download MCL during initial setup. MCL then handles routine package management and startup. Users with a suitable runtime can obtain the loader directly, while those who need guided setup can begin with the installer.
Modular loading
Implement core functions through modules and extend the loading process.
Packages and configuration
Manage packages, persist configuration, and select update channels from the command line.
A loading process built from modules
Its foundations include module management, persistent configuration, package management, a downloader with progress reporting, and console logging. Modules implement the main functions and run in defined phases. Extensions can be placed in the designated directory and loaded through Java service discovery. This makes MCL useful for studying how a modular loader works, beyond simply running its startup script.
Control packages and updates
The command line supports adding and removing packages, choosing update channels, selecting and locking versions, and enabling or disabling modules. It can also update runtime libraries while skipping startup. These controls help reproduce an installation or examine the effects of an update. A selected version must still exist in its channel, and historical repository addresses need to be checked separately.
From a release archive to the CLI
The original documentation requires Java 11 or later and describes downloading, extracting, and starting MCL manually. Read the release notes before changing packages and channels with the CLI guide. Plugin file formats differ between versions, so meeting the Java requirement alone does not ensure plugin compatibility. Reproducing an older configuration requires checking the loader, plugins, and repositories together.