0.0.2
Compatibility
Changes
The second update is here and it brought in a lot of neat new features!
Command Changes:
- Added /deathsettings with parameters:
- deathsound <id>
- kickondeath <boolean>
- banondeath <boolean>
- kicktext <string>
- banduration <number: minutes>
- soundpitch <number>
- soundvolume <number> (clamps at: 0.01–1)
- unban <username>
- list (shows all the changed settings.)
-
/deathsound <id> is now /deathsettings
-
/soundpermissions <add/list/remove/help>
-
Only operators and permitted users may are allowed to view deathsettings.
-
Anyone can run /soundpermissions but only with the parameter help; /soundpermissions help.
-
Operators cannot be kicked or banned when kick or ban on death is enabled.
Saving Changes:
Settings that were previously saved in the config folder now have their own folder with their own save files:
- allowed-people.txt
- deathsettings.properties
- tempbans.properties
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:bU8vCuSb:U6xJSd6p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bU8vCuSb:U6xJSd6p"
}

