Tags
Creators
Details
Licensed MIT
Published 3 weeks ago
Updated yesterday
All versions
2.7.0+26.2
Release
Chestlogger 2.7.0+26.2yesterday 5
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Required content
Any compatible version
Changes
📦 ChestLogger v2.7.0 (Paper)
🌟 Highlights
- Multi-Version Support: First-class release support for both Paper 26.3 and Paper 26.2.
- Double Chest Logging Overhaul: Zero-duplication transaction tracking across 54-slot inventories.
- Unified Double Chest Audit Merging: Inspecting either half displays the complete, merged history of both container blocks.
🚀 What's New & Changed in Paper
1. Paper 26.3 & 26.2 Dual Releases
We now provide dedicated SemVer 2.0 build-metadata JARs for Paper server administrators:
chestlogger-paper-2.7.0+26.3.jar— Built against Paper API 26.3chestlogger-paper-2.7.0+26.2.jar— Built against Paper API 26.2
2. Double Chest Transaction Deduplication
- Resolved Issue: Player deposits, withdrawals, and hopper transfers in double chests were occasionally logged twice due to Bukkit event propagation across combined inventories.
- Fix: Updated
PaperChestEventListenerwith coordinate half-partitioning. Deltas occurring in slots0–26are assigned strictly to the primary block location, while slots27–53are routed to the linked partner block.
3. Unified Historical Log Merging
- Resolved Issue: When single chests were combined into a double chest, older logs from one side were excluded when inspecting the other side.
- Fix:
/chestlog inspect, the Inspection Wand, and the in-game viewer now dynamically resolve connected double chest halves viaDoubleChestblock states and fetch unified transaction history across both coordinates in a single query.
4. Engine & Performance Stability
- Zero Server Tick Impact: Lock-free MPSC ring buffer processing up to 65,536 events with LZ4 block compression on background worker threads.
- Pure Bukkit Architecture: Zero NMS (net.minecraft.server) dependencies ensures clean compatibility across server builds.
- Self-Healing Storage: Tail recovery engine automatically repairs incomplete or truncated write boundaries on abrupt server shutdowns.
📋 Requirements & Upgrading
- Java: Java 25 JRE/JDK required.
- Server Platform: Paper 1.21.x - 26.2.
- In-Place Upgrade: 100% backward compatible with existing
v2.6.xlogs (logs/*.clog) and indexes (index/*.idx). Simply replace the JAR in yourplugins/directory and restart.
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:kIc1go8Y:oLlHpMs9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kIc1go8Y:oLlHpMs9"
}

