PvPIndex Factions

Fixed

• Fixed bStats created_factions chart to reset the counter after each report, ensuring it shows the number of factions created in the reporting period rather than the cumulative total since startup.

Changed

• Updated TeamsAPI integration from 2.4.0 to 2.5.0.

Added

• TeamsService.getTeamIds() - returns all team UUIDs for iteration without loading full team objects. Consumers can iterate over team IDs for bulk operations without loading each full Team object.
• Team.getOwner() - default method available via existing getOwnerUUID() and getMember() implementation. Returns the owner's TeamMember directly.

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

• TeamsAPI baseline: 2.4.0+
  • Modrinth: https://modrinth.com/plugin/teams-api
• PlaceholderAPI role placeholders available:
  • Modrinth: https://modrinth.com/plugin/placeholderapi

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.

Added

• Faction Chests:
  • New /f chest command group for shared faction storage.
  • Added subcommands: /f chest list, /f chest open <name>, /f chest create <name>, /f chest delete <name>.
  • /f chest opens the configured default chest (factions.team-chest.default-name) and auto-creates it on first use.
  • Per-faction chest count is capped by factions.max-team-chests (default: 1).
  • New permission nodes: factions.cmd.chest, factions.cmd.chest.create, and factions.cmd.chest.delete.

Changed

• Bumped plugin version to 1.1.6.
• Synced release metadata and public listing copy for this release.

Documentation

• Updated TeamsAPI requirement references in public docs/listings to 2.3.0+ to match the current integration baseline.

Fixed

• Fixed startup crash on servers using older TeamsAPI builds that do not provide TeamsChestService. TeamsAPI chest provider registration is now optional and loaded reflectively, so the plugin enables normally and keeps other available TeamsAPI adapters active.

This version is a small bugfix for the /fa help command. To have effect reset of the translation file is required.

Fixed

• Fixed MiniMessage MiniMessage translation for /fa help
• Fixed configurable default messages for /fa help

Fixed

• All /f subcommands broken when TeamsAPI is absent: FactionCommandExecutor and FactionTabCompleter held direct import statements for TeamsAPI classes. On Paper's isolated plugin classloader this caused NoClassDefFoundError at class-load time when TeamsAPI was not installed, preventing the executor from being registered and making every /f <subcommand> (including /f info, /f map, etc.) fail with "Invalid command!".

  Introduced TeamsCommandBridge (no TeamsAPI imports, loaded unconditionally) and TeamsCommandBridgeImpl (imports TeamsAPI, instantiated only via reflection when TeamsAPI is confirmed present). Mirrors the existing TeamsApiRegistrar isolation pattern. With TeamsAPI absent the bridge is null and all subcommands route through the local CommandRegistry as intended.

Added

• /f info detail pages (/f info page <n> [faction]): the summary view now shows a hint pointing players to /f info page <n>. The new page subcommand displays additional faction stats across paginated pages:
  • Online member count with a hover list of names
  • Rank distribution (members per rank)
  • Activity stats - inactive-over-7-days count and last-seen summary
  • Relations summary (Ally / Truce / Neutral / Enemy counts)
  • Claim capacity with RAIDABLE / STABLE risk indicator
  • Full power breakdown (total, member contribution, power boost)
  • Top 3 power contributors
  • Newest member and most-recent activity timestamps
• Sender context tracking for /f info page: the last faction viewed per sender is remembered so /f info page <n> works without repeating the faction name after an initial /f info [faction].
• New messages in messages.yml: info.details-hint, info.page-title, info.page-next, info.page-prev, info.invalid-page, info.page-no-context.

Changed

• Updated TeamsAPI dependency from 2.0.0 to 2.1.0.
• Bumped plugin version to 1.1.3.
• TeamsAPI relation adapter now honors TeamRelation nature metadata (RelationNature) when persisting relation changes, so friendly/hostile custom relation natures map safely to internal declared relations.

Fixed

• TeamsAPI relation adapter now honors RelationNature metadata (TeamsAPI 2.1.0+): custom relation natures (FRIENDLY / HOSTILE) on non-standard TeamRelation values are mapped to the correct internal ALLY / ENEMY relation instead of always falling back to NEUTRAL.

Added

• Faction MOTD (/f motd): officers and above can set a message of the day for their faction. The MOTD is displayed in chat when a member logs in. Use /f motd clear to remove it.
• Configurable member-size cap: a new max-members setting in config.yml limits how many players can belong to a faction (0 = unlimited). The cap is enforced in /f join and in the join service. Default is 0 (no limit).
• Warp passwords (/f warp password <name> [password | clear]): officers and above can protect a faction warp with a password. Players must supply the correct password as a second argument (/f warp <name> <password>) to teleport. Passwords are stored as plain text in the warps table — avoid using important credentials.
• Warp per-use cost (/f warp cost <name> <amount>): officers and above can require a Vault economy payment each time a warp is used. Setting the cost to 0 makes the warp free. The charge is deducted via Vault before teleporting; if Vault is absent or the player has insufficient funds the teleport is blocked.
• Database migration: the warps table gains two new nullable columns (password, use_cost) when the plugin starts on an existing installation. No data is lost during upgrade from 1.1.1.
• Dynmap startup smoke test (.github/workflows/dynmap-smoke.yml): downloads the latest dynmap plugin from Modrinth, starts a Paper server with both plugins, and asserts dynmap hooked - faction territory layer enabled. is logged. Runs on Paper 1.21.4 and 1.21.11 on every PR to main/develop.

Changed

• Dependency upgrades (maintenance): all outdated compile and test dependencies bumped to their latest compatible versions:
  • EssentialsX 2.21.0 → 2.21.2
  • worldedit-bukkit 7.3.9 → 7.4.3
  • worldguard-bukkit 7.0.12 → 7.0.16
  • placeholderapi 2.11.6 → 2.12.2 (repo URL updated to repo.helpch.at)
  • mysql-connector-j 9.1.0 → 9.7.0
  • h2 2.3.232 → 2.4.240
  • HikariCP 6.2.1 → 7.0.2
  • junit-jupiter 5.11.4 → 5.14.4
  • mockito-core / mockito-junit-jupiter 5.14.2 → 5.23.0
  • maven-shade-plugin 3.6.0 → 3.6.2
  • asm / asm-commons override 9.8 → 9.10
  • jacoco-maven-plugin 0.8.12 → 0.8.14
  • maven-surefire-plugin 3.5.2 → 3.5.5

Fixed

• dynmap compatibility expanded to 3.x (3.4 – 3.8): the vendored compile-time dynmap-api dependency was upgraded from 3.4-beta-3 to 3.8 (latest stable, released 2026-01-14). In dynmap 3.8 the marker API was split into a separate DynmapCoreAPI JAR; both JARs are now vendored under libs/ with minimal POMs so CI never contacts repo.mikeprimm.com. The runtime hook code only uses stable org.dynmap marker APIs that are present in every 3.x release, so the plugin continues to work with any installed dynmap 3.x version.