Tags
Creators
Details
0.9.4
Compatibility
Changes
VelocityPteroPower Update: Whitelists, McSS Support, and Major Improvements!
This version of VelocityPteroPower brings, expanded panel support, and a host of under-the-hood improvements for better performance and stability.
Highlights of this Release:
New Features
- Server Whitelist Management:
- Dynamically fetch, parse, and enforce server whitelists directly from your panel.
- Manually reload whitelists with the
/ptero whitelistReloadcommand. - Configure whitelist settings per-server in your
config.yml.
- Mc Server Soft Panel Support:
- VelocityPteroPower now supports Mc Server Soft panels alongside Pterodactyl and Pelican!
- Includes appropriate API handling (note: whitelist file fetching is not supported by McSS).
Key Improvements
- Major Code Refactor: Significant parts of the plugin have been rewritten to be more modular, reliable, and easier to maintain. This means a more stable experience for you.
- Enhanced Connection & Server Management:
- Improved logic for handling player connections and server switches.
- More robust server lifecycle management for starting and stopping servers.
- Smarter handling for players attempting to connect to offline servers, redirecting to a limbo server if available.
- Improved API Key Handling: More reliable API key validation across all supported panel types.
- Clearer Logging: Logging has been improved for better diagnostics and clearer information.
Important Fixes
- Resolved issues with API key validation occurring at the wrong time.
- Addressed several log redundancies and optimized instance creation.
- Fixed issues related to API rate limit processing.
- Ensured more consistent whitelist enforcement.
As always, please back up your configuration files before updating.
Thank you for using VelocityPteroPower!
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:TMNnazMd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1dDr5J4w:TMNnazMd"
}

