Tags
Creators
Details
1.1.0
Compatibility
Changes
VelocityLimboHandler v1.1.0 - Connection Error Handling Improvements
Overview
This update enhances the player experience by significantly improving how connection errors are handled. Players who are banned or not whitelisted on destination servers now remain in limbo with appropriate notifications rather than being disconnected.
New Features
- Players now receive clear, color-coded notifications when they cannot connect to a server due to bans or whitelist restrictions
- Added persistent tracking of player connection issues (banned/not whitelisted)
- Improved queue system to properly skip players with connection issues
Bug Fixes
- Fixed issue where banned players were kicked from the proxy entirely
- Fixed queue system becoming blocked when a player with connection issues was at the front of the queue
- Fixed error message detection to properly identify ban and whitelist messages
Technical Improvements
- Enhanced error detection by checking both exception messages and server response components
- Improved connection failure handling with proper categorization of error types
- Made connection issue notifications independent of queue status
Configuration
- Added "queue-enabled" to toggle if the queue should be enabled, or just use random selection from players (Only recommended for small servers to keep it fair)
This release focuses on creating a more stable experience for players during server maintenance and restarts while preventing unnecessary disconnections.
Full Changelog: https://github.com/AkselGlyholt/velocity-limbo-handler/compare/v1.0.1...v1.1.0
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:Sl8k2Ndp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xPIxOI5h:Sl8k2Ndp"
}

