WHAT: 	Call of Duty / Quake 3 getstatus flood fix for Windows servers (quick and dirty) v3
WHO: 	omnigenus @ tcadmin forum
TNX2:	Luigi Auriemma and his Proxocket tool
FOR: 	WINDOWS ONLY!!!!

=======================================================================
		I M P O R T A N T    N O T E S !  !  !

- Please share this fix with every fellow hoster you know....
- This problem is hitting both Windows and Linux server, spread the word
- More people using this (or similar) solution = less DDoS attacks

=======================================================================


Ok, let's go :)


A) TESTING YOUR SERVER

	1. Create a new Call of Duty/2/4 server...or use the existing one, if you have one you can test this on.
	2. Start my Getstatus Flood Test Tool tool on your computer (you need .Net Framework 2.0 for this)
	3. Simply enter your CoD/2/4 server's IP and then PORT to test your server
	4. Program will now send one lame burst of 500 "getstatus" packets to your server and you'll be able to see the result
	5. If you get all the 500 game server status (info) responses... BAD TIMES..you need to fix that (Look @ B)


B) GETTING THE SHIT DONE

	1. Copy wsock32.dll and myproxocket.dll files from DLLs folder to your game server folder (where your game .exe is located)
	2. Make sure you DON'T RENAME THOSE FILES
	3. Make sure you put them in the same folder as the executable
	4. Start your CoD/2/4 test server
	5. Make sure the server is online and working (should be)
	6. Start my testing tool to check your server again. You should now see 11 full responses and then a socket timeout error.
	7. Be happy, rejoice, praise the lord and stuff like that 

-----------------------------------------------------------------------

IT'S WORKING?
	---> high five, grab a beer and you're welcome :-)
	---> spread the word

IT'S NOT WORKING?
	---> well...it must be your fault :Dcontact me and we'll try to see what the problem is