Considering I made a post about my top IRC clients, I have been told, and have thought about showing a tutorial based on connecting and using such clients. First one being mIRC and AdiIRC. So without further-ado..

Lets get our clients

One of the first things before connecting to IRC is getting a client.. And for todays, we are using mIRC and AdiIRC.

mIRC: http://www.mirc.com/get.html

AdiIRC: https://www.adiirc.com/download.php

Once you have them installed, which should be pretty easy, just click next when it asks you to. After that we can go onto the next thing. AdiIRC requires Microsoft’s .NET Framework, which it should install itself, or you can download versions 2.0 or 4.5 yourself, mIRC shouldn’t require anything, if that’s your thing.

Now lets connect!

On mIRC and AdiIRC simple connections and scripted connections are pretty much the same. Lets say you’re connecting to a network named LameNet and its ‘hostname’ or ‘server address’ is “irc.lamenet.org”, and you saw it say it has SSL and Non-SSL ports, 6697 and 6667 respectively.

For a quick connect from AdiIRC or mIRC to their SSL port:

/server irc.lamenet.org +6697

Now AdiIRC and mIRC have a switch (–switch/-s) you can use so you don’t have to put +PORT, and their’s is -e

If we write that as a command,

/server -e irc.lamenet.org 6697

Lets say another group of friends says they are on freenode, you can connect to it without killing your connection to LameNet

/server -m chat.freenode.net +6697
/server -me chat.freenode.net 6697

Lets say you have LameNet, freenode, and ElectroCode perhaps. But you don’t want to type that every time you open your client.

In AdiIRC, Menubar -> Tools -> Edit Scripts
In mIRC, Menubar -> Tools -> Script Editor -> Make sure you’re on the remote tab

The code to put down in either client is the following,

on *:START: {
  server -e irc.lamenet.org 6697
  server -me chat.freenode.net 6697
  server -me irc.electrocode.net 6697

After that is put in, you need to save your script so that it works.. Choose a name that describes your script.

After that is done, when you click save and you exit, you will be prompted with a question/warning, this is due to the code being used can either start when loaded, as we are technically loading a new script in; The other time is whenever you start up your client. The dialog box looks like this.

Allowing your script to initialize.

If you’re already connected to your networks, you DO NOT say ‘Ok’, as this will kill your current connection, as well as open up two new connections to the second and third networks, the reason being is the -m switch, which as said, opens a new connection, no matter what.

Some Extra things to think of — Stuff to do after connecting

Both of these clients have some options that are beneficial to you, and your continued use of IRC.

One of the things is having some of your events come to the window you’re looking at. So you don’t have to switch windows to check on if a command went through. The few you should be most ‘concerned’ about, is “Whois”, “Notice”, and “CTCP”. On AdiIRC, this may be already set, but you want these set to “In Active” for the most part, if you are a network where ‘notice spam’ ‘ctcp spam’ are prevalent, then feel free to leave them as “In Status”.

In mIRC, Menubar -> Tools -> Options -> IRC and then you should see

on the right.

There is also a scripting way of getting this done, but that will be in a later post.




If you think there should be changes to this post, leave a comment down below! I can’t improve if there’s no response of what I need to improve on.

See here for other ways to contact me.

Tagged , , , , , , . Bookmark the permalink.

  • If this page or post could use some sprucing up, let us know by contacting us through this link