
Dynamically alter player prefixes and TAB weights based on who is looking at whom.
A powerful, high-performance Spigot plugin designed for multi-proxy networks and partnered Minecraft servers. CrossNetworkPrefixer allows you to dynamically alter player prefixes and TAB-list sorting weights based on who is looking at whom. Perfect for server networks that share chat or TAB lists across different proxy clusters (via Velocity or BungeeCord) but want to maintain clear, localized staff hierarchy and visibility.
Display completely different prefixes and sorting weights depending on the viewing player's origin network.
Dynamically adjust TAB weights to ensure local staff members are always sorted at the very top of their respective network's TAB list.
Seamlessly integrates with the LuckPerms Meta-Data API to instantly determine a player's origin network and real group inheritance.
Fully implements standard and relational placeholders for complete compatibility with advanced TAB and Chat formatters.
Evaluates group inheritance directly from LuckPerms API layers, preventing standard Minecraft Operator (/op) permissions from breaking group sorting order.
The plugin registers the crossnetworkprefixer identifier.
| Placeholder | Description |
|---|---|
%crossnetworkprefixer_prefix% |
Returns the formatted prefix for the player themselves. |
%crossnetworkprefixer_weight% |
Returns the weight value for sorting. |
%rel_crossnetworkprefixer_rel_prefix% |
Recommended for TAB/Chat. Shows the target's prefix adjusted to the viewer's network profile. |
%rel_crossnetworkprefixer_rel_weight% |
Relational sorting weight based on the viewer's network profile. |
# =========================================================================
# CROSSNETWORKPREFIXER CONFIGURATION
# =========================================================================
# The LuckPerms meta-key used to identify which network/server the player is from.
# Example: If a player has the meta "from=network_one", the plugin loads that profile.
meta-key: "from"
# Default network profile used if a player doesn't have the meta key
# or if their network profile is not defined below.
# Set to "none" to completely disable prefixes for unknown networks.
fallback-network: "none"
# =========================================================================
# Network Profiles (Configure your networks here)
# =========================================================================
networks:
# -------------------------------------------------------------------------
# EXAMPLE PROFILE A: network_one
# -------------------------------------------------------------------------
network_one:
priority:
- "admin_network_one"
- "mod_network_one"
- "admin_network_two"
- "vip"
- "default"
admin_network_one:
prefix: "&4&lADMIN &8» &c"
weight: "1000"
mod_network_one:
prefix: "&c&lMOD &8» &c"
weight: "900"
admin_network_two:
prefix: "&d&lPARTNER &8» &d"
weight: "500"
vip:
prefix: "&a&lVIP &r"
weight: "100"
default:
prefix: "&7"
weight: "1"
# -------------------------------------------------------------------------
# EXAMPLE PROFILE B: network_two
# -------------------------------------------------------------------------
network_two:
priority:
- "admin_network_two"
- "admin_network_one"
- "vip"
- "default"
admin_network_two:
prefix: "&2&lADMIN &8» &a"
weight: "1000"
admin_network_one:
prefix: "&5&lPARTNER &8» &d"
weight: "500"
vip:
prefix: "&a&lVIP &r"
weight: "100"
default:
prefix: "&7"
weight: "1"
Let's assume Admin One controls Network One and Admin Two controls Network Two.
With a normal chat plugin, both players might simply appear as:
[ADMIN] Admin One
[ADMIN] Admin Two
This provides no distinction between local and partner staff.
Admin One appears as &4&lADMIN
Weight: 1000
Sorted at the very top
Admin Two appears as &d&lPARTNER
Weight: 500
Sorted below local staff
Admin Two appears as &2&lADMIN
Weight: 1000
Sorted at the very top
Admin One appears as &5&lPARTNER
Weight: 500
Sorted below local staff
This ensures staff members maintain localized ranking authority and prominent visibility on their home instances while partner-network staff are clearly identified as guests.
✅ Perfect for partnered Minecraft networks
✅ Lightweight and optimized
✅ No external database required
✅ LuckPerms-powered architecture
✅ Viewer-dependent prefixes
✅ Viewer-dependent TAB sorting
✅ PlaceholderAPI compatible
✅ Supports complex network structures
plugins/ folder.config.yml.CrossNetworkPrefixer is actively maintained and optimized.
Feature suggestions, bug reports, and contributions are always welcome.
Thank you for using CrossNetworkPrefixer ❤️