
Shared Player Data
Server-only shared vanilla player profile data for bound UUID groups.
About this Mod
Languages
Shared Player Data
A server-side Fabric mod that allows selected online players to share the same persistent player profile data through explicit administrator binding.
Overview
Shared Player Data lets server administrators bind players together so that they use a shared player data profile.
After players are bound, they share the same persistent gameplay state, including vanilla player data such as inventory, position, experience, health, statistics, advancements, and related saved profile data.
Only one player from the same bound group may be online at the same time. If another player from the same group attempts to join while the shared profile is already in use, the join is rejected with the vanilla duplicate-login message.
Key Features
- Bind two online players with a simple command
- Bound players share the same persistent player profile
- Only one player from the same bound group can be online at once
- Uses the vanilla duplicate-login disconnect message when a bound profile is already in use
- Supports online-player name suggestions for commands
- Automatically saves binding configuration
- Synchronizes operator status within bound groups
- Designed for dedicated servers
- No client-side installation required
Commands
/playerbind <name1> <name2>
Behavior
- Both players must be online
<name1>remains online<name2>is bound to the same shared profile group and then disconnected- The command requires level 4 permission
- The command can be used by level 4 operators, the server console, and RCON
Restrictions
- The first and second player cannot be the same player
- A player cannot bind themselves as the second target
Operator Synchronization
When players are in the same bound group, their operator status is synchronized.
If one member of the group is granted operator status, the other known members of the group will also receive operator status.
If one member of the group is removed from the operator list, the other known members of the group will also be removed from the operator list.
Multiplayer Behavior
- Bound players share one persistent gameplay profile
- Only one bound player may use the shared profile at a time
- Other players in the same bound group receive the vanilla duplicate-login disconnect message while the profile is in use
- Players outside the bound group are unaffected
Server Safety
- Server-side only
- Dedicated-server focused
- No client mod required
- Does not require players to install anything
- Does not change player authentication identity
- Keeps real player accounts separate while sharing bound gameplay data
- Prevents simultaneous access to the same shared profile
Configuration
The mod stores its configuration in:
config/shared-player-data.json
Bindings created through commands are saved automatically.
Manual configuration edits should be made while the server is stopped.
Supported Versions
- Minecraft 26.1.2
- Fabric Loader 0.19.2+
- Fabric API 0.150.0+
- Java 25
License
MIT
Available Versions
How to Install Shared Player Data on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (26.1.2).
Install Mod
Open the mod browser in the dashboard and search for "Shared Player Data". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
26.1.2
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Shared Player Data server crashes on startup – what to do?
Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (26.1.2). You can switch loaders with one click in the panel.
Is Shared Player Data compatible with fabric?
Shared Player Data officially supports fabric for Minecraft 26.1.2. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Shared Player Data – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Shared Player Data consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Shared Player Data with just one click on your server.