
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.1
Compatibility
Changes
CoreXForLB is a high-performance Paper server utility providing real-time diagnostics, live TPS displays, and intelligent plugin error trapping with instant staff notifications.
What's New in 1.0.1
This update brings major improvements over 1.0.0 including a live BossBar monitor, personal ActionBar TPS display, automatic TPS drop alerts, a full plugin health inspector, error log export, and staff join health summaries.
Features
- Live BossBar TPS monitor with color-coded health indicators
- Personal ActionBar TPS display toggled per player
- Automatic TPS drop alert system with configurable threshold
- Staff join health summary showing TPS, RAM and plugin count
- Real-time plugin error trapping via Log4j2 with stack trace attribution
- Full plugin health inspector listing error counts per plugin
- Error log export to file with
/corex export - Dynamic hot-reload with
/corex reload - Smart alert throttling to prevent staff chat spam
Commands
CoreXForLB provides the following staff commands:
/corex status— Real-time TPS, MSPT, RAM, players and uptime/corex plugins— Full plugin list with health and error count/corex debug— Recent error diagnostics and exception log/corex bossbar— Toggle persistent live TPS BossBar/corex actionbar— Toggle personal live TPS ActionBar/corex export— Export error history to a log file/corex clear— Clear in-memory error history/corex reload— Hot-reload all configuration
Installation
- Download
CoreXForLB-1.0.1.jar - Place it in your server's
pluginsdirectory - Start or reload your Paper server
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:ZyS12MzQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cgEz4BQV:ZyS12MzQ"
}
