2.1.2
Compatibility
Changes
2.1.2:
-
Fixed an issue where chat formatting removed spaces after placeholders, causing messages like “Player:Message” instead of “Player: Message”.
-
Improved chat format handling so that only the title wrapper is removed when a player has no active title, without affecting other parts of the format.
2.1.1:
-
Updated chat formatting behavior: when a player has no active title, the title part is no longer shown (no empty brackets like “[]” or other leftover title decorations).
-
Added a new admin command to set a player’s active title: /rtitle set <player> <title>.
-
Improved tab-completion for the new /rtitle set command: it now suggests only the titles that the selected player actually owns.
-
General command UX improvements for title management and chat formatting.
2.1.0:
New features:
-
Title descriptions are no longer mandatory when granting a title.
-
Added support for an explicit description keyword in the grant command.
-
New command syntax: /rtitle grant <player> <title> /rtitle grant <player> <title> desc <description>
-
Description is only applied when the "desc" keyword is used.
-
Improved admin tab completion: when using /rtitle revoke <player>, tab completion now suggests only titles owned by the selected player.
-
Added full localization support for all player-facing command messages.
-
Added language files for English (en_us) and Russian (ru_ru).
Improvements:
-
Reworked command structure to use proper Brigadier branching.
-
Removed hardcoded command messages and replaced them with translatable components.
-
Improved overall command clarity and usability for both players and administrators.
-
Command logic is now easier to extend and maintain.
Fixes:
-
Fixed incorrect tab completion in the revoke command that previously suggested titles of the command sender instead of the target player.
-
Fixed forced title descriptions when granting titles.
-
Improved error handling when command arguments are missing or incomplete.
Notes: No configuration changes are required.
Existing titles and player data remain fully compatible.
Localization can be extended by adding new language files to the assets folder.
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:z9yZ1KxT:FnM0AiVt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z9yZ1KxT:FnM0AiVt"
}

