Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 2 years ago
Updated 2 years ago
All versions
2.2.0
Release
vLobbyConnect 2.2.02 years ago 1,152
Compatibility
Minecraft: Java Edition
1.21–1.21.5
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
Platform
Velocity
Changes
New Features
- Added
/vlobbyconnect reloadcommand to reload configuration - Added permission system with
vlobbyconnect.admin.reloadpermission - Added configurable messages with color code support
Improvements
- Added embedded default messages for improved reliability
- Added version placeholder support in "no lobbies" message
- Added fallback system for configuration loading
- Added detailed error reporting for configuration issues
Bug Fixes
- Fixed message handling when config.yml is missing or invalid
- Fixed reload command not working with invalid config
- Fixed potential NPE during configuration loading
- Fixed resource handling in plugin build process
Configuration Changes
- Added new messages section in config.yml
- Added new permissions section in config.yml
- Added support for customizable error messages
- All messages now support color codes with '&' symbol
Technical Updates
- Version updated from 2.1.0 to 2.2.0
- Improved error handling throughout the plugin
- Enhanced logging for configuration operations
- Optimized resource loading process
Notes for Server Admins
- Existing config.yml files will continue to work
- New messages can be added to config.yml to override defaults
- No server restart required for config changes
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:JKzrCTaM:cw8UUwmo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JKzrCTaM:cw8UUwmo"
}

