











Diagnostic answers now come back inside SpawnBox, the player list and Console recover on their own after a blip, plus new Minecraft versions and safer backups.
The theme of this one is simple: when something needs your attention, SpawnBox is better at telling you, and a few screens that could get left behind after a hiccup now recover on their own. There is a new way to hear back from us right inside the app, support for the newest Minecraft versions, and a handful of things that finally do exactly what you set them to.
Before, if you sent us a diagnostic report from the Diagnostics screen, hearing back meant watching Discord or email and hoping. Now, when we look at your report and work out what is going on, the reply comes to you right inside SpawnBox, as a notification and a card with the fix laid out plainly. You do not even need to be signed in for it to reach you. If we ever have an answer for you, you will see it the next time you open the app.
Most of the time the player list just works. But under some circumstances (after you minimized SpawnBox, a connection blip, or a brief server wobble) it could get stuck, either showing “nobody’s here” or people who had already left, and stay that way until you nudged it. Now it notices and catches itself back up within a few seconds, so what is on screen matches who is really on your server. If a server’s detailed data source ever drops out, SpawnBox falls back to basic tracking and brings the full stats back within seconds once it recovers, instead of showing you a richer view than it really has.
When you reopen SpawnBox or reconnect, the Console and Activity feed catch you up on everything that happened while you were away. That catch-up worked before, but the way it was pieced together was fragile, so once in a while it could be left behind until you poked it. We rebuilt it to be dependable, so coming back to either screen reliably reloads the full picture instead of leaving you looking at a stale one.
You can now spin up servers on the newest Minecraft versions, including 26.2 and the 26.1.x line. And creating Paper and Spigot servers works again, after those broke when their download service changed how it hands out files.
If your PC already runs Docker Desktop, first-time setup could hang and never finish. That is fixed. SpawnBox now sets up and runs its own engine right alongside Docker Desktop, out of each other’s way.
The memory (RAM) slider has always tried to keep you from handing a server more than your computer can spare, but that safety check recently broke and stopped working out your machine’s real limit. That is fixed. On top of the restored check, it now also warns you in the moment when a running server is asking for more than your machine can give right then, so a bad number gets caught early instead of surfacing as a crash at 2am.
A few backup fixes land together:
There was a bug where your server’s activity history could quietly stop recording joins, deaths, and chat after a scoreboard reset, leaving a silent gap. That is fixed, so your history stays complete.
Last release, SpawnBox’s background engine learned to stop after a few tries rather than retrying forever. This release extends that same safety net to the deeper setup steps underneath it, so if one of those keeps failing it also stops and shows you a clear, what-to-do-next status instead of flapping away where you would never notice. The “SpawnBox can’t reach the internet” message also names one more common cause now, a particular network setting, alongside VPNs.
Closing SpawnBox from the tray quits it right away now, cleanly, with no extra prompt to click through.
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。