ViewDistanceTweaks
Automatically adjusts view and simulation distance per world to match what your server can handle - more distance when there is headroom, less before players notice lag.
Список изменений
A mistyped profile name silently dropped the profile you were running
/vdt profile <name> tore the current overlay down before it looked the name up. Type evnt-mode instead of event-mode and the command answers "unknown profile" — but by then every value event-mode had set was already back to what config.yml says, including its max-view-distance-cap. Nothing said so. activeProfile still named the profile, so /vdt status went on reporting event-mode as in effect for the rest of the session, and only a /vdt reload put the real values back.
The name is checked first now. A switch that is rejected leaves the running profile exactly as it was.
The log line and the chat announcement lied about excluded dimensions
A world with exclude-simulation-distance: true never has its simulation distance touched — the setter is skipped, which is the point. But the console line and the announce-changes-in-chat message were built from the numbers the engine had asked for, not the ones the world ended up holding. So a world sitting at simulation distance 12 was announced as "Sim: 12→6" while nothing had moved, and {newSim} in a custom announce-format carried the same wrong figure.
/vdt history reads the same event and always recorded the applied value, so the two contradicted each other on exactly the servers that exclude a dimension. Both now report what the world actually holds.
Emergency relief could not engage while the memory safeguard was active
emergency-relief is the last thing checkWorld() does, and the increase veto above it returned outright. In proactive mode a world pinned at its minimum still computes a target above it, because the chunk budget says it could afford more — so the cycle counts as an increase, and the memory safeguard refuses it and returns.
That is the exact situation relief exists for: at the floor, still over the threshold, nothing left to give back. It was the one path that could never reach it, and on a server with a tight heap it is the path taken every single cycle. Lifting relief already had its own route out for the same reason; engaging now has one too.
Smaller things
The version in plugin.yml is filled in from the build rather than written twice, so the number the update checker compares can no longer fall behind the jar it is in.
Three new tests cover the cases above. All 61 pass, and each of the new ones fails against 2.10.4.