View Distance Tweaks

Code (YAML):

# Configuration for View Distance Tweaks.
# Plugin page: https://www.spigotmc.org/resources/75164/
# Github: https://github.com/froobynooby/ViewDistanceTweaks

# Please don't change this!
version : 8

# Set this to true to enable the plugin. The plugin is initially disabled so that you can make changes to the config
# appropriate to your server.
enabled : false

# How should we determine whether the simulation distance needs adjusting? Accepts three values:
#   proactive : Adjust the simulation distance so that the player-loaded chunk count is always below a set threshold.
#   reactive  : Adjust the simulation distance in response to changes in the server's MSPT.
#   mixed     : Be both proactive and reactive; prioritising decreasing the simulation distance over increasing.
adjustment-mode : mixed

# These settings are for the proactive adjustment mode.
proactive-mode-settings :
  # Set this to the maximum ticking chunk count your server can handle. The simulation distance of each world will be
  # adjusted such that the total number of player-loaded chunks is sitting as close to this value as possible.
  #   If you know your server can handle up to p many players with a simulation distance of d, a reasonable choice is
  #    to set this to (2d + 1)^2 p.
  #   As an example, 5780 is the number of player-loaded ticking chunks for 20 players with a simulation distance of 8.
  global-ticking-chunk-count-target : 5780

  # Set this to the maximum number of non-ticking chunks you want to be loaded by the view distance.
  #   Note: this only counts chunks that are outside of the simulation distance of a player, but within the view
  #    view distance of a player.
  #   If you know your server can handle up to p many players with a view distance of v and a simulation distance of s,
  #    a reasonable choice is to set this to ((2v + 1)^2 - (2s + 1)^2) p.
  #   As an example, 6720 is the number of non-ticking chunks loaded by the view distance for 20 players with a view
  #    distance of 12 and a simulation distance of 8.
  global-non-ticking-chunk-count-target : 6720

# These settings are for the reactive adjustment mode.
#   MSPT stands for "milliseconds per tick", and tells you how long your server takes to tick on average. A server
#    whose MSPT is above 50 will notice things slowing down, as the TPS drops.
reactive-mode-settings :

  # Below what MSPT should we consider increasing the simulation distance?
  increase-mspt-threshold : 40.0

  # Above what MSPT should we consider decreasing the simulation distance?
  decrease-mspt-threshold : 47.0

  # These settings concern how we determine the server's MSPT.
  #   Only touch these settings if you know what you're doing.
  mspt-tracker-settings :
  # Over how many ticks should we collect tick durations for calculating the MSPT?
    #   Setting this too high will make the MSPT very slow to react to changes.
    #   Setting this too low will make the MSPT volatile.
   collection-period : 1200

  # We keep a history of MSPT vs. player-loaded chunk count in order to better predict what the MSPT will settle to
  # after increasing the simulation distance.
  mspt-prediction :
  # Should we use MSPT prediction when we are considering increasing the simulation distance?
    #  * For example, we may be at 38 MSPT with a simulation distance of 6, meaning we would consider increasing the