RedstoneReboot

🔥 Why RedstoneReboot?

RedstoneReboot is a production-grade server lifecycle engine that provides precise control over when, why, and how your server restarts. Backed by real-time health monitoring, intelligent scheduling, and a pluggable backend handoff system.

From a single survival server to a fleet behind Pterodactyl — it delivers reliability, intelligence, and elegance.

Key Capabilities

• 🕐 Intelligent Scheduling — Multiple daily restart windows with global timezone support and day-of-week filters
• 📊 Health Monitoring — Real-time TPS and memory tracking with consecutive-check false-positive protection
• 🚑 Emergency Fail-safes — Automatic restart triggers on critical TPS or memory breach
• 🔔 Rich Alerts — Chat, title, action bar, and configurable sound notifications
• 🔌 Backend Handoff — Delegate to Pterodactyl, Systemd, Docker, or local wrapper scripts
• 🔄 Hot-Reload — Change backend config and /reboot reload — no full server restart needed
• 🧩 PlaceholderAPI — 8 placeholders for scoreboards, tab lists, and MOTD plugins (Bukkit builds)
• 📈 bStats Metrics — Anonymous usage telemetry (view live stats)

⚡ The Backend System & Startup Loops

RedstoneReboot divides "when to restart" from "how to restart" by supporting multiple backends:

• SHUTDOWN_ONLY — Graceful shutdown (letting your external wrapper restart the process)
• LOCALSCRIPT — Auto-generated shell script handles process restarts
• SYSTEMD — Service integration on Linux
• DOCKER — Container-native restart policies
• PTERODACTYL — Direct panel API integration

💡 Do I need to set up a custom backend?

If your server is already wrapped in a startup loop script (like a .sh or .bat file with a while true loop, a Docker container set to restart: always, or a systemd service), SHUTDOWN_ONLY works out of the box! When the restart timer runs out, the engine gracefully stops the server, and your script starts it back up automatically.

Why configure a custom backend then?

1. Intelligent Handoff (Pterodactyl / Panels): Avoid panel desyncs or false offline indicators. Instead of just shutting down, the plugin talks to your panel's API to request a clean power cycle.
2. Self-Healing Bootups: If you don't run a startup loop script, the LOCALSCRIPT backend spawns a new process to boot the server back up automatically.
3. Crash Lockout Safety: Simple loops can get stuck in infinite crash loops if a file gets corrupted. Custom backends implement safety lockout timers to prevent endless boot hammering.

📦 File Selection

Choose the file that matches your server platform:

🌍 Platform Compatibility

• Bukkit / Spigot / Paper / Purpur: 1.9.x to 1.21.x+
• Folia: 1.20.1+
• Fabric: 1.20.1+
• Forge: 1.20.4+
• NeoForge: 1.20.4+

📋 Supported Versions

⚙️ Installation

Plugin Install (Bukkit/Folia)

1. Download the correct plugin file.
2. Place it in plugins/.
3. Start the server — config files are generated automatically.
4. Configure plugins/RedstoneReboot/config.yml and restart-backends.properties.
5. Run /reboot reload to apply.

Mod Install (Fabric/Forge/NeoForge)

1. Download the correct mod file.
2. Place it in mods/ (Fabric requires Fabric API).
3. Start the server.
4. Configure config/redstonereboot.properties and config/restart-backends.properties.
5. Run /reboot reload to apply.

🎮 Commands

🔗 PlaceholderAPI (Bukkit Builds)

MOTD compatible as of v1.3.3+.

🔗 Quick Links

• 📖 Complete Wiki
• 💻 GitHub Repository
• 🛠️ Developer API Docs
• 📊 bStats
• 🐛 Bug Reports & Issues
• 💬 Discord Support

Crafted with ❤️ by DemonZ Development

Premium Minecraft infrastructure, engineered for scale.