Tags
Creators
Details
Licensed Apache-2.0
Published 3 months ago
Updated 4 days ago
All versions
1.4.1
Release
RedstoneReboot 1.4.12 months ago 9
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
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
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
v1.4.1 — Security & Stability
This release fixes all findings from an independent source code audit.
Security
- LocalScriptBackend: Shell-escape all startup command args for Linux and Windows — prevents command injection via
sun.java.command, JVM args, or env vars - LocalScriptBackend: Filter sensitive JVM args (
-Dpassword,-Dsecret,-Dtoken,-Dkey,-Ddb.*, etc.) from generated restart scripts — no more credential leakage to disk
Fixes
- Folia: Async scheduler methods now use
getAsyncScheduler()— blocking backend operations no longer freeze the server tick thread - RestartManager:
isRestartInProgress()now checks the backend execution guard — prevents race where a new restart could fire during an active backend call - Fabric: Title broadcasting now uses reflection to support both 1.20.1 and 1.20.2+ — no more crash on modern Fabric versions
- Pterodactyl: Server IDs are now URL-encoded — special characters in IDs no longer break API requests
- Bukkit TPS: Reflection handles are cached after first lookup — eliminates repeated
getMethod/getFieldcalls - Cleanup: Console logging added for reload-cancelled restarts
What to download
- Bukkit / Spigot / Paper / Purpur →
RedstoneReboot-Bukkit-1.4.1.jar - Folia →
RedstoneReboot-Folia-1.4.1.jar - Fabric →
RedstoneReboot-Fabric-1.4.1.jar - Forge →
RedstoneReboot-Forge-1.4.1.jar - NeoForge →
RedstoneReboot-NeoForge-1.4.1.jar
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:q1G1C28r:VhMuugvJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:q1G1C28r:VhMuugvJ"
}

