Welcome to the Hangar Open Beta. Please report any issue you encounter on GitHub!
Avatar for PvPIndex

Modern Factions refactor, old-school factions but with modern QOL features and TeamsAPI

Report PvPIndex-Factions?

Release
1.1.7

Shadow48402 released PvPIndex-Factions version 1.1.7 on May 31, 2026

Server owner highlights

This release improves faction role management for production servers and makes role behavior easier to control globally.

  • New dedicated roles.yml file 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.0 for 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.
  • Allow faction-specific role customization:
    • Set roles.overrides.enabled: true.
  • Standardize rank visuals across all newly created factions:
    • Configure roles.defaults.owner.prefix, roles.defaults.officer.prefix, and roles.defaults.member.prefix.
  • 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

Fixed

  • /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.

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.

Information

Published onMay 31, 2026
Downloads0

Platforms

Paper Paper (1.21-26.1.2)