Tags
Creators
Details
Licensed CC-BY-NC-4.0
Published last month
Updated 2 weeks ago
All versions
0.2.1+26.1.2
Release
Relay 0.2.1+26.1.23 months ago 7
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
Client and Server
- added health sharing
- added more notifications when client fails to connect to relay service
- moved any mod integrations to integrations tab in config
- added pings (similar to that of fortnite)
- added table hud alignment option
- worldmap icon is now visible at all times
- fixed worldmap icon glitching when user was hovering over the icon of a player that was moving
- renamed the two columns in the trust list
- fixed armor durability sharing being off by default
- fixed RateLimiter triggering when changing servers in a network
- added /available command to see teammates that are online and can receive your alerts
- added multiple new options to view armor durability
- fixed invert list not working
- increased cooldown duration scaling in the config for alerts
- fixed muting someone muting your alerts to them also
- added the ability to share waypoints from xareos worldmap to teammates
- added team chat system for mute players
- improved the naming of ips on the alert toast
- changed the default send alert keybind to unset
- changed the remove trust keybind to now toggle trust for the targeted player
- moved the relay server option to an advanced section in the config
- named are now colored by ping color in the hud
Server Only
- improved routing efficiency with higher player counts
- implemented a stats system collecting non identifying data about players connected to the network (simply the counts of players online and unqiue players connected)
- added support for older protocol versions to connect to the service
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:kMxsmTLv:CCR11p9k"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kMxsmTLv:CCR11p9k"
}

