/
This release improves faction role management for production servers and makes role behavior easier to control globally.
roles.yml file for all role-related settings.2.4.0 for role-definition compatibility.custom.role.*) are now translated into all eight supported locales: English, German, Spanish, French, Japanese, Portuguese (Brazilian), Russian, and Chinese.roles.overrides.enabled: false.roles.overrides.enabled: true.roles.defaults.owner.prefix, roles.defaults.officer.prefix, and roles.defaults.member.prefix.%pvpindex_player_role%%pvpindex_player_role_prefix%# 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.
# 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.
# 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.
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>2.4.0+
/f role create now 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 from boolean to a typed CreateRoleResult enum with nine distinct values.Owner, Officer, Member) remain protected from destructive edits.1.1.7.
Modern Factions refactor, old-school factions but with modern QOL features