| EGGDROP WAR |
| Transform to lamer
user Kill Kill Die Die |
| The properly
configured Eggdrop bot is one of the most powerful IRC war machines, able
to flood, icmp, nuke, and easily takeover channels. It is also damn near
impossible to kill! On this page I will try to teach you a few of the
tricks of configuring and using the Eggdrop Warbot.
By itself Eggdrop is little more than a tough irc client. The heart of the warbot is in the various tcl scripts designed to wreak havoc on IRC! I'll tell you what they are, where to get them, and how to set them up for maximum damage. First, lets make sure yer bot's protection is set up properly. Eggdrop flood protection is set in the config file, way down in the "###MORE ADVANCED STUFF###" section. Heres an example from a 1.1.4 bot: # how many msgs in how many
seconds from the same host constitutes a flood? set flood-msg 5:60 You can change these to yer liking but I find that the defaults work just fine in most cases. Some bot masters run an extra tcl for protection such as ctcpprot but I've rarely had a bot flud off with the defaults. If you feel you need extra protection, its there. Fighting With EggdropSo you got a new bot and you want to be a badass? Well, its easy enough to do. After you have yer bot's protection squared away, you'll need a few tcl scripts to help you on yer way. I don't have the server space to offer all the available war tcls but you can get most any of them at ftp://ftp.sodre.net/pub/eggdrop/ in the appropriate scripts section for yer bot version. Here's a list of some of my favorites:
There are also a few advanced Unix war programs like "botnuke", "ssping", and "pepsi" but they require root access so almost noone can use them. If you have root access, you likely don't need me to tell you how to play war on Unix! The same goes for the fabled "spoofers", if you have them, you know how to use them. OK, now that we have them, how do we use them? Well, most have their own help files. Use them. Anytime you are planning on loading a script you should always open it in an editor to see if there is anything you need to set before loading it. Now's a good time to look the script over for the basic commands, and the help commands! For example, the help file in takeover.tcl is accessed with the command ".thelp". This is a typical usage. Sometimes there are settings for which user flag will be required to use the tcl. Most default to +m but you can change that. My recommendation is to leave it as +m or even +n. Don't let all yer users access your bot's war stuff unless you want problems with opers. Let's talk a little about icmp.tcl. This script rox, if you can use it. Unfortunately most shells don't allow ping or allow only very limited pinging. Its easy to find out if you got lucky.... Just load the script, no editing needed for the test. In dcc type ".set icmp 1". Now get someone's dns addy (the numeric one, do "/dns nick" in mIRC) and type ".icmp addy", putting the dns addy instead of the word "addy" of course.... Your bot will do one of several things. Most likely it will say "Sorry, this shell does not support ping". If it does, yer s.o.l., unload the script. It might, however, say "now icmp flooding". If it floods, watch yer victim (or use yer own dns for the test) and see if he poofs. If he drops off within a few minutes you are one of the lucky ones! If not, your ping is limited to a useless level. The help file for icmp.tcl is "icmp". Another kewl script is mjoin.tcl. Its a botnet mass join/part script. Its usage is real simple, just load it and type ".mjoin #channel". Every bot on yer net which is running this script will join that channel. Use ".mpart #channel" to get them out. This script can be loads of fun but use it carefully as some people don't care for their bots being jerked into strange channels. Those people, of course, shouldn't run this tcl but some do...... The king of the Eggdrop war scripts is flud.tcl, available in various versions. The ones I prefer are available above. Use 501e for 1.0x bots and 501f for 1.1x. 501e comes complete with 2 versions, a standard -oc version and a +oc version. The +oc (stands for oper-check) will check the victim before fludding and abort fluds on opers, a damn good idea! There is a bit more to this tcl, both in setup and use, than most of the others. To get started open the tcl in any editor EXCEPT PICO (pico doesn't like long lines). You will see these settings at the top: # set flag1 "e"
;# Flag suggested for fludflag. The first one, #set flag1 "e", you have to uncomment if you want to use it. It gives users a seperate flag if they are allowed to flud. I never use this, I just leave the fludflag at "m", allowing any master to flud. The only settings you might need to change here are the fludnet, ircnick, and fludnick. Fludnet, obviously, should be set to the network yer bot is on. Ircnick allows 1.0x bots to have a different nick on the botnet and on irc, a good idea in my opinion. 1.1x allows you to set "botnet nick" in the config file so its not needed here. Fludnick is an interesting feature, very useful but somewhat annoying. It changes yer bot's nick during fluds to a random nick, such as SJYT233, then changes it back again after the flud. This can save you from k-lines when the victim sends his log to an oper but can be a bitch in a busy channel. I always set fludnick 1. All my bots flud and I have very few k-lines. Its up to you! OK, once you have these things set its time to learn how to use flud. The help file for flud.tcl is ".fludhelp". You will need it. There are many types of fluds available, each useful in certain situations. The basic syntax for fluds is ".flud/ nick /# of times/ type of flud". In other words, ".flud butthead 10 15" would flud butthead 10 times with a type 15 flud, a "Boom" echo flud. Always use 10 for the number of lines as most fludbots are set for a maximum of 10. If my victim is a standard mIRC client I like to start with the Boom flud. If there are above 30 fludbots available he will usually drop. If he doesn't drop, he may be running an advanced mIRC script and be basically un-fludable. Against bots I use a "4" or clientinfo flud. Sometimes it works. Another kewl flud is the "22" or privmsg flud. This one opens a bunch of little chat windows on yer victims screen. Not very effective but annoying as hell! Experiment, find yer own favorites. A few other useful commands are ".fludbots", which tells you how many bots will flud, and ".last" which tells who made the last flud. Set yer console to +5 to see flud results and progress. Always remember the main rule of fludding, do a /whois on yer victim before fludding. DO NOT EVER flud irc operators. To do so risks not only yer own bots but all fludbots on the net. Most botnets will kick you off for fludding an oper. Remember this. You have been warned. Fighting Against EggdropSince Eggdrops are UNIX processes they are invincible to standard nuking and such things as will easily kill a Windoze client. A strong icmp, such as from a T3, will kill a bot but thats about it. This assumes, of course, that yer bot is on a solid shell (Win-Eggs are NOT included). I've also had limited success with an old DOS based proggie called Flash. Most Eggdrops don't blink at this but a few will drop. Its worth a try if you need to kill an Eggdrop. If you have a good fludnet behind you (say 50 or more fludbots) you can sometimes drop an Egg with a standard flud. I find that clientinfo fluds (usually flud type 4) work best against Eggdrops. Again, most won't blink but a few will fall. You can also try a good nuker set for non-standard protocols like "host unreachable". If these things don't work yer likely stuck with waiting and hoping the bot's shell goes down so you can jump in the channel and quickly kill the other users, grabbing ops before the bot returns. In ConclusionMany people nowadays say things like "IRC war is lame" or "the days of IRC war are over". Well, lame it may be, but dead it certainly isn't. I am a firm believer in peace on Earth, and on IRC, but I also believe that peace is best maintained, in both cases, through superior firepower.
|