All versions
1.0.1
Release
vConnect 1.0.14 months ago 31
Uploaded by
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
Platform
Velocity
Changes
VConnect 1.0.1
This update improves fallback behavior and adds a new update checker.
Changes
- Fixed an issue where players were redirected to the lobby/Limbo when trying to connect to an offline or unavailable backend server.
- Players now stay on their current server if a manual server switch fails.
- Added a configurable Modrinth update checker.
- Added
/vconnect updateto manually check for updates. - Added update notifications for players/admins with the
vconnect.update.notifypermission. - Added new fallback config option:
fallback-on-connect-failure. - Added new update checker config section:
advanced.update-checker. - Added new configurable messages for update checks.
- Bumped version to
1.0.1.
New permission
vconnect.update.notify
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:MX7q8nd5:7YjNcOGR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MX7q8nd5:7YjNcOGR"
}

