New config file directive listenonc_forest

[irc/gameservirc.git] / gameserv / gameserv.example.conf

diff --git a/gameserv/gameserv.example.conf b/gameserv/gameserv.example.conf
index 2c9620d7f6ad430e16391871539516d0a2e51256..fc19f67454ea2444eeb902cef5f5907948132669 100644 (file)
--- a/gameserv/gameserv.example.conf
+++ b/gameserv/gameserv.example.conf
@@ -24,6 +24,9 @@ servername gameserv.yourdomain.com
 # GameServ Forest channel
 c_Forest #forest
 
+# True or false - whether or not to listen for commands on c_Forest
+listenonc_forest true
+
 # GameServ Forest Channel Topic
 c_ForestTopic The forest is dark and gloomy.
 
@@ -77,13 +80,30 @@ pidfile gameserv.pid
 # can be to be able to fight them.
 # ie. If this is set to 2, you can fight players two levels above you
 # eg. a level 1 player can fight a level 2 or 3 player, but not 4+
+# HINT: Set maxbfightdistance and maxafightdistance to 0 to allow same level
+#       player fights only
+
 maxafightdistance 2
 
 # This is the maximum number of levels below you a player 
 # can be to be able to fight them.
 # ie. If this is set to 1, you can fight players 1 level below you
 # eg. a level 12 player can fight a level 11 player, but not 10 or below
+# HINT: Set maxbfightdistance and maxafightdistance to 0 to allow same level
+#      player fights only
 maxbfightdistance 1
 
+# This is the maximum time (in seconds) that a player may remain idle
+# before something naughty happens to them :)
+maxidletime 300
+
+# This is the period (in seconds) that gameserv will wait between
+# checking the entire players list for idlers.
+# Warning: bigger networks should not set this too low!
+# Minor Warning: This should be fairly close to the maxidletime, but
+#     it doesn't have to be. The farther the two are apart, the more
+#     random it gets.
+idlecheckperiod 300
+
 # Delete or comment this line so that GameServ will Load
 die You must read the entire config file!