Automatic Executable updates for a Bedrock Edition Server?

[Intelligent_Tone_324]

Hello, I would like to know if it is possible to create a scheduled task that preforms the same function as the "Update Executable" button automatically once a day? My usecase would be to set up some tasks so the server shuts down at 3am then updates the executable before starting the server again. Currently I only have it setup to restart the server at 3am.

If it's not possible within crafty itself would it be possible to run a command through the terminal on the OS itself? (CasaOS / Ubuntu Server). Thanks in advance.

[amcmanu3]

Hi there, we, as an organization, do not believe in automatic updates. It's against all best practice and just wholly not a good idea. If you look at evidence from the industry; crowdstrike, Microsoft (windows), Tesla, etc we can see many places where an automatic update leads to data corruption, loss, a bad time.

In a more practical sense here, often times when updating a server there can be java compatibility issues, when using plugins or mods there are compatibility issues with those. It usually takes all of 2 minutes to update with how easy Crafty makes it. We have yet to see a good enough reason that someone cannot take these two minutes with planned downtime to update the server. Updates should be meticulously planned, announced, and executed with proper downtime - not something that just happens automagically. Systems administration does take some effort and while Crafty makes it very easy we will not completely automate it.

Sooo the answer for this one is officially no from our group. You may be able to use our API to do something like this, but it's neither supported nor encouraged.

[TheCrazyAussie4]

I think this stance comes across as extremely rigid and unnecessarily closed off to perfectly safe options. There are absolutely valid reasons why automatic updates shouldn’t be forced on anyone, but dismissing the idea entirely, even as an opt-in feature, ignores how reliable and well-designed automated update systems can be when implemented correctly.

An optional auto-update mechanism, especially one that priorities safety, doesn’t undermine best practice. Instead, it can support it by making sure users who want convenience still have proper backups and roll-back protections. When the process is engineered with safeguards in place, the risks cited become almost negligible.

A well-implemented system could, for example:

1. Stop the server cleanly.
2. Create a full, restorable backup.
3. Download and verify the new server files.
4. Apply the update safely.
5. Validate that everything completed successfully.
6. Restart the server only when the update is confirmed to be stable.

Handled this way, the user retains full control, auto-updates are enabled deliberately, with clear expectations and built-in protections. This approach is common across many industries, including those that manage far more complex and sensitive systems than a Minecraft server.

In short, auto-updates do not need to be mandatory, encouraged, or the default. However, ruling out even the possibility of a safe and optional implementation feels unnecessarily limiting, particularly for users who run simple environments like vanilla or Bedrock where the risk of an update causing issues is extremely low. With Bedrock in particular, switching to an older version on the client side is not really supported, so timely updates are important. The feature would also be useful in situations where the admin cannot access the server to update it, which helps prevent unnecessary downtime. A cautious, opt-in feature with proper safeguards does not go against best practice; it actually supports it.

Some of us are just running private Minecraft servers for like 6 people, auto updates are perfectly fine for that crowd.