
LegacyVelocity Forwarding
LegacyVelocity: Velocity modern forwarding for Spigot/Paper 1.8.8 What it does LegacyVelocity lets a Spigot or Paper 1.8.8 server accept Velocity’s modern player-info forwarding. Velocity normally needs a 1.13+ backend for this. The plugin implements the
Tags
Creators
Details
2.0.0
Compatibility
Changes
LegacyVelocity 2.0.0
Added
/lv command showing the plugin version and status: a bold green RUNNING! when active, or a bold red NOT RUNNING with the reason. /lv reload to reload the config and start forwarding without a restart. Permission legacyvelocity.admin (default: ops) for the commands and warnings. Warning to admins on join, in bold red, if no forwarding key is set, online-mode is true, or the plugin couldn’t hook the server. Detailed debug logging of every login step, including the forwarding request, the proxy’s reply and any kicks.
Changed
Renamed from VelocityForwarding18 to LegacyVelocity. The config is reorganized into forwarding, messages and debug sections, with setup notes as comments. The secret is now empty by default. The plugin no longer disables itself when no key is set. It stays loaded, warns the console and admins, and does not block logins until you configure the key. Works with ViaVersion on the 1.8.8 server: packets bypass ViaVersion’s handlers and are written with correct length prefixes.
Fixed
Forwarding packets were sent without the length prefix, so Velocity couldn’t read them. ViaVersion on the server could translate and drop Velocity’s reply. A removed secret after /lv reload now kicks players instead of causing an error.
Upgrading from 1.0.0
Copy your secret into forwarding.secret in the new plugins/LegacyVelocity/config.yml, because the config layout changed.
Known issues
ViaVersion on the Velocity proxy blocks forwarding to 1.8 servers. Use it on the 1.8.8 server instead. On Java 9 or newer, set use-native-transport=false in server.properties. Beta: not yet confirmed end to end.
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:s4zpjgt8:5opj3BA8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s4zpjgt8:5opj3BA8"
}
