Tags
Creators
Details
Licensed ARR
Published last year
Updated 3 months ago
All versions
2.0.0
Release
Command Trace 2.0.010 months ago 103
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
CommandTrace 2.0.0 – Changelog
Major Changes
- Complete rewrite of the logging system for higher reliability and scalability.
- New folder-based log architecture for clean organization.
- Per-player command log files:
PlayerName-UUID.trace. - Dedicated Operator audit logs for high-privilege command tracking.
- Configurable log rotation:
DAILYorWEEKLY.
Logging Layout
logs/
├── console/
├── operators/
└── players/
- All player commands are always logged in
players/. [conversation_history:1] - Operator commands are logged twice: in
players/andoperators/. [conversation_history:1] - Console commands are logged separately in
console/. [conversation_history:1] - Folders are created automatically for each rotation period. [conversation_history:1]
Performance
- 100% asynchronous file writing. [conversation_history:1]
- Designed for zero impact on server TPS, even on high-traffic servers. [conversation_history:1]
- Optimized writer reuse with safe shutdown flushing. [conversation_history:1]
Smart Filtering
- Command blacklist and whitelist support. [conversation_history:1]
- Optional logging of cancelled commands. [conversation_history:1]
commandtrace.bypasspermission to exclude trusted accounts from logging. [conversation_history:1]
Commands
/commandtrace reload | /ct reload -> Reload configuration
/commandtrace status | /ct status -> View logging status
/commandtrace current | /ct current -> View active log folder
⚙️ Configuration
- New
config.ymlwith: [conversation_history:1]rotation-mode:DAILYorWEEKLY.- Customizable log formats.
- Flexible filtering options.
- Operator and Player logging are mandatory and cannot be disabled. [conversation_history:1]
Breaking Changes
- Log file locations have changed to the new folder structure.
- Old single-file logs are no longer used.
✅ Compatibility
- Tested on Paper 1.21.11 and compatible with Paper / Spigot 1.21+.
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:pipW27DB:MITwn1dL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pipW27DB:MITwn1dL"
}

