Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated 4 months ago
All versions
1.0.2
Alpha
Velocity - Auto Reconnect 1.0.26 months ago 210
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
1.7.x
Platform
Velocity
Changes
- Fixed built-in virtual holding reconnects failing on backend restart.
- Fixed players sometimes getting kicked instead of being held and reconnected.
- Fixed reconnect loops where the plugin kept trying forever even after the backend was back online.
- Fixed the reconnecting screen disappearing too early and ending in a timeout.
- Fixed heavy reconnect screen flickering and repeated visual reloads while waiting.
- Fixed stuck in-flight backend connections that could block reconnect completion.
- Fixed cases where players timed out while sitting in built-in holding by adding proper keepalive handling.
- Fixed ghost sessions where the proxy could think a player was still online after leaving during reconnecting/holding.
- Fixed “already connected to the proxy” / stuck session issues after failed reconnect attempts.
- Fixed cleanup of backend and in-flight connections when a player disconnects.
- Fixed shutdown handling so plugin tasks are cancelled properly when the proxy stops.
- Fixed the proxy shutdown warning about the plugin executor not closing in time.
- Fixed disabled mode so backend restarts use a normal clean disconnect instead of a broken connection reset style disconnect.
- Fixed reconnect completion handling to avoid false failure states after a successful reconnect.
- Improved reconnect finalization timing so players are sent back faster once the backend is actually ready.
- Improved built-in holding handoff logic for modern Velocity config/play switching.
- Improved compatibility with voice chat reconnect behavior so voice chat can reinitialize correctly after reconnecting.
Added /velocityreconnect enable Added /velocityreconnect disable Added /velocityreconnect status Added bStats support. Improved config readability and setting descriptions.
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:Ri89j7v5:THb9RdOC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ri89j7v5:THb9RdOC"
}

