************************************* Instructions for running a WOD:LOX server ************************************* I suggest naming your Weapons of Destruction:Lethal Orifice eXamination directory "lox". That seems to be the standard over the Internet. And it makes it much easier, when it comes to automatic downloads and all that, to know all Weapons of Destruction:Lethal Orifice eXamination files are going into the same directory. Two default config files have been provided -- server.cfg for deathmatch. You will probably want to edit them before running your server for the first time (though their defaults work well). To run a dedicated server, the command is: quake2 +set dedicated 1 +set game lox +exec server.cfg ----- Try "set maplist 1" on your 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.) I recommend starting with either "biggun" or "fact3" -- in my experience, those are the two biggest fragfest maps in the standard collection, and they're nice to use whenever you want to wake everyone up and get their blood pumping. The maplist.txt file, as provided, contains my opinion of which game maps make good DM maps. You are free to have your own opinion. maplist.txt contains the name of each of the good maps, 10 times, shuffled together thoroughly. Should be fine for most uses! ----- 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 LOX weapons weaponban and featurebans: ----------------- LOX 1.12.4 Flags ----------------- // weaponban SUPERBLASTER 1 SHOTGUN 2 SNIPERGUN 4 SUPERSHOTGUN 8 FREEZEGUN 16 MACHINEGUN 32 MACHINEROCKETGUN 64 BURSTMACHINEGUN 128 CHAINGUN 256 STREETSWEEPER 512 GRENADE 1024 CLUSTERGRENADE 2048 RAILBOMB 4096 PLASMAGRENADE 8192 NAPALMGRENADE 16384 SHRAPNELGRENADE 32768 CATACLYSMDEVICE 65536 GRENADELAUNCHER 131072 BAZOOKA 262144 ROCKETLAUNCHER 524288 HOMINGROCKETLAUNCHER 1048576 HYPERBLASTER 2097152 PLASMARIFLE 4194304 RAILGUN 8388608 FLAMETHROWER 16777216 BFG10K 33554432 For example, to ban the cataclysm device, the homing rocketlauncher, and the BFG10K (the 3 most hated weapons it seems), weaponban is 65536 + 1048576 + 33554432 == 34668544. 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. // loxweaponban AIRFIST 1 SWORD 2 PULSERIFLE 4 NAILGUN 8 BUCKY 16 SKIPPERHOMINGROCKET 32 //two spots here // GUIDEDMISSILE 256 POSITRON 512 STICKGRENADELAUNCHER 1024 ICECUBEGUN 2048 DURG 4096 LIGHTNINGGUN 8192 DOUBLEIMPACT 16384 FBFG 32768 DISINTEGRATOR 65535 VACUUMMAKER 131072 ENERGYVORTEX 262144 SPIRALROCKETLAUNCHER 524288 SONICRAILGUN 1048576 EXPLOSIVESHOTGUN 2097152 EXPLOSIVESUPERSHOTGUN 4194304 EXPLOSIVEMACHINEGUN 8388608 KAMINIT 16777216 WALLPIERCINGRAILGUN 33554432 NUKE 67108864 FLOATINGMINELAUNCHER 134217728 ANTIMATTERCANNON 268435456 SUPERRAILSHOTGUN 536870912 GUIDEDNUKE 1073741824 // loxsweeperban SUPERBLASTERSWEEPER 1 FREEZERSWEEPER 2 GRENADESWEEPER 4 BAZOOKASWEEPER 8 RAILGUNSWEEPER 16 FLAMESWEEPER 32 DURGSWEEPER 64 CHUNKGUN 128 SNIPERSWEEPER 256 EXPLOSIVECHAINGUN 512 EXPLOSIVESTREETSWEEPER 1024 STICKYGRENADESWEEPER 2048 // loxgrenadeban PLASMACLUSTERGRENADE 1 TELEGRENADE 2 FREEZERGRENADE 4 HOMERGRENADE 8 ROCKETGRENADE 16 BLINDINGGRENADE 32 POSITRONGRENADE 64 // loxarmorban ORGANICARMOR 1 SLUGARMOR 2 CELLARMOR 4 SHELLARMOR 8 BULLETARMOR 16 ROCKETARMOR 32 GRENADEARMOR 64 // loxfeatureban CLOAK 1 EXPLOSIVE 2 INVISIBILITY 4 FLASHLIGHT 8 CHECKSTATS 16 RANGEFINDER 32 PLAYERID 64 FEIGNDEATH 128 ANGELOD 256 ANGELOL 512 ANGELOM 1024 ANGELOF 2048 ANGELOP 4096 SWEEPERFIREMODE 8192 HEIGHT 16384 ANGELOB 32768 ANGELOH 65536 ANGELOBLIND 131072 AIRSTRIKE 262144 FPM 524288 TRACKER 1048576 ANGELOR 2097152 BATON 4194304 HOLO 8388608 CHAMBER 16777216 REGENHEALTH 33554432 ANGELOU 67108864 VAMPIHEALTH 134217728 // featureban BANDOLIER 1 AMMOPACK 2 SILENCER 4 REBREATHER 8 ENVIROSUIT 16 ADRENALINE 32 MEGAHEALTH 64 POWERARMOR 128 INVULNERABILITY 256 DECOY 512 HOOK 1024 ID 2048 KAMIKAZE 4096 LASERSIGHT 8192 TRIPLASER 16384 NIGHTVISION 32768 PUSHPULL 65536 SCANNER 131072 ZOOM 524288 JETPACK 1048576 CLOAK 2097152 For example, to ban the decoy, nightvision, and scanner, featureban is 512 + 32768 + 131072 == 164352. // fragban BLASTER 67108864 TELEFRAG 134217728 KAMIKAZE 268435456 HOOK 536870912 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 cataclysm devices, homing rockets, and telefrags, fragban is 65536 + 1048576 + 134217728 == 135331840. Also note that banning frags for the flamethrower (value 16777216) will ban frags for all fire. ----- WOD:LOX now features IP banning. You can add or remove addresses from the filter list with "sv addip " and "sv removeip ". 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 "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 " 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 "addip " 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. There is a nightdaytime variable available now. The default value is 13. This means that the time that it takes for the cycle to go from day to night to day 13 minutes. Just modify the nightdaytime variable to suit your needs. ----- Does your server sometimes crash with "ERROR: *Index: overflow"? I've finally figured out what the problem is. Turns out the game is running out of modelindexes. Every model in the game (male player, female player, each weapon, health-pack, and so on) gets loaded in and is assigned a modelindex. Quake II has an internal limit of 256 models. Most people don't get this problem unless they have several extra player models installed on their server machine, *and* they use the maplist feature. 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. That's just some sloppiness on Id's part. I've written them a letter about it. Until they fix their bug, here's what you do. First, if you have extra installed player models, you don't necessarily have to remove them. First, see if you can get just the standard 8 DM maps to run without incident. If not, you have too many player models & you're gonna have to remove some. But if the DM maps work fine, then you can run your server with maplist turned on. Note what maps cause your server to crash, and remove them from the maplist.txt file. Eventually :) you will have a list of maps that won't crash your server. 07-30-99 Well I have an update to the ERROR: *Index: overflow problem, I have created a workaround to the problem. Essentially this is what is going on. Whenever a new map loads the old models get uncached an the new models get cached. Knowing this information helped me develop the workaround. Basically what I did was provide a check that if you are about to get that error it will end the level and start the next one. Hopefully this will work until I can get a better solution. 09-06-99 It turns out that if you have the Grenade and Bazooka sweepers enabled you will start to get some warnings. Well these are just warnings but for some reason or another they will cause server lag. To fix the problem just ban these two weapons. ----- As always, if you have questions, feel free to mail me at jblabs@aracnet.com Modifications and additions for LOX v1.12.x by QwazyWabbit windowmeister@hotmail.com See the changelog.txt file for QwazyWabbit's modifications and fixes for the 1.12+ version of the mod. Portions of the changelog are also included in the release archive in the readme.txt file.