Tags
Creators
Details
0.9.3.1
Compatibility
Changes
VelocityPteroPower v0.9.3.1 - Release Notes
This release focuses on enhancing server management flexibility, configuration options, and overall stability within VelocityPteroPower.
✨ New Features
- Configurable Server Status Check Method:
- A new
serverStatusCheckMethodoption has been added toconfig.yml. - Choose between
VELOCITY_PING(uses Velocity's built-in ping) orPANEL_API(uses Pterodactyl/Pelican panel API for higher precision, mindful of API rate limits).
- A new
- Adjustable Logging Level:
- Control the plugin's log verbosity using the new
loggerLevelsetting inconfig.yml.
- Control the plugin's log verbosity using the new
- Customizable Initial Check Delay:
- The
startupInitialCheckDelayoption inconfig.ymlallows you to configure how long the plugin waits before the first server status check after startup.
- The
- Refined Limbo Server Handling:
- Improved logic for handling limbo servers, including dynamic checks to ensure they are usable before redirecting players.
- Enhanced Messages:
- Added new placeholders and messages to
messages.yml. - The
%limbo%placeholder can now be used in relevant messages. - New messages provide more detail during server startup and when encountering API rate limits.
- Added new placeholders and messages to
🚀 Improvements
- Updated Server Startup Flow:
- Players attempting to connect to a starting server will now be redirected to a configured limbo server (if available and usable).
- Added pre-checks for Pterodactyl API rate limits before attempting to start a server via the API.
- Enhanced Logging:
- Added detailed debug-level logging for server status checks and API interactions, aiding troubleshooting.
- Improved detection and logging of potential panel or server misconfigurations.
- Optimized Server Shutdown & Retries:
- Refined the server shutdown process and retry logic.
- Now considers API rate limits and whether a server is empty before attempting shutdown actions.
- Version Checker Update:
- De-duplicated critical update warnings.
- Merged
CRITICALandHIGHurgency levels for update notifications for clarity.
🐛 Bug Fixes
- Resolved an issue where players could be disconnected during target server startup if configured limbo servers were unavailable or unusable.
- Improved consistency in task handling and retries during the server shutdown sequence.
- Prevented unhandled exceptions during server status checks (both
PINGandAPI), ensuring graceful handling of rate limits and other unknown errors.
Issues: #10
Full Changelog: https://github.com/BT-Pluginz/VelocityPteroPower/compare/v0.9.2.4-alpha...v0.9.3.1
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:47Ingb5V"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1dDr5J4w:47Ingb5V"
}

