Compatibility
Minecraft: Java Edition
Platforms
Creators
Details
PvPIndex Factions is a long-term modernization of the classic Factions experience for modern Paper servers.
The goal is simple: revive Factions with a timeless architecture, reliable persistence, clean gameplay UX, and API-connectable systems that can integrate with modern server ecosystems for years to come.
If you love classic Factions gameplay but need something maintainable, scalable, and integration-ready, PvPIndex Factions is built for exactly that.
TeamsAPI integration available - PvPIndex Factions connects natively with TeamsAPI to expose faction data to other compatible plugins and services. Requires TeamsAPI 2.0.0+. Download TeamsAPI on Modrinth →
Supported platforms
| Platform | Version | Notes |
|---|---|---|
| Paper | 1.21.x, 1.26.x | Recommended |
| Folia | 1.21.x, 1.26.x | Native Folia scheduler support |
| Spigot | 1.21.x, 1.26.x | Legacy compatibility mode |
| Java | 21+ |
Vision: timeless Factions, modern backend
PvPIndex Factions is not a quick port. It is an active refactor effort to make Factions:
- Easier to operate in production
- Easier to integrate with APIs and external systems
- Easier to maintain across future Minecraft/Paper updates
- More consistent for players and staff
This project keeps the recognizable Factions identity while replacing legacy internals with a modern service/repository model and optional integration adapters.
What is modernized vs legacy Factions
Compared to older Factions-era plugins, PvPIndex Factions focuses on:
- Modern command ergonomics and guided help UX
- Persistent invite lifecycle with login notifications
- Better map readability and interaction flow
- More complete claim/unclaim modes
- Configurable GUI-driven navigation
- Optional tax/economy control for faction banks
- Cleaner permissions and admin workflows
- Soft-dependency integrations that fail gracefully
- Documentation and operational runbooks for real server owners
You keep the Factions gameplay loop, but gain a modern operational foundation.
Why server owners choose PvPIndex Factions
- Modernized
/fcommand experience with familiar muscle memory - Persistent faction invites with login-time invite notifications
- Advanced land control:
claim/unclaimmodes (one,square,circle,fill,auto) - Interactive
/f mapwith clearer territory context - Faction bank with deposit/withdraw/transfer/history and optional tax engine
- Configurable
/fGUI viagui.yml - Scales from standalone setup to larger integrated networks
Feature overview
Faction lifecycle
- Create, rename, describe, and disband factions
- Member administration with invite/revoke/accept/decline flows
- Leadership transfer and rank movement (promote/demote)
- Clear onboarding through
/f help
Land and map
- Claim/unclaim behavior designed for both casual and advanced use
square,circle, andfillmodes for territory management- Auto claim/unclaim modes for movement-driven workflows
- Modernized
/f mapdisplay and improved territorial context messaging
Economy and bank
- Faction bank deposit, withdraw, transfer, and history
- Optional periodic tax engine with configurable rates/intervals
- Works with Vault-based economy stacks
Homes and warps
- Faction home and warp management
- Warp listing/set/delete flows
- Compatibility-oriented command structure for player familiarity
Faction flags
- Per-faction boolean toggles:
pvp,friendly-fire,explosions,fire-spread,open - Officers manage flags in-game with
/f flag set; defaults and editability configurable per-flag - Admins override any flag via
/fa flagregardless of the player-editable setting
Audit log
- Officers and above can page through their faction's action history with
/f audit [page] [--action=<action>] - Staff can view any faction's history with
/fa audit <faction> [page] [--action=<action>] - Tracks claims, unclaims, relation changes, kicks, promotions, demotions, bank transactions, and merge events
- Page size configurable via
factions.audit.page-sizeinconfig.yml
Faction merges
/f merge send <faction>— officers can propose dissolving their faction into another/f merge accept <faction>— officers of the target faction accept the request- All claims, warps, bank balance, and members are transferred atomically; the sender faction is then disbanded
- Online target members are notified immediately when a request arrives
Internationalization
- Eight built-in locale bundles:
en,es,de,fr,pt-BR,ja,zh,ru - Players choose their language with
/f language [code|reset] - Server default locale configurable via
factions.language.defaultinconfig.yml - All command output, GUI item text, and map display respect the resolved locale
- Message lookup order: player locale → server default → English → inline fallback
- Community locale contributions welcomed — see the i18n guide
Power and war mechanics
- Configurable power model with per-player max, regen rate, loss on death, and grace period
- Optional kill power rewards, with configurable flat or scaled amounts (scale rewards by victim/killer power ratio)
- Optional death streak multiplier — consecutive deaths in a short window incur escalating loss
- Optional inactive member exclusion — long-offline members do not count toward max-land
- Overclaiming with enemy-relation guard and optional offline protection (block raids when all defenders are offline)
- Raidable state broadcast — members (and optionally the server) are notified when a faction crosses the raidable threshold
- War shield system — admins assign a daily UTC protection window; during the window territory cannot be overclaimed
/f powerhistory— paginated per-player power change log (alias:/f phist); shows death, kill, and passive-regen events
Notifications and QoL
- Invite visibility for online and returning players
- Territory and event notifications
- Player-level notification controls
API and integration direction
PvPIndex’s long-term direction is an API-connectable Factions core.
That means systems are designed to be:
- Adapter-friendly
- Service-oriented
- Compatible with external plugins/services without hard coupling
- Reliable even when optional integrations are absent
This creates a stable base for future extensions, panels, tooling, and ecosystem plugins.
Integrations
PvPIndex Factions runs standalone, and integrates when available:
- Vault (economy API)
- PlaceholderAPI
- TeamsAPI
- WorldGuard / WorldEdit
- dynmap (3.x, tested 3.4 – 3.8)
- EssentialsX
- LWC / LWCX
- EzAuction (faction auctions)
- EzShops (faction shops)
- EzRTP (avoids faction claims)
- EzClean (avoids faction claims)
- DiscordSRV (faction event broadcasts to Discord)
Integration downloads
- PlaceholderAPI: https://modrinth.com/plugin/placeholderapi
- WorldEdit: https://modrinth.com/plugin/worldedit
- WorldGuard: https://modrinth.com/plugin/worldguard
- dynmap: https://modrinth.com/plugin/dynmap
- EssentialsX: https://modrinth.com/plugin/essentialsx
- LWC: https://modrinth.com/plugin/lwc
- Vault API: https://www.spigotmc.org/resources/vault.34315/ (official dependency page)
- TeamsAPI: https://modrinth.com/plugin/teams-api
- EzAuction: https://modrinth.com/plugin/ezauction
- EzShops: https://modrinth.com/plugin/ezshops
- EzRTP: https://modrinth.com/plugin/ezplugins-ezrtp
- EzClean: https://modrinth.com/plugin/ezclean
- DiscordSRV: https://modrinth.com/plugin/discordsrv
Configuration and operations
Generated config files:
config.ymldatabase.ymlmessages.ymlgui.yml
Storage options:
- Embedded H2 for quick setup
- MySQL/MariaDB for larger networks
Docs include:
- Installation and setup guides
- Full config reference
- Feature-by-feature documentation
- Integrations setup notes
- Operations runbook and troubleshooting
Visual preview
GUI:

Map:

Faction info:

Faction info page 2:

Top tab-complete:

Faction Flags:

Set flag state:

Flag autocomplete:

Audit log:

Admin power history:

Commands at a glance
- Player root:
/f(/faction,/factions) - Admin root:
/fa(/factionadmin) - Highlights:
/f create,/f invite,/f join,/f claim,/f unclaim,/f map,/f info,/f top,/f bank,/f warp,/f audit
Designed for migration-minded communities
If your server comes from legacy Factions communities, PvPIndex Factions is intentionally built to feel familiar while offering a cleaner and more future-proof base.
The objective is not to erase Factions identity; it is to preserve it and make it sustainable for modern server operations.
Documentation
For setup, configuration, operations, and troubleshooting:
- Docs: https://pvp-index.github.io/pvpindex-factions
- Getting started: https://pvp-index.github.io/pvpindex-factions/getting-started
- Installation: https://pvp-index.github.io/pvpindex-factions/installation
- Step-by-step guides: https://pvp-index.github.io/pvpindex-factions/guides
- Core configuration: https://pvp-index.github.io/pvpindex-factions/configuration/core-settings
- Full configuration reference: https://pvp-index.github.io/pvpindex-factions/configuration/reference
- Features overview: https://pvp-index.github.io/pvpindex-factions/features
- Integrations docs: https://pvp-index.github.io/pvpindex-factions/integrations
- Operations runbook: https://pvp-index.github.io/pvpindex-factions/operations/admin-runbook
- Troubleshooting: https://pvp-index.github.io/pvpindex-factions/operations/troubleshooting
- Commands reference: https://pvp-index.github.io/pvpindex-factions/commands
- Permissions reference: https://pvp-index.github.io/pvpindex-factions/permissions
- Source: https://github.com/PVP-Index/pvpindex-factions
- Issues: https://github.com/PVP-Index/pvpindex-factions/issues
License and attribution
- LGPL-3.0
- Derivative of MassiveCraft Factions (LGPL-3.0)
- Refactor by PvPIndex.com team (Shadow48402, Epildev)


