1.0
Compatibility
Changes
Tracks when players place or open chests so admins can see who did what.In-game menu to browse players and their chest history. Saves data either to a local file or to a MySQL database.Setup wizard in chat to choose storage and migrate data.Export a player’s chest history to a CSV file you can open on your computer.Highlight nearby tracked chests with particles so admins can find them.Watchlist + alerts get notified when specific players touch chests or act suspiciously. Auto-remove old records if you want to keep storage small. Note: Needs a MySQL driver if you pick MySQL, and works on Bukkit or Spigot or Paper servers (Minecraft 1.13+).
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:S1H9BwWr:r2t9nYFx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:S1H9BwWr:r2t9nYFx"
}

