Tags
Creators
Details
2.0.0-b4
Compatibility
Changes
-
Added Velocity support
-
Added velocity checks for modern forwarding
-
Updated the update checker to be more robust
-
Fixed some data leaks related to looking up UUIDs
-
Removed symbolic links for Velocity
-
Fixed configs saving to file when unneeded to
-
Added custom color translation to Utils for Velocity
-
Added getPluginVersion to Bungie and Velocity Api
-
Fixed heartbeat command not being sent to wrapper causing connection resets
-
Removed MOTDs in Velocity(Velocity does not natively support server motds)
-
Replaced data packets with Base64 encoding to speed up server syncing
-
Added Hastebin paste to debug dump for easier log sharing ( /psa debug toggle | /psa debug | /psa debug toggle )
-
Fixed running servers not being re-added to proxy after restart
-
Fixed PlayerServers not reconnecting to wrapper on connection reset
-
Added getController to Bungee and Velocity api ( might be removed if its not useful )
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:l6pSCvax:kzQlHUZa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l6pSCvax:kzQlHUZa"
}
