2.0.3
Compatibility
Changes
🇪🇸 Español
Ahora, cuando el plugin detecta datos antiguos o un cambio en el sistema de almacenamiento, los recupera automáticamente antes de iniciar.
Los datos originales no se eliminan, las bóvedas no se duplican y se evita sobrescribir aquellas que ya contengan objetos.
También se reforzó el sistema de guardado para reducir el riesgo de pérdida de datos si el servidor se apaga, se elimina una bóveda o se cambia de versión mientras todavía existen guardados pendientes.
🇺🇸 English
The plugin now automatically recovers legacy data or data from a previous storage system before starting.
The original data is not deleted, vaults are not duplicated, and vaults that already contain items are protected from being overwritten.
The saving system has also been improved to reduce the risk of data loss if the server shuts down, a vault is deleted, or the plugin version is changed while save operations are still pending.
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:JyaEopfV:bs1h8x1d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JyaEopfV:bs1h8x1d"
}

