Tags
Creators
Details
All versions
0.9.5-6992e40
Alpha
VelocityPteroPower Alpha • 6992e40last year 28
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
Platform
Velocity
Changes
⚠️ Alpha build for branch: dev
This build is generated automatically on every commit and may be unstable or untested. Need help? Join the Discord: https://discord.pluginz.dev
What's in testing (commits in this push)
- 9186576 update formatting Took 7 minutes (TubYoub)
- 8377990 update formatting Took 4 minutes (TubYoub)
- 69ac46f update formatting Took 3 minutes (TubYoub)
- 98fd099 Merge pull request #22 from Tubs-Pluginz/workflow-test Workflows (TubYoub)
- 0aa1f08 Player connect to the server they started Took 32 minutes (TubYoub)
- 51ecd45 usage message fixed to have the correct placeholder Took 2 minutes (TubYoub)
- 236287c Merge remote-tracking branch 'GitHub/0.9.5' into 0.9.5 (TubYoub)
- 3865879 feat: more metrics for bstats ### Features - Added
recordServerStartSignalSentmethod to track the total number of server start signals sent. - Implemented bStats custom charts to monitor server metrics like managed servers, total starts since boot, and panel types. ### Improvements - EnhancedcompareVersionsto sanitize pre-release and build metadata in version strings. - Introduced helper methods (sanitizeVersion,safeParseInt) for cleaner and safer version handling. - Optimized proxy shutdown process by including normalization and cleanup of the server list configuration. - Updatedconfig.ymlwith clearer documentation for theshutdownOnProxyExitsetting. ### Fixes - Resolved potential issues in handling malformed or null version strings in version comparison logic. Took 40 minutes (TubYoub) - 4b444cd feat: configurable limbo and forced-host behavior ### Features - Introduced
sendToLimboOnStartconfiguration option to enable sending players to a limbo server when their target server is starting. - AddedforcedHostOfflineBehaviorconfiguration with options (DISCONNECT,LOBBY_OR_LIMBO,LIMBO_ONLY) for managing forced-host joins when the target server is offline. ### Improvements - Enhanced logic to redirect players to holding servers (lobby or limbo) during server start scenarios, avoiding unnecessary disconnections. - Optimized connection flow to prevent redundant actions for players already connected to a limbo or lobby. ### Fixes - Correctly handle forced-host join failures by logging errors and falling back to default behavior when no valid holding servers are available. - Fixed potential issues with players being redirected or disconnected incorrectly during auto-connect routines. Took 46 minutes (TubYoub) - c3fb5d6 fix: limbo redirection for player connections Took 12 minutes (TubYoub)
- 9796795 chor: added missing permissions and commands to README.md Took 19 minutes (TubYoub)
- 983b0ba fix: weird behaviour when the CommandCooldown is set to 0 now it will just be ignored Took 11 minutes (TubYoub)
- 3cc562a chor: eddited comments to include the new Peli key prefix Took 3 minutes (TubYoub)
- 48a3ae5 feat: If a player moves to a limbo server there is record of why and also a sweep to clear limbos if a player gets stuck. iF a player moved there by himself or got moved they will be ignored Took 21 minutes (TubYoub)
- 04ab066 feat: Server history for players Took 28 minutes (TubYoub)
- ee804e9 bug: Had the wrong variable the whole time so commandCooldown just always defaulted to 10 seconds Took 21 minutes (TubYoub)
- 3e4b427 bug: Fix player staying in limbo on first connect Took 6 minutes (TubYoub)
- d5b9a0b feat: added autoscalling for apithreads to support servers using larger amounts of servers Took 50 minutes (TubYoub)
- aa9a851 Merge branch 'dev' into 0.9.5 (TubYoub)
- 6992e40 Merge pull request #24 from Tubs-Pluginz/0.9.5 Version 0.9.5 (TubYoub)
Links
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:1dDr5J4w:HlbMMBRW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1dDr5J4w:HlbMMBRW"
}

