1.2
Compatibility
Changes
Version 1.2 - The Vampirism Update
This update introduces the new Vampirism ability for high-level dogs and improves the pet info display!
šØ Important: Manual Configuration Update Required šØ
This version adds new features and requires you to manually add new lines to your config.yml file. The plugin's new auto-updater will handle future updates, but for this transition, a manual addition is needed to preserve your settings.
Please add the following keys to your config.yml:
- Add the
config-versionkey at the very top of the file:config-version: 2 - Add the
vampirismparameters underupgrades.damage:upgrades: damage: # ... existing settings ... vampirism-required-level: 10 vampirism-heal-percentage: 0.10 - Add the new
messagesfor the ability display:messages: # ... existing settings ... pet-info-ability: " &6Ability: &f{value}" pet-info-ability-vampirism: "Vampirism" pet-info-ability-none: "None" hover-ability-vampirism-unlocked: "&aActive Ability: Vampirism\n&eHeals the dog for {percent}% of the damage it deals." hover-ability-vampirism-locked: "&7Unlockable Ability: Vampirism\n&eUnlocks at Damage Level {level}."
⨠New Features
- Vampirism (Lifesteal) Ability: Dogs that reach a high Damage Level (configurable) will now gain the Vampirism ability, healing them for a percentage of the damage they deal with each hit.
š Improvements
- Improved Pet Info Display: The
/petinfocommand now shows a dedicated "Ability:" line. Hovering over this line will show details about the current active ability (like Vampirism) or the next one that can be unlocked.
š§ Configuration
- Vampirism Control: Added
vampirism-required-levelandvampirism-heal-percentageto give server owners full control over the new ability. - New Translatable Messages: Added new message keys for the ability display and its hover text to support full translation.
- Config Versioning: A
config-versionkey has been added to facilitate smoother updates in the future.
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:3wem5Vai:VylSDCVm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3wem5Vai:VylSDCVm"
}

