Links
Tags
Creators
Details
1.5.4
Compatibility
Changes
Since this plugin has been on github until now, heres what has been done:
-
Built-in Web Panel – Implemented an embedded HTTP server that provides a browser-based dashboard for viewing logged events, with configurable port settings and optional Basic Authentication.
-
Live Dashboard Updates – Added automatic event polling and refresh logic so newly logged events appear in real time while preserving active player, world, and action filters.
-
Event Browsing – Implemented server-side sorting and pagination to efficiently browse large numbers of events, always displaying the newest entries first.
-
Player & Death Summaries – Added aggregated statistics and summary views for player activity and recorded deaths.
-
Enhanced Death Logging – Expanded death records with coordinates, world, and cause information, while adding fallback detection and duplicate protection to ensure reliable logging.
-
Discord Webhook System – Implemented an asynchronous webhook queue with retry/backoff handling, configurable filtering, and reduced console spam by suppressing non-critical queue warnings.
-
Selective Event Filtering – Added support for excluding specific event types (such as inventory/container movements) from Discord notifications while continuing to record them locally.
-
Log File Management – Implemented automatic size-based log rotation to prevent log files from growing indefinitely.
-
Administrative Commands – Added operator commands for managing the webhook queue and retrieving the web panel URL directly from the server.
-
In-Game Log Viewer – Created a per-player inventory GUI for browsing recent logged events without leaving the game.
-
Asynchronous Logging – Implemented non-blocking JSON file logging using dedicated worker threads to minimize impact on the server's main thread.
-
Configurable Logging Framework – Added configurable event filters and thread pool settings, allowing server owners to customize logging behavior and performance.
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:xGpMqYBI:hWyVxgCF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xGpMqYBI:hWyVxgCF"
}

