Tags
Creators
Details
2.0.0
Compatibility
Changes
🇪🇸 Español
Se corrigió y mejoró el sistema de mensajes al reiniciarse las minas.
Cambios principales:
• Se corrigieron los placeholders de los mensajes. • Se agregó una opción para activar o desactivar los mensajes del chat durante el reinicio. • Se agregó una opción independiente para activar o desactivar los mensajes de la consola. • La Actionbar ahora puede configurarse individualmente para cada mina. • Los menús ahora pueden crearse y configurarse utilizando el formato de zMenu. • Desde el menú avanzado de cada mina ahora se puede activar o desactivar:
• Mensajes • Actionbar • Sonidos • PartÃculas • Bossbar
Configuración global:
reset:
messages-enabled: true
actionbar-enabled: true
console-logging-enabled: false
Configuración individual por mina:
visuals:
messages-enabled: true
actionbar-enabled: true
Para desactivar los mensajes y la Actionbar en una mina especÃfica:
visuals:
messages-enabled: false
actionbar-enabled: false
🇺🇸 English
The mine reset messaging system has been fixed and improved.
Main changes:
• Message placeholders have been fixed. • Added an option to enable or disable chat messages during mine resets. • Added a separate option to enable or disable console messages. • The Actionbar can now be configured individually for each mine. • Menus can now be created and configured using the zMenu format. • From each mine's advanced menu, you can now enable or disable:
• Messages • Actionbar • Sounds • Particles • Bossbar
Global configuration:
reset:
messages-enabled: true
actionbar-enabled: true
console-logging-enabled: false
Individual mine configuration:
visuals:
messages-enabled: true
actionbar-enabled: true
To disable messages and the Actionbar for a specific mine:
visuals:
messages-enabled: false
actionbar-enabled: false
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:PXajnyAN:LNpI4eS6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PXajnyAN:LNpI4eS6"
}

