Links
Tags
Creators
Details
1.0.0
Compatibility
Changes
Restartify v1.0.0 Beta — Test release
Restartify provides reliable server restarts by implementing a customizable countdown system. The plugin eliminates abrupt disconnections by broadcasting scheduled chat announcements and displaying an on-screen BossBar. Once the countdown concludes, it executes the restart using the server core's native method.
Key Features
- Dynamic BossBar Countdown — A live progress bar that smoothly tracking the remaining time. Supports configuration of colors (PINK, BLUE, RED, GREEN, YELLOW, PURPLE, WHITE) and styles (SOLID, NOTCHED_6/10/12/20). Players joining mid-countdown will see the active BossBar automatically.
- Scheduled Chat Alerts — Flexible notification modes including fixed intervals every N seconds (INTERVAL), exact custom timings such as 60/30/15/10/5/4/3/2/1 seconds (SCHEDULE), or completely silent operation (OFF).
- Hybrid Text Formatting — Comprehensive support for both MiniMessage and legacy formats simultaneously. Developers and admins can combine advanced tags (<red>, <bold>, gradient:#ff0000:#0000ff) and classic color codes (&c, &l, &#RRGGBB) within a single line.
- Administrative Logging — When a restart is initiated, all server operators receive a notification specifying the initiator (player name or Console).
- Real-Time Control Commands — The /reboot cancel command immediately stops the active countdown and removes the BossBar from all clients. The /reboot reload command hot-reloads the configuration file without disrupting any running timers.
- Zero Dependencies — Built directly on top of the Adventure API, which natively ships with Paper, eliminating the need for external libraries.
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:48nfEoGR:IVe6dDRH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:48nfEoGR:IVe6dDRH"
}

