ViewDistanceTweaks

Changed

• New defaults for how fast the plugin reacts. A benchmark on fresh terrain (players flying into land nobody had generated yet) showed the old defaults raising the view distance to 16 while single ticks took over a second, and taking about two minutes to back off. The cause: MSPT was averaged over a full minute, which hides a one-second freeze almost completely, and the chunk generation safeguard was off.

  • ticks-per-check 600 -> 200: worlds are checked every 10 seconds instead of 30.
  • passed-checks-for-increase 3 -> 9: growing stays exactly as fast as before (about +2 chunks every 90 seconds), only reacting to load got faster.
  • collection-period 1200 -> 200: MSPT is averaged over 10 seconds instead of a minute.
  • chunk-generation-safeguard is now on, trips at 8 newly generated chunks per second instead of 15, and caps view distance at 8 while it is tripped (emergency-view-distance -1 -> 8). Walking into new land stays below that; elytra and horse travel does not.
  • The event-mode profile's passed-checks-for-increase 20 -> 60, so it keeps the same pace.

  With these values, on fresh terrain the p99 tick time went from 242 / 406 ms to 58 / 48 ms and ticks over 100 ms from 485 / 733 to 107 / 114 (two runs each, same bot routes). On pre-generated terrain nothing got worse: the plugin still holds about 14.5 view distance at the stutter level of a fixed 12.

Config update

Existing config files are updated on the first start. A value is only changed if it still has the old default; anything you set yourself stays as it is, and a backup is kept as config.yml.bak. Each changed line gets a short note with its old value. If your ticks-per-check was still 600, every passed-checks-for-increase in the file (profiles included) is tripled with it, so the climbing pace you chose stays the same. The console lists every setting it changed.