v0.1.69

v0.1.69

v0.1.68

v0.1.68

v0.1.67

v0.1.67

v0.1.66

v0.1.66

v0.1.65

v0.1.65

v0.1.64

v0.1.64

v0.1.63

v0.1.63: updating with the tunnel running could break the install

Worth updating for, and worth knowing about until you do.

- Updating while your tunnel was running could leave a half-copied install that
  would not launch. The tunnel runs MCPersist.exe itself, so it holds the very
  file the update replaces - the copy failed partway, the retries could not help,
  and it reported that the old install had been left in place when it had not.
  The update is now refused with an explanation until you stop the tunnel.
  Updating with only the Minecraft server running is safe and is still allowed.
- The update message no longer puts a scrollbar on the status page. The window
  grows the few pixels it needs and shrinks back afterwards.

v0.1.62

v0.1.62: a very small error-message fix

Nothing urgent. If adding someone to the whitelist fails to write AND cleaning up
its temp file also fails, you now still get the explanation naming what went
wrong instead of a raw error.

This round's audit found nothing else significant.

v0.1.61

v0.1.61: Java 8 detection and whitelist salvage ordering

Both narrow. Worth updating, but nothing urgent if you are on v0.1.60 and only
run modern Minecraft versions.

- Setting up an older instance (Java 8 era, e.g. 1.12.2 Forge) could read its
  Java version as "1" instead of "8" and then fail trying to download a
  nonexistent Java. Only reachable when Mojang's version manifest could not be
  reached, since that normally takes precedence.
- If a corrupt whitelist.json had to be replaced and the replacement then failed
  to write, you could be left with no whitelist.json and no message saying where
  the old one went. The replacement is now written first.

v0.1.60

v0.1.60: adding to the whitelist can no longer wipe it

Worth updating for. When the server was stopped, adding a player edited
whitelist.json directly - and if that file could not be read at that moment
(locked by antivirus or a cloud-sync agent, or truncated by an earlier crash),
everyone already whitelisted was replaced by just the newly added player. It
reported success while doing it.

- An unreadable whitelist is now refused outright, leaving the file untouched.
- A genuinely corrupt one is moved aside as whitelist.json.corrupt-<time> and
  you are told, instead of its entries silently disappearing.
- Whitelist writes are now atomic, so an interrupted write cannot truncate it.
- Cancelling a setup and starting another no longer lets the first one report
  "Done" into the second, which could leave you pointed at the wrong world.
- Saving Memory or Performance settings no longer looks like it did nothing when
  the world folder has been deleted.