Creators
Details
1.1.7
Compatibility
Changes
Server owner highlights
This release improves faction role management for production servers and makes role behavior easier to control globally.
- New dedicated
roles.ymlfile for all role-related settings. - Safer defaults for rank structure and prefixes.
- New PlaceholderAPI values for role name/prefix in chat, scoreboards, and tablist formats.
- TeamsAPI baseline updated to
2.4.0for role-definition compatibility. - Role-management messages (
custom.role.*) are now translated into all eight supported locales: English, German, Spanish, French, Japanese, Portuguese (Brazilian), Russian, and Chinese.
What you can use it for
- Lock role changes server-wide while keeping role display prefixes:
- Set
roles.overrides.enabled: false.
- Set
- Allow faction-specific role customization:
- Set
roles.overrides.enabled: true.
- Set
- Standardize rank visuals across all newly created factions:
- Configure
roles.defaults.owner.prefix,roles.defaults.officer.prefix, androles.defaults.member.prefix.
- Configure
- Show rank info in PlaceholderAPI-driven scoreboards/chats:
%pvpindex_player_role%%pvpindex_player_role_prefix%
Configuration examples
1) Keep role structure globally controlled (default-safe mode)
# roles.yml
roles:
overrides:
enabled: false
custom:
enabled: true
Use this when you want admins to control rank structure centrally and avoid faction-by-faction role drift.
2) Allow faction-level custom roles
# roles.yml
roles:
overrides:
enabled: true
custom:
enabled: true
min-priority: 11
max-priority: 99
max-per-faction: 8
Use this for community-driven servers where faction leadership should design its own rank ladder.
3) Set consistent role prefixes for new factions
# roles.yml
roles:
defaults:
owner:
prefix: "<gold>[Owner]</gold>"
officer:
prefix: "<yellow>[Officer]</yellow>"
member:
prefix: ""
Use this for clearer chat hierarchy and onboarding visibility.
Commands added / updated
Role management command suite:
/f role list/f role create <name> <priority> [prefix]/f role rename <old> <new>/f role setpriority <role> <priority>/f role setprefix <role> <prefix|none>/f role delete <role>/f role assign <player> <role>
Integrations
- TeamsAPI baseline:
2.4.0+- Modrinth: https://modrinth.com/plugin/teams-api
- PlaceholderAPI role placeholders available:
Fixed
/f role createnow shows a specific error for each failure path (priority out of range, actor rank too high, name already taken, role limit reached, feature disabled) instead of a generic "Could not create that role" message. The service method return type was changed frombooleanto a typedCreateRoleResultenum with nine distinct values.
Notes
- Core roles (
Owner,Officer,Member) remain protected from destructive edits. - Role authority checks apply consistently across legacy rank commands and role assignment.
- Plugin version bumped to
1.1.7.
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:trDfzeaq:VUxKWk82"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:trDfzeaq:VUxKWk82"
}

