Tags
Creators
Details
2.2.0
Compatibility
Changes
Improved Rewrote all existing commands to make arguments optional where possible. You can find the updated command syntax at the top of your config.yml instead of the old one.
[Requested by Jekyll] Added a new command (/bodyhealth add [player] [body part] ) for you to be able to modify health values relatively.
Improved Rewrote all TAB completions to make them truly intelligent, suggesting command syntax and possible inputs not only based on your position within the command, but also by analysing your partial inputs and comparing them to possible command completions
Added Health values in commands are now taken as raw health values per default, meaning they are calculated into the corresponding percentages, taking your configuration per body part into account, but you can still modify health values directly in percent by appending a '%' sign to your value. The new TAB completions make sure you don't forget that option
Added support for popular vanish plugins like PremiumVanish and SuperVanish, excluding vanished players from TAB completions.
Added a new config option for you to choose if you also want to force-keep body parts at their new state for the set amount of seconds, that have been modified relatively (Good for excluding health related items, so it's default is "false").
Improved All language files have been updated to not only include the new command, but also a new format, containing definitions for body part names, to make smoother command responses possible. All natively supported languages are updated automatically, but if you made your own language configuration, you have to update it to the new format.
Changed Moved language file generation and validation messages from normal- to dev-debug mode.
Optional dependencies
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:DwIZUWS0:eQHZe2v8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DwIZUWS0:eQHZe2v8"
}

