Skip to content

Feature request: Add auto-update for game versions

Problem Statement

Currently, updating the Minecraft Bedrock server executable in Crafty requires manually clicking the “Update Executable” button in the web UI. There is no built-in way to schedule this update, which creates several issues for users who want fully automated server maintenance

Who will benefit?

1. Server Administrators / Owners

  • Can fully automate server maintenance, reducing manual work.
  • Ensures the server always runs the latest Bedrock version without constant monitoring.
  • Reduces the risk of running outdated executables that may have security issues or bugs.

2. Players

  • Experience fewer interruptions, since servers can be updated during scheduled downtime rather than unexpectedly.
  • Always play on servers with the latest features and bug fixes.

3. Crafty Developers

  • Feature adds value to Crafty as a one-stop server management tool.
  • Reduces repetitive support questions about how to update Bedrock servers automatically.

4. Community / Other Users

  • Anyone running multiple servers or automating larger deployments can save time.
  • Makes Crafty more appealing to users considering it over other server management solutions.

Benefits and risks

Benefits

  • Fully automated updates – Reduces manual work for server admins.
  • Up-to-date servers – Always run the latest Bedrock version with bug fixes and security patches.
  • Improved player experience – Updates can occur during scheduled downtime, reducing unexpected interruptions.
  • Consistency across servers – Useful for admins managing multiple servers.
  • Enhanced Crafty value – Makes Crafty a more complete, hands-off server management solution.

Risks

  • Server downtime during updates – Automatic updates could restart the server unexpectedly if schedules overlap with player activity.
  • Update failures – If the download or extraction fails, the server could be left in a broken state unless Crafty handles rollback.
  • Token/session expiration – If the scheduled task uses web session tokens, they may expire, requiring a more robust authentication method (e.g., API key).
  • Compatibility issues – Automatic updates could introduce new features or changes that break plugins, add-ons, or scripts.
  • Security implications – Automatically downloading and replacing binaries must be done securely to prevent tampering.

Proposed solution

Add a new scheduled action in Crafty called “Update Server Executable” that can be selected in the existing Tasks / Schedule section. This action would:

  1. Stop the server (optionally, or leave it up if safe)
  2. Backup the server
  3. Update the Bedrock executable to the latest version
  4. Start the server

Essentially do the same thing as manually clicking the "Update executable" button.

Examples

  1. Pterodactyl
  2. Application Management Panel (CubeCoders AMP)
  3. MultiCraft
  4. Linux Game Server Managers (LinuxGSM)

Priority/Severity

Medium (This will bring a good increase in performance/productivity/usability)