0.0.6
Compatibility
Changes
SafeChest v0.0.6 - Hotfix
What's Fixed?
This update fixes a game-breaking bug introduced in v0.0.5 that prevented chests from saving or loading.
- ✅ Fixed SQL Error: Players will no longer see "no such table: angelchests" errors in the console.
- ✅ Database Sync: The plugin now correctly saves and loads chest data from the
safecheststable. - ✅ Config Fix: Default database filename is now correctly set to
safechests.db.
How to Update
- Stop your server.
- Go to
plugins/SafeChest/. - Delete
safechests.db(This is important to fix the schema mismatch). - Install the new
.jarfile. - Start your server.
Note
Your previous chests from v0.0.5 may not be recoverable as the table was not being written to correctly. This update ensures all future chests are saved properly.
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:7CmPGtjq:8eXC77R1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7CmPGtjq:8eXC77R1"
}

