
CoreXForLB
CoreXForLB is a lightweight, modern Paper server management utility engineered for server administrators and staff. It provides real-time performance diagnostics, instant dynamic configuration reloads, and an automated log appender that catches uncaught
1.0.2
Compatibility
Changes
CoreXForLB is an advanced Paper server management utility providing real-time telemetry, an interactive admin control GUI, and intelligent plugin error trapping with staff alerts.
Updates
Version 1.0.2 introduces several powerful tools for server administration:
- Interactive Admin Control Panel GUI (
/corex gui) with clickable actions - World, chunk, and entity lag diagnostics (
/corex entities) - Player latency and server average ping telemetry (
/corex ping) - On-demand RAM optimization via manual Garbage Collection (
/corex gc) - Interactive clickable and hoverable staff chat error alerts
Features
CoreXForLB includes a comprehensive suite of monitoring and diagnostic features:
- Interactive 27-slot chest GUI control panel for server administrators
- Native Paper API performance engine tracking real-time TPS and MSPT
- Persistent BossBar and personal ActionBar live performance meters
- Automated TPS drop warning system alerting staff when lag occurs
- Real-time Log4j2 log appender attributing exceptions to specific plugins
- Interactive chat buttons to view diagnostics or export error logs instantly
- World and entity diagnostics showing loaded chunks, entities, and living counts
- Full plugin health overview showing active plugins and error frequencies
- Dynamic hot-reload with
/corex reloadto update configurations instantly - Export system dumping recorded server errors to a text file
Commands
Manage your server using the following administrative commands:
/corex gui- Opens the interactive Admin Control Panel GUI/corex status- Displays real-time server TPS, MSPT, RAM, players, and uptime/corex entities- Lists loaded worlds, chunks, and entity counts/corex ping [player]- Shows player latency or server average ping/corex gc- Runs the Java Garbage Collector to free unused memory/corex reload- Reloads all configuration files and plugin mappings/corex plugins- Displays all loaded plugins with error counts/corex debug- Shows recent plugin error diagnostics in chat/corex export- Exports error history to a text file/corex clear- Clears in-memory error logs/corex bossbar- Toggles the live overhead TPS BossBar/corex actionbar- Toggles the personal live HUD ActionBar/corex help- Shows the command help menu
Permissions
Assign permissions to your staff members using the nodes below:
corex.admin- Full access to all CoreX featurescorex.admin.gui- Allows opening the Admin Control Panel GUIcorex.admin.status- Allows viewing server performance statuscorex.admin.entities- Allows viewing world and entity diagnosticscorex.admin.ping- Allows checking player latencycorex.admin.gc- Allows running the Garbage Collectorcorex.admin.reload- Allows reloading configurationcorex.admin.plugins- Allows listing plugin health statuscorex.admin.debug- Allows viewing error diagnosticscorex.admin.alerts- Receives real-time error notificationscorex.admin.export- Allows exporting error logscorex.admin.bossbar- Allows toggling the live BossBarcorex.admin.actionbar- Allows toggling the personal ActionBar
Installation
Follow these steps to install CoreXForLB on your server:
- Download the
CoreXForLB-1.0.2.jarfile. - Place the jar into your server's
pluginsdirectory. - Start or reload your Paper server (
1.20.4+running Java 17+). - Configure options in
plugins/CoreXForLB/config.ymlas desired.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:cgEz4BQV:duVSWD5z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cgEz4BQV:duVSWD5z"
}
