Updated Base Plugin Settings (markdown)

mikeprimm 2011-12-09 19:39:12 -08:00
parent a0899092c0
commit a5519d4585

@ -12,6 +12,8 @@ The core settings defined include the following:
* _renderaccelerateinterval_ : this setting, a floating point value in seconds, is used as the _renderinterval_ value when the length of the tile update queue exceeds _renderacceleratethreshold_ tiles in length. * _renderaccelerateinterval_ : this setting, a floating point value in seconds, is used as the _renderinterval_ value when the length of the tile update queue exceeds _renderacceleratethreshold_ tiles in length.
* _tiles-rendered-at-once_ : this setting controls the maximum number of update tiles that will be rendered concurrently. If not defined, the value defaults to 1/2 the number of processor cores. Settting this to lower values can reduce peek CPU use when large tile update load occur (from newly generated chunks, for example).
* _zoomoutperiod_ : this setting, an integer value in seconds, specifies how often update processing of zoomed-out tiles is done. This done to prevent unneeded regeneration of the tiles due to repeated changes by players (such as when mining). Default value is 60 seconds. * _zoomoutperiod_ : this setting, an integer value in seconds, specifies how often update processing of zoomed-out tiles is done. This done to prevent unneeded regeneration of the tiles due to repeated changes by players (such as when mining). Default value is 60 seconds.
* _enabletilehash_ : this setting, a boolean, is used to enable the use of tile content hash codes, which are used to avoid re-encoding tiles that have not changed in value after re-rendering (such as due to changes in blocks that are not visible on the tile). This reduces processing load, zoom-out processing, and communications traffic with web clients. * _enabletilehash_ : this setting, a boolean, is used to enable the use of tile content hash codes, which are used to avoid re-encoding tiles that have not changed in value after re-rendering (such as due to changes in blocks that are not visible on the tile). This reduces processing load, zoom-out processing, and communications traffic with web clients.