
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
2.0.0
Compatibility
Changes
CoreXForLB 2.0.0 is the flagship server health suite for Paper servers (supporting versions 1.20 up to 26.3+), offering real-time telemetry, an interactive admin GUI, Discord webhook alerts, tick jitter benchmarking, and smart error trapping.
Major Update
Version 2.0.0 represents a major milestone in CoreX development, bringing enterprise-grade diagnostic tools:
- Non-blocking Discord webhook notifications for plugin errors and TPS drops
- Built-in 10-second tick jitter benchmark with automated server grading
- Chunk lag spotter detecting high entity-density chunks with click-to-teleport
- Comprehensive system diagnostic crash dumps for bug investigations
- Upgraded 27-slot interactive Admin Control Panel GUI
Key Features
CoreXForLB delivers complete server observability with zero performance overhead:
- Native Paper API tick engine measuring accurate TPS and MSPT
- Overhead BossBar and HUD ActionBar real-time performance meters
- Automated TPS drop alert system notifying in-game staff and Discord
- Log4j2 error interceptor isolating faulty plugins with clickable chat actions
- Memory optimizer running Garbage Collection on demand with reclaimed RAM stats
- Detailed world diagnostics listing loaded chunks and entity distributions
- Per-plugin error frequency metrics and health reports
Administrative Commands
Control every aspect of CoreX using the primary administration command:
/corex gui- Opens the interactive Admin Control Panel GUI/corex benchmark- Runs a 10-second tick variance probe and health grade/corex chunks- Displays the top laggy chunks sorted by entity density/corex dump- Generates a complete system diagnostic snapshot file/corex status- Shows real-time TPS, MSPT, RAM, players, and uptime/corex entities- Lists loaded worlds, chunks, and entity statistics/corex ping [player]- Checks latency of yourself or other players/corex gc- Runs Java Garbage Collection to free unallocated RAM/corex reload- Hot-reloads configuration and monitor modules/corex plugins- Displays all loaded plugins with detected error counts/corex debug- Shows recent plugin exceptions 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 personal live HUD ActionBar/corex help- Shows the command help menu
Permission Nodes
Assign permissions to administrators using the permission nodes below:
corex.admin- Full access to all CoreX featurescorex.admin.gui- Allows opening the Admin Control Panel GUIcorex.admin.benchmark- Allows running the server benchmark probecorex.admin.chunks- Allows scanning top laggy chunkscorex.admin.dump- Allows creating diagnostic system dumpscorex.admin.status- Allows viewing real-time server statuscorex.admin.entities- Allows viewing world and entity diagnosticscorex.admin.ping- Allows checking player latencycorex.admin.gc- Allows running the RAM 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 staff error notificationscorex.admin.export- Allows exporting error logscorex.admin.bossbar- Allows toggling the live BossBarcorex.admin.actionbar- Allows toggling the personal ActionBar
Setup Guide
Follow these steps to deploy CoreXForLB 2.0.0 on your server:
- Download
CoreXForLB-2.0.0.jar. - Move the file into your server's
pluginsfolder. - Start or restart your server running Paper 1.20 - 26.3+ with Java 17 or Java 21+.
- Configure optional Discord webhooks in
plugins/CoreXForLB/config.yml.
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:Uc46kZKe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cgEz4BQV:Uc46kZKe"
}
