aboutsummaryrefslogtreecommitdiff
path: root/minetest.conf.example
diff options
context:
space:
mode:
authorAuke Kok <sofar@foo-projects.org>2016-03-01 23:14:26 -0800
committerparamat <mat.gregory@virginmedia.com>2016-03-19 17:56:26 +0000
commitc5c727d62735e334ec64f07c557a2896d6d66d9f (patch)
tree1393fff1723a92fcf522ef24fe520a9533ce0bd6 /minetest.conf.example
parentd915ca11249050fd67a87ebee16ca2b2f67f93d5 (diff)
downloadminetest-c5c727d62735e334ec64f07c557a2896d6d66d9f.tar.gz
minetest-c5c727d62735e334ec64f07c557a2896d6d66d9f.tar.bz2
minetest-c5c727d62735e334ec64f07c557a2896d6d66d9f.zip
Allow NodeTimer, ABM and block mgmt interval changes.
ABM's are hardcoded to run every 1.0s, NodeTimers are hard coded to run at every 1.0s. Block mgmt is running every 2.0sec. However, these timers can be better tuned for both higher and lower values by server owners. Some server owners want to, and have the resources to send more packets per second to clients, and so they may wish to send smaller updates sooner. Right now all ABM's are coalesced into 1.0 second intervals, resulting in large send queues to all clients. By reducing the amount of possible timers, one can get a far better response rate and lower the perception of lag. On the other side of the camp, some servers may want to increase these values, which again isn't easily doable. The global settings abm_interval and nodetimer_interval are set to current values by default. I've tested with 0.2/0.5 type values and noticed a greatly improved response and better scattering of nodetimers, as well as enjoying not faceplanting into doors with pressure plates anymore.
Diffstat (limited to 'minetest.conf.example')
-rw-r--r--minetest.conf.example12
1 files changed, 12 insertions, 0 deletions
diff --git a/minetest.conf.example b/minetest.conf.example
index 6a9dc5ce3..65b1f19e5 100644
--- a/minetest.conf.example
+++ b/minetest.conf.example
@@ -980,6 +980,18 @@
# type: float
# dedicated_server_step = 0.1
+# Length of time between Active Block Management execution cycles
+# type: float
+# active_block_mgmt_interval = 2.0
+
+# Length of time between ABM execution cycles
+# type: float
+# abm_interval = 1.0
+
+# Length of time between NodeTimer execution cycles
+# type: float
+# nodetimer_interval = 1.0
+
# If enabled, invalid world data won't cause the server to shut down.
# Only enable this if you know what you are doing.
# type: bool