               ******************************************
               Instructions for running a WoD 7.44 server
               ******************************************

		Modified from wod6.08 server instructions
                           by Joker{WoD}

This documentation assumes you're already familiar with running Q2 and
know your way around it pretty well.  If you don't, I suggest going to
http://www.planetquake.com/console/ to learn about all the different
things you can do at the Q2 console.

Files and Locations
-------------------
Your WOD7.3 directory must be "quake2/weapons".  In that directory you
must have the gamex86.dll, the new pak0.pak file, and a server 
configuration (i.e. server.cfg - Edit SAMPLEserver.cfg to your liking,
then rename to server.cfg). 

To run a dedicated server, the command is:

quake2 +set dedicated 1 +set game weapons +exec server.cfg


Maps
----
Although maps may be placed in the quake2/weapons/maps directory, it is
advisable to put all of your maps in the quake2/baseq2/maps directory
where they can be accessed by all mods.


Message of the Day
------------------
Your server can have a "message of the day".  It'll be shown briefly
to players as they log in (and will appear in their scrollback).  The
default name for the MOTD file is "motd.txt", but that can be changed
by changing the value of the "motdfile" variable.  The MOTD file must
be in your "weapons" directory.

NOTE:  Your MOTD must be less than 1500 characters on deathmatch servers
and even less on Teamplay DM or Extinction.  If your MOTD is too long
your players will overflow immediately upon connection, and won't be
able to connect.  


Map List Feature
----------------
Try "set maplist 1" on your deathmatch or team-deathmatch server...the
next map will be chosen from maplist.txt, instead of running in the
normal loop.  (maplist will be subsequently set to 2, 3, etc. by the
server, indicating where it is in the maplist.  It will loop back to 1
at the end of the file.)


Map List by "Number of Players" Feature
---------------------------------------
Two different maplists can be used according to the number of players
on the server.  

The "smallmapfile" variable sets the name of the maplist
file for a smaller number of players, this is also the default maplist.

The "bigmapfile" variable sets the name of the maplist for a larger number
of players.

The "num_big" variable determines when to switch to the large maplist.


Example for switching to large maplist when there are 6 or more players:

set num_big 6
set smallmapfile maplist.txt
set bigmapfile bigmaps.txt


New Rail Only Maplist Feature
-----------------------------
This feature bans ALL weapons except the Railgun on any map in your
maplist with a "+" added at the end of the name (no space).
Players will spawn with a railgun in hand.  Ex:

		q2dm1
		2box4+
		fact3
		thegym+

This feature cannot be used on manual map changes - sorry, but the
manual map change function is part of quake2.exe.


Multiple Servers on Single System
---------------------------------
If you are running multiple servers on one system you will need to
make multiple maplist files with different names.

Example for 2 servers on one system:
	Make 2 maplists, one called "maplist1.txt" and the other called
	"maplist2.txt" in the weapons directory.

Add to first servers config:			Add to first server config:
----------------------------			---------------------------
set maplist 1					set maplist 1
set maplistfile maplist1.txt			set maplistfile maplist2.txt
set smallmapfile maplist1.txt 			set smallmapfile maplist2.txt
set bigmapfile maplist1.txt			set bigmapfile maplist2.txt

For different "Message of the Day" on each server add:

set motdfile motd1.txt				set motdfile motd1.txt


DMFLAGs
-------
The dmflags determine the game settings for the server, the default is 16.

Values:
1 - No Health.
2 - No Powerups.
4 - Weapons Stay.
8 - No Falling Damage.
16 - Instant Powerups.
32 - Same Map.
64 - Teams by Skin.
128 - Teams by Model.
256 - No Friendly Fire.
512 - Spawn Farthest.
1024 - Force Respawn.
2048 - No Armor.
4096 - Allow Exit.
8192 - Infinite Ammo.
16384 - Quad Drop.
32768 - Fixed FOV.

For example, to set infinite ammo, Instant Powerups, and Weapons Stay,
weaponban is 8212 (8192 + 16 + 4).

set dmflags 8212


WEAPON AND FEATURE BANNING
--------------------------
You can ban any of the weapons and features with the "weaponban" and
"featureban" variables.  Both variables are flags, in the same way
that the "dmflags" variable is: just add together the numbers of the
weapons/features you want to ban, and that's your value for
weaponban/featureban, respectively.

Values for weaponban:

Ban flare gun			1
Ban shotgun			2
Ban disruptor			4
Ban super shotgun		8
Ban freeze gun			16
Ban machinegun			32
Ban razorgun			64
Ban burstfire machinegun	128
Ban chaingun			256
Ban streetsweeper		512
Ban grenades			1024
Ban napalm avenger		16384
Ban grenade launcher		131072
Ban bazooka			262144
Ban rocket launcher		524288
Ban speedrocket launcher	1048576
Ban IR laser			2097152
Ban teslagun			4194304
Ban railgun			8388608
Ban deathray			16777216

For example, to ban the teslagun (4194304) and the deathray (16777216),
weaponban is 20971520 (4194304 + 16777216).

set weaponban 20971520

Note that if you ban grenades (value 1024), then *all* of the grenade
types, as well as the grenade launcher and bazooka, are banned too.


Banning Dark Magik Grenades
---------------------------
To ban all grenades except the standard fire grenade:
set unigrenade 1


OGL Grenade Ban
----------------
To ban just the Kamikaze and Plague grenades:
set ogl_grenades 1


Airstrike Ban
-------------
To ban the Airstrike feature:
set airstrike 0


Rail Deathray Only
------------------
To set the server for Rail and Deathray only:
set rail_deathray 1


Values for featureban:

Ban bandolier		1
Ban ammo pack		2
Ban silencer		4
Ban rebreather		8
Ban environment suit	16
Ban adrenaline		32
Ban megahealth		64
Ban power armor		128
Ban decoy		512
Ban grappling hook	1024
Ban player ID		2048
Ban kamikaze		4096
Ban zoom view		262144
Ban jetpack		524288

For example, to ban the jetpack and decoy, featureban is
512 + 524288 == 524800.

You can also ban frags for certain weapons, i.e. players can use them
to kill other players, but won't score any points for doing so.  The
"fragban" variable uses the same flags and values as the "weaponban"
variable, with the following additions:

Ban frags for blaster				67108864
Ban frags for telefrags				134217728
Ban frags for kamikazes				268435456
Ban frags for grappling hook			536870912

For example, to ban frags for telefrags and grappling hook, fragban
is 671088640 (134217728 + 536870912).




WoD features IP banning.  You can add or remove addresses from the
filter list with "sv addip <ip>" and "sv removeip <ip>".  The ip address
is specified in dot format, and any unspecified digits will match any
value, so you can specify an entire class C network with "sv addip 192.246.40".

removeip will only remove an address specified exactly the same way.
You cannot addip a subnet, then removeip a single host.

There is one more way to ban a player.  "sv kickban <player#>" will ban
the player's IP address and then kick them from the server.

"sv listip" prints the current list of filters.  "sv writeip" dumps
"sv addip <ip>" commands to listip.cfg so it can be execed at a later date.
The filter lists are not saved and restored by default.

In addition, there's a "filterban" variable.  If set to 1 (the default),
then ip addresses matching the current list will be prohibited from
entering the game.  If set to 0, then only addresses matching the list
will be allowed.  This lets you easily set up a private game, or a game
that only allows players from your local network.

-----

Other variables:

set teamplay 0    -- sets server to teamplay if set to 1

idledetect -- The number of minutes a player can be idle before they're
			kicked.  (Set it to 0 to turn it off.)

Changed dmflags:

DF_TEAMREBALANCE - Available under Teamplay DM or Extinction.  Replaces
	DF_CTF_NO_TECH (since there aren't any techs in WoD).  If set, then
	after each game, the teams are rearranged according to players'
	frags-per-minute.  (This is probably what you'd want to run on a
	public Teamplay WoD server.)



Server Crashes
--------------
Does your server sometimes crash with "ERROR: *Index: overflow"?

Usually, it's the server running out of modelindexes.
The problem happens because anything in the map that can move or be
destroyed (exploding walls, bridges, and so on) are also considered a
model.  They might not be used in the deathmatch game, but the
modelindex doesn't get freed.

It just means you can't use that map with WoD.  Stop using it.

