Links
Tags
Creators
Details
Licensed MIT
Published last year
Updated 2 weeks ago
All versions
1.2.0+1.21.7
Release
ChestSee - Chestlogger 1.2.0 for 1.21.72 weeks ago 5
Compatibility
Minecraft: Java Edition
1.21.7
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
New
- In-game lookups, no more digging through the world folder:
/chestsee inspecttoggles inspect mode. Right-click or punch a container to see its log. The container doesn't open and doesn't break while inspect mode is on./chestsee lookup <x y z> [page] [dimension]shows the log of one container./chestsee player <name> [page]shows everything a player did in all containers, newest first. Click an entry to jump to that container's log. The search runs in the background, so big log folders don't lag the server.- All commands work from the console and RCON.
- Furnaces, blast furnaces, smokers and brewing stands are now logged. Only what players put in or take out shows up, not the smelting or brewing itself.
- Chest minecarts, hopper minecarts and chest boats are now logged. Their log files are named after the entity UUID since they can move.
- New config file
config/chestsee.json:retentionDays: remove entries older than X days on server startmaxFileSizeKb: drop the oldest entries when a log file gets too bigexcludedDimensions: don't log in these dimensionscontainers: turn logging off per container typepageSize: entries per page/chestsee reloadapplies changes without a restart.
- Permission nodes for LuckPerms:
chestsee.inspect,chestsee.lookup,chestsee.playerandchestsee.reload. Without a permission mod everything needs OP level 2 like before.
Existing log files keep working, nothing needs to be converted.
Fixes
- 1.1.0 for 1.21.7 wrote log files without the
.txtextension. They are renamed on server start, so the commands find them.
Optional dependencies
Any compatible version
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:LFa3fejY:COoH4WfG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LFa3fejY:COoH4WfG"
}

