Tags
Creators
Details
1.7.0
Compatibility
Changes
๐ VelocityLimboHandler v1.7.0
โ ๏ธ Important: Configuration Migration
If you are updating from v1.6.2 or lower, your task-interval unit has changed.
- Old behavior: Seconds (e.g.,
3) - New behavior: Milliseconds (e.g.,
3000) - Action Required: Please update your
config.ymlto reflect this change, otherwise, the plugin will attempt to reconnect players far too fast!
๐ ๏ธ Performance & Stability
This update brings major internal improvements to ensure the proxy remains responsive even under heavy load.
- Non-Blocking Reconnections: All server pings and connection requests are now handled asynchronously. This prevents "Proxy Hangs" if a backend server is slow or timing out.
- Full Server Protection: Added a "Pre-flight" check. The plugin now pings the target server and checks player capacity before attempting a connection. This eliminates the "Server is full" console spam and reduces network overhead.
- Memory Management: Fixed several memory leaks where disconnected players were remaining in internal tracking maps.
โจ New Features & Fixes
- New Integration: Added support for LibreLoginNext in the AuthManager.
- Queue Logic: Fixed a bug where players could sometimes "skip" the queue under specific timing conditions.
- Smart Rerouting: Improved the connection listener to detect "Intentional" reconnections, preventing players from getting stuck in a loop between Limbo and the Lobby.
๐ฆ Pull Requests
- Added LibreLoginNext support (#41)
- Unit migration: task-interval to milliseconds (#42)
- Core: Async implementation and leak fixes (#43)
- Fix: Logic to handle full backend servers (#44)
- Bugfix: Resolved queue skipping issues (#45)
Full Changelog: https://github.com/AkselGlyholt/velocity-limbo-handler/compare/v1.6.2...v1.6.3
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:xPIxOI5h:LFnNbNFH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xPIxOI5h:LFnNbNFH"
}

