Tags
Creators
Details
1.1.1
Compatibility
Changes
CreeperCLI v1.1.1
This patch restores the CLI launcher's Node shebang so commands installed through npm launch correctly on Windows, macOS, and Linux. CI and release checks now install the packed CLI and run the generated command. Users of CLI 1.1.0 should upgrade to 1.1.1.
The release also includes the server and proxy improvements introduced in 1.1.0.
Manage Paper/Spigot servers and BungeeCord/Waterfall or Velocity proxies from your terminal.
Install or update
- Plugin: requires Java 21. Download
CreeperCLI-1.1.1.jar, replace the existing jar inplugins/, and restart your server or proxy. - CLI: run
npm install -g creepercli@1.1.1.
The plugin binds to 127.0.0.1 by default. For remote access, use an SSH tunnel, VPN, or trusted private network. See the security documentation.
Added
- BungeeCord/Waterfall and Velocity support.
- Authentication deadlines and bounded outbound queues.
- Expanded regression coverage for authentication, transfers, sync paths, plugin loading, monitoring, and filesystem operations.
Changed
- Plugin now requires Java 21 and targets Paper/Spigot 1.21+.
- New configurations bind to
127.0.0.1by default. - Removing or replacing accounts revokes their live sessions. Password changes revoke other sessions.
- Release workflows verify builds, package versions, tests, and CLI package contents before publishing.
Fixed
- Incorrect Paper/Spigot plugin entry point.
csynchandling of.,..,~, and relative paths aftercd.- Missing local parent directories during downloads.
- Slow partial requests bypassing the authentication deadline.
exit,quit, andqleaving the REPL running.- CLI updater querying the wrong npm package.
- Upload temporary-file collisions, checksum validation, unauthorized transfer aborts, and abandoned transfers.
- Authentication limiter cleanup and successful-login throttling.
- Tick-time calculations and trailing-newline handling in
tail. - Invalid configuration recovery now backs up the original file.
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:fPKEvBZo:BzmYGYo4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fPKEvBZo:BzmYGYo4"
}

