1.2.2
Compatibility
Changes
v1.2.2
This pull request introduces several improvements and fixes to the nametag handling system, focusing on more robust and dynamic updates, better configuration management, and improved event handling. The main changes include making nametag updates periodic and event-driven, improving configuration migration and management, and refactoring the code for better maintainability and flexibility.
Nametag Update Improvements:
- Added periodic nametag updates using a configurable interval (
interval), with nametag text now updating dynamically based on player state and location. A newupdateNametagTextsmethod ensures all nametags stay current. [1] [2] [3] - Nametag text and position are now recalculated based on a height offset above the player's head, ensuring better visual alignment. [1] [2]
Event Handling Enhancements:
- Added event listeners for player world change, teleport, death, respawn, and game mode change to trigger a delayed nametag reload, ensuring nametags stay accurate through all relevant player events.
Configuration and Migration:
- Added a new
intervalconfiguration option to both default and main config files, allowing server owners to control how often nametags are updated. Updated theconfig_versionto 2 and improved the configuration migration logic to handle new entries and upgrades. [1] [2] [3] [4]
API and Code Refactoring:
- Refactored
NametagHandlerto expose areload()method (replacingreloadNametags()in command handling), and madeNametagEntitymutable to allow dynamic text updates. [1] [2] [3] [4]
Versioning:
- Bumped the plugin version from 1.2.1 to 1.2.2 in
gradle.propertiesto reflect these changes.
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:Ksss1YfG:lbp4OXli"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ksss1YfG:lbp4OXli"
}

