This release fixes servers you create without starting right away, straightens out where the Files tab says datapacks go, and makes the background service that keeps your servers reachable lighter. Here is what changed.

Creating a server

In 1.5.0, if you created a server and chose not to start it straight away, its card could say “We’ve lost track of what’s happening to this server” and keep the Start button greyed out, so there was no way to start the server you had just made. That broke in 1.5.0 and is fixed: a new server that has not been started now shows as stopped, and Start works the first time.

The Files tab and importing

The Files & Folders guide on the Files tab told you datapacks belong in a world’s hidden .appdata/datapacks folder. Nothing reads that folder. Minecraft loads a world’s datapacks from the world’s own datapacks folder, and the guide now shows that. We also trimmed the guide down to the folders you actually work in (your worlds, plugins, mods, config) and hid the ones SpawnBox manages for you.

When you import a server, the wizard offered a checkbox to bring the world’s datapacks along. Your datapacks always came with the world, because they live inside it; the checkbox only made an extra copy in that same unused folder. The checkbox and the copy are gone. Nothing about what you get after an import changes.

The background service

SpawnBox runs a small background service that keeps your servers reachable and your backups running. Several fixes make it lighter:

• On computers with a newer (IPv6) internet connection, it re-added every one of its network rules on every check. It now adds only the ones that are missing.
• Its log files grew for as long as it ran, which on a PC that stays on for weeks could mean hundreds of megabytes. Logs now roll over while it runs.
• It ran at a lower priority than your other programs, so when your PC was busy it could fall behind. It now runs at normal priority.
• A routine wait between update checks showed as Degraded and kept forcing the status panel open. A wait we were told to take is now shown as information, not a problem.

Diagnostic Package

A Diagnostic Package is the bundle of logs and settings you can send us when something goes wrong. Reopening a package you already built used to lose the email and Discord username you typed, so it reached us with no way to reply to you. It now keeps them, and it says “Loading your finished package…” while it finds the one you built instead of showing an empty form. The progress shown while a package builds also no longer freezes during its longest steps.

Smaller fixes

• In some setups the backup service could keep reloading its settings over and over, making every part of the background service redo its work far more often than it needed to. It now settles.
• Turning off automatic port setup for one server no longer switches off newer-connection (IPv6) forwarding for your other servers, and forwarding no longer blinks off for a moment when the background service starts.