ReaperFlood ReadMe
Author: DDA-TriCk-E
Version: 1.18
Beta Version: No


Contents
   o Version Changes
   o Config.ini
   o Proxies
   o Delays
   o Cdkeys
   o Interface
   o Special characters
   o Nagle Algorithm: definition
   o Static: definition
   o Dynamic: definition
   o Boolean: definition


Version changes
v1.18
 Added
   o Nagle Algorithm support, when this is enabled it can significantly increase
     the speed of your flood. I haven't tried this for loading yet but one would 
     assume it would work fine.
   o Loading sets, to allow bots to connect in groups. (Not recommended for floods) [Experimental Component]
   o Cdkeys per proxy so you can load more than 1 bot per proxy.
 Removed
   o nothing
 Fixed/changed
   o Changed from timer to Winsock-Level timeout system, saying this it may be wise to decrease 
     the 'waittimeout' in config for faster flooding.
   o Changed from listbox to collection for spams.txt data.
   o Changed configuration, you will need to update your old one with this one.


Config.ini

///// Settings
 {victim}
   o The channel to flood or massload

 {server}
   o The battle.net server to connect to
   o Must be the IP address of the server, e.g. 63.241.83.109

 {format}
   o This field can either be static, dynamic or mixed. Dynamic makes use of the special characters

 {password}
   o This field is purely static
 {spamset}
   o This field is the spamset for flooding
	R or r Makes the bot to rejoin (each spamset must start with R)
	S or s Makes the bot to spam the next line from spams.txt

 {verbyte}
   o The hexed version byte for Starcraft, e.g. CB

///// On/off options
 {removebadproxies}
   o Boolean value that specifies whether to remove bad proxies.
 {removebadcdkeys}
   o Boolean value that specifies whether to remove bad cdkeys.
 {permanent}
   o Boolean value that affects both of the above options, if it is enabled it will remove
     the item permanently otherwise its temporary.
 {massload}
   o Boolean value that specifies whether the bot will massload or flood.
 {naglealgorithm}
   o Boolean value that specifies whether to use the Winsock Nagle Algorithm

///// Delay variables
o Millisecond values (1 second = 1000 milliseconds)
 {waitbetweensets}
    o Specifies time to wait between connecting each set (experimental)
 {waittimeout}
    o Specifies time to wait before forcing the winsock to timeout.
 {waitchannel}
    o Specifies time to wait in the preparation channel before flooding.

///// Amount variables
 {connectperset}
    o Specifies how many bots to connect per set (experimental)
 {proxylogin}
    o Boolean value that specifies whether to authorize proxies via string or array type connection.
 {proxythreshold}
    o Specifies how many proxy or socket errors the bot allows before this proxy is removed. 
    o Only works when 'removebadproxies' is enabled
 {cdkeysperproxy}
    o Specifies how many bots to load on each proxy


Proxies

SOCKS4(SOCKS4.txt) and SOCKS5(SOCKS5.txt)
    o Each proxy goes on a new line, avoid having blank lines for faster loading.
    o Proxies go in this format: x.x.x.x:port, the x's represent the number value for each part.
    o If no port is specified it is assigned with the default SOCKS port: 1080


Delays(Delays.txt)
    o The delays must be non-zero times in milliseconds.
    o Each delay goes on a new line, avoid having blank lines for faster loading.


Cdkeys(Cdkeys.txt)
    o The cdkeys must be 13 characters, remove the separators from your cdkeys if you have them.
      e.g. 0000-00000-0000 would be 0000000000000
    o Each cdkey goes on a new line, avoid having blank lines for faster loading.


Interface
    "Connect" 			Connects all bots to the specified server.
    "Disconnect" 		Disconnects all bots from the specified server.
    "Victim Channel" 		Indicates where the bots are loading or flooding.
    "Total Sockets" 		Indicates how many sockets are loaded.
    "Total Attacks" 		Indicates how many bots have attacked, only works for flooding.
    "Online" 			Indicates how many bots are connected to the server. (Unreliable)
    "Connecting to proxy"	Indicates how many bots are connecting to the proxy.
    "Connecting to server"	Indicates how many bots are connecting to the server.
    "Connection errors"		Indicates how many bots are experiencing problems connecting.


Special characters {
	# Inserts a randomly generated number in place of this symbol
	@ Inserts a randomly generated uppercase letter in place of this symbol
	$ Inserts a randomly generated lowercase letter in place of this symbol
	% Inserts a random type's value in place of this symbol
	Else Other characters remain as is
	Note Accepted battle.net characters are:
		(A - Z) (a - z) (0 - 9) - . _ ( ) [ ]
		The non-alphanumeric characters cannot be put at the start of the name or next to eachother in a name
}


Nagle Algorithm: definition {
	The Nagle algorithm works by aggregating data on the sending side of TCP applications. 
	It accumulates sequences of small messages into larger TCP packets before data reaches
	the wire, thereby preventing the generation of unnecessarily large numbers of small packets. 
	When the Nagle algorithm works as designed, TCP applications utilize network resources 
	more efficiently. 

	Applications can enable or disable the Nagle algorithm with the TCP_NODELAY socket option.
	Windows, Linux, and Java systems all normally enable the Nagle algorithm by default. 
	However, in some cases, the Nagle algorithm has a negative effect on application performance, 
	so network application engineers may prefer to disable it. 
	Reference: http://compnetworking.about.com/od/tcpip/l/bldef_nagle.htm


Static: definition {
	Data that is a constant variable, therefore it doesn't get changed.


Dynamic: definition {
	Data that doesn't stay the same, it can change.


Boolean: definition {
	The value of this can only be 0 or 1, 0 indicates false whereas 1 indicates true

Top