                           

                        JIAN'S SET UP TEXT

This is my setup for running multiple instances of mIRC ver 3.64. 
The features are as follows:

1.  Allows ease in monitoring multiple channels in one window.
2.  Allows ease of communicating with multiple channels from the
    window you're monitoring.
3.  Provides for an extremely reactive protection mode. (Any user at level
    10 or above is protected not only against kicking but deopping as well,
    the deopper is immediately shitlisted, kicked and banned.)
4.  Complete remote control of all multiple instances of mIRC.
5.  81 different Vassago kicks from a ctcp command line.
6.  64 different Vassago kicks from an alias.
7.  On version sends a BlOoD LiCe VeR Xx9 along with the standard
    mIRC ver 3.64... Causes the bad guys to pause a bit before messing
    with you.
8.  Enhanced DCC functions and easy access to timers...
9.  Many other features too numerous to mention.

Special thanks go to Mook, Krejt & RoC without their input these ini's would not have
been possible!!!

                        SETUP INSTRUCTIONS

Step1:  
  
   Decide on your permanent nickname... It should be something that        
is not common... ie. Don't pick a nick like "Hacker." There are far too
many "Hackers" on the net. You need a variation of that nick. _Hacker, 
Hacker_ or Hacker^ are acceptable variations...

Step2:

   Decide on the channel that you're going to use monitor the channels your
other mIRC clients are in. For me the channel is #JIAN. Remember the mode
setting for this channel cannot be +n or +m. I use a mode setting of +sti.
+s = secret, +t = Only the op can change the topic and +i = invite only.
The reason you CANNOT set the mode to +n or +m is that your other
bots/clones will be sending to that channel... +n = no outside messages
to the channel and +m = moderated which means only ops or people with a
+v rating can speak in the channel.

Step3

   Create multiple mIRC clients. This is done by copying your mIRC.exe as
mIRC1.exe, mIRC2.exe, mIRC3.exe etc. Next copy the mirc2.ini file as 
mirc3.ini, mirc4.ini etc. Put mirc1.ini and the other mirc2-n.ini's in 
your windows directory. Go into Program manager and highlight the group
you're going to add your mirc clients to. Under "File" in Program Manager
select "New," then select item and enter the name of the client. This should
be MIRC1. This is your "master" client. All other clients will report to
this client. Your command line should be for example: 

C:\network\mirc\mirc1.exe -d mirc1.ini

The next one should be similar:

C:\network\mirc\mirc2.exe -d mirc2.ini

And so on... -d causes mirc to use the 3-D boxes we've grown so accustom
to in windows. Specifying which "ini" file to use on the command line
assures that each mirc will be set up correctly.

Step4

   Now fire up your mirc's and let's customize them to fit your specific
situation. In Mirc1 you should go into "Misc" select extras and TURN OFF
beep on notice in the upper right corner. This is done by making sure the
box in front of notice is blank. The reason for this is that mIRC1 will
be very busy receiving notices... it will beep you to death if you don't
deselect beep on notice. In the lower left section where it says: "Show
this text in the title bar" Insert "1" This will help you tell which is
your master client. Next you should add yourself as a level 1000 user. 
This can be done by typeing: /guser 1000 yournick 3 There is a problem in
mirc that only allows users to be added in this fashion up to a level 999.
So you need to select Tools and then Remote and edit your user list. You
will see yourself added at a level 999 change the 999 to 1000. Next click
on commands. You will see all the commands you have added to this section.
MAKE SURE LISTENING IS CHECKED!!! Now click on events. You will see all the
events that have been added... Again make sure listening is checked.

Step5

   Set up mIRC2 - n the same way... execpt there is no need to deactivate
the beep on notice. These won't be nearly as active as mIRC1. Remember to
Add yourself and the nicks of your additional client's at level 1000!!!
Now for the editing. Go to your remote sections and look for things that
are in ALL CAPS. They will say things such as "YOURNICK," "YOURCHANNEL."
Insert the appropriate information where it asks for these. Remember to
make sure your remote commands and events are activated by checking the
"LISTENING" box.

Step6

   Place your bots/clones - mIRC2 - N in the channels of your choice. You
can do this by typing /ctcp "nickofmirc2" join #channel or you can manually
do it by downsizing mIRC1 and maximizing mIRC2 and going to that channel.
When you're all set up they should report back to your home channel and 
you can monitor the activities in those channels... If one of your clones
is messaged it will show up in your message window with the name of the
clone and the nick of the person messaging you... Good Luck! Have fun and
remember: READ THE FAQ SHEET!!!!

Commands:

Joining a channel:

This can be done one of several ways. The first way is to tell the bot to join a channel.
The command is: /ctcp botsnick join #channel or /ctcp botsnick DO /join #channel. You 
can always go to the channel and invite the bot to that channel.

Opping in a channel:

If you have your levels properly set to 1000 for you and your bots, this really is a superflous
command because you or your bots will be automatically opped if you join a channel where
either you or one of your bots ALREADY have ops. Nevertheless the command is as follows:
/ctcp botsnick opme #channel

Remote Communications:

You can talk through your bots and have them speak in whatever channels they are in. 
The command for doing this is: /msg botsnick #channel (Message) If someone messages one
of your bots, you can have them message that person back by typing:
/ctcp botsnick DO /msg nickofperson (Message)

Remote Actions:

You can also have your bots perform actions in the CHANNELS they are in. Read that line
carefully! If your bot is in more than one channel... it will perform the same action in ALL the
channels it is in. Why? Because I haven't figured out a way to NOT make it perform the action
in all the channels... If you figure out a way... by all means share it with me. Anyway the 
command is: /ctcp botsnick DO /ame (Action to be performed)

BlOoD LiCe Xx9 is a better than average bot ini file for mIRC. It will always be under constant
revision! Feel free to share it with whoever you wish. Hopefully it will bring you more enjoyment
from your IRChat sessions. I developed the spybot aspects myself, with the help of Mook
and Krejt. I also incorporated RoC's beta ini file. I got tired of having my channels taken over
by some of the hoodlums that plague IRC. Let me say, there is NO WAY to guarantee your
channel will not be taken over, but you can make it difficult!  There are several tips you should
follow. Make sure your bots are not all on one server!!! The more different servers they are on
the more stable your channels!!! Also, don't give all your bots the same E-mail name/machine
name. That's a sure fire give away that it's a bot.  The best bots are the ones that nobody
knows are bots. Good luck and enjoy!!!




        