Links
Tags
Creators
Details
All versions
1.4.0
Beta
PlayerRelay 1.4.0last year 38
Compatibility
Minecraft: Java Edition
1.21.6–1.21.8
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
⚠️ Warning
This version is incompatible with versions 1.3.0 and below.
New Features
- Player list
- Added player model rendering
- Added dimension icons
- Added player status overlay (AFK and death)
- Added
echestcommand:- View another player's ender chest
- Player must have opened their ender chest at least once in the current world
- Lets you view your own ender chest if a player isn't specified
- Ender chest inventory updates when you re-run the command
- Added custom player name colors
- Colors also apply to pings from Ping Wheel
- Added Xaero's Minimap / WorldMap waypoint sharing via Player Relay
- New config options:
- Client
- Display Name Color (default:
#FFFFFF) - AFK Timeout (default:
120'000ms)
- Display Name Color (default:
- Player List
- Show Dimension Icon (default:
ON) - Player Icon Type (default:
PLAYER_MODEL, previouslyPLAYER_HEAD)
- Show Dimension Icon (default:
- Xaero's Minimap / WorldMap
- Share Waypoints Via Player Relay (default:
ONpreviouslyOFF)
- Share Waypoints Via Player Relay (default:
- Client
Changes & Fixes
- Support Ping Wheel 1.12.0
- Older Ping Wheel versions are now incompatible
- Renamed
peekinvcommand toinv - Fixed config not saving color types correctly
- Fixed player name and UUID being unknown until a world is loaded
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| player-relay-1.4.0-sources.jar | Unknown | 98.73 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:4vsSeMij:ZjT8dfIG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4vsSeMij:ZjT8dfIG"
}

