gameserv/gameserv.example.conf

   1 # This is an example configuration file for GameServ that contains every
   2 # configuration directive necessary to properly load GameServ
   3 # You should read this file along with the Changes file for any updates
   4 # and changes to the config file directives.
   5
   6 # You should copy this file to gameserv.conf then edit it. gameserv.conf
   7 # is the name of the config file that will be loaded at runtime.
   8
   9 ########## IRC STUFF ##########
  10
  11 # Comments can only begin at the beginning of a line, and must begin with a pound (#)
  12 # GameServ Nickname
  13 s_GameServ GameServ
  14
  15 # GameServ Host
  16 gshost yourdomain.com
  17
  18 # GameServ username (ie. username@host)
  19 gsident GameServ
  20
  21 # Gameserv Psuedo Server Name
  22 servername gameserv.yourdomain.com
  23
  24 # GameServ Forest channel
  25 c_Forest #forest
  26
  27 # GameServ Forest Channel Topic
  28 c_ForestTopic The forest is dark and gloomy.
  29
  30 # The hostname/ip of the real ircd gameserv will be connected to
  31 remoteserver 127.0.0.1
  32
  33 # The port on the real ircd gameserv will be connecting to
  34 remoteport 6667
  35
  36 # The password for linking to the real ircd
  37 remotepass linkpass
  38
  39 # Seconds to wait on load before displaying "Hello Nick" to new users
  40 # joining your network
  41 welcomedelay 10
  42
  43 # Message that is displayed to new clients that join the IRC Network
  44 # Welcomemsg is a formatted string. To use it in a function that uses formatting like notice(), you must include a string
  45 # as an argument. i.e. notice(s_GameServ, u, welcomemsg, nick);
  46 # This is only true if you include anything like %s etc... if you include more than one %s or %d or anything, you must
  47 # include the proper type as an argument also.
  48 welcomemsg Hello, %s! This network utilizes a services package called GameServ. For info on how to play the game, type /msg %S help.
  49
  50 ########## END IRC STUFF ##########
  51
  52
  53 # Filename to store player data in.
  54 playerdata players.dat
  55
  56 # Filename to load monsters from
  57 monsterdata monsters.dat
  58
  59 # Password to control SHUTDOWN, LOAD, and SAVE
  60 adminpass apass
  61
  62 # How often (in seconds) to save the player database. In case of accidental
  63 # shutdown or crash, this should be set fairly low. 180 seconds = 3 minutes.
  64 updateperiod 180
  65
  66 # How many forest fights per day should everyone get
  67 forestfights 100
  68
  69 # This is the filename for the gameserv process ID
  70 # This should be different between .conf files so you have different pid
  71 # files saved for each process (if you want)
  72 # If left the same for all processes, the pid file will hold the process
  73 # Id for the last run process
  74 pidfile gameserv.pid
  75
  76 # This is the maximum number of levels above you a player
  77 # can be to be able to fight them.
  78 # ie. If this is set to 2, you can fight players two levels above you
  79 # eg. a level 1 player can fight a level 2 or 3 player, but not 4+
  80 # HINT: Set maxbfightdistance and maxafightdistance to 0 to allow same level
  81 #       player fights only
  82
  83 maxafightdistance 2
  84
  85 # This is the maximum number of levels below you a player
  86 # can be to be able to fight them.
  87 # ie. If this is set to 1, you can fight players 1 level below you
  88 # eg. a level 12 player can fight a level 11 player, but not 10 or below
  89 # HINT: Set maxbfightdistance and maxafightdistance to 0 to allow same level
  90 #       player fights only
  91 maxbfightdistance 1
  92
  93 # This is the maximum time (in seconds) that a player may remain idle
  94 # before something naughty happens to them :)
  95 maxidletime 300
  96
  97 # This is the period (in seconds) that gameserv will wait between
  98 # checking the entire players list for idlers.
  99 # Warning: bigger networks should not set this too low!
 100 # Minor Warning: This should be fairly close to the maxidletime, but
 101 #     it doesn't have to be. The farther the two are apart, the more
 102 #     random it gets.
 103 idlecheckperiod 300
 104
 105 # Delete or comment this line so that GameServ will Load
 106 die You must read the entire config file!