So, as weechat is my #1, I thought I would save the best for last.  Its actually pretty easy to get things started in weechat, even adding servers and making weechat connect to them at the start can all be done in one line, granted with some typing.

Let’s Get Our Clients

weechat is great through SSH and when used as your direct client. On Windows, you can use it through putty, or install it in CygWin. If you’re on a Debian derived distribution, you can use ‘apt-get install weechat‘, of course, if you aren’t the root user, you will need to add ‘sudo’ to the front of that. Anyways.. Lets get our client downloading.


sudo apt-get install weechat weechat-scripts


I’m assuming you already have CygWin. Start up the package downloader, and either, go into Net and find everything, or enter ‘weechat’ into the search field, and select pretty much everything that comes up for it.


If you’ve got something else, or you’re looking for something else, see their download page here.

Let’s Start Connecting

Connecting to a network with the right options the first time is pretty easy for weechat users, as you can give all your options in one line.

Normal Connection

/connect irc.lamenet.org/6667

SSL Connection

/connect irc.lamenet.org/6697 -ssl

SSL Connection (Don’t Verify Certificates)

/connect irc.lamenet.org/6697 -ssl -nossl_verify

Now what if you have a server you want to connect to that has a password?

/connect irc.lamenet.org/6697 -ssl -nossl_verify -password="ServerPass"

What about SASL???

/connect irc.lamenet.org/6697 -ssl -nossl_verify -sasl_username="LameUser" -sasl_password="lamepass1234" -sasl_mechanism="PLAIN"

What if I have a certificate??

/connect irc.lamenet.org/6697 -ssl -nossl_verify -ssl_cert="%h/ssl/Cert.pem"

Setting up networks

The format for adding servers/networks and connecting to them directly is basically the same.

/server add LameNet irc.lamenet.org/6667 -[no]option=""

Lets try adding LameNet in as having a certificate”

/server add LameNet irc.lamenet.org/6697 -ssl -ssl_verify -ssl_cert="%h/ssl/Cert.pem"

What about if you want weechat to connect automatically when it starts?

/server add LameNet irc.lamenet.org/6697 -ssl -ssl_verify -autoconnect

“I have a certain RDNS I want shown, what do I do? (IPV6 type)”

If you have a /64, its going to look something like this 2004:2345:2:123::/64, you’re going to enter something like this

/server add LameNet irc6.lamenet.org/6697 -ssl -ssl_verify -ipv6 -local_hostname="2004:2345:2:123::4051:0001"

Given the previous was using IPV6, why don’t we look at a simple line to use it on a hostname that allows both IPV4 & IPV6.

/server add irc.lamenet.org/6697 -ssl -ssl_verify -ipv6

Wasn’t too hard was it? I would hope not.

Extra Stuff

Now that we’ve got you connected and roaming, how about we start showing some advanced uses or convenient plugins to have.


buffers.pl is a perl script(.pl) that gives users a buffer list, which if you’re used to most any other client, then this should be the first script you download/install. There are some extra things you can do with it, including making it look like a regular tree list of windows. See our post here, you’re also going to want to make sure you use /mouse toggle if you want to use your mouse to select your buffers.

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.


Since HexChat seems to be the goto for this type of client, that will be what this tutorial is about.  XChat is old, and mostly closed source, as far as my memory allows. Since HexChat comes from XChat, if you use hexchat, there should be no real big difference in your interface.

Lets get our clients!

Hexchat: https://hexchat.org

XChat: https://xchat.org

Installation is pretty easy, if you’re a beginner, you should be good on just pressing ‘Next’ through the whole thing. Otherwise, you should know what you’re doing with each section.

Let’s Start Connecting!

To start off, when you open HexChat for the first time, you should see a server list dialog box.

Shown here


As you’ll see I have a selected network called “New Network”, we’ll talk about this later in the post, for now, lets go for instant connections.

Ok, so lets say you’ve skipped the network list, if you want to connect to LameNet, then we enter /server irc.lamenet.org +6697 for SSL. and /server irc.lamenet.org 6667 for Non-SSL.

If you need to open up a new connection without killing your first, then you need to use the command /NEWSERVER with the same input, so that would be /NEWSERVER chat.freenode.net 6667/+6697

Here they are for readabilities’ sake.

/SERVER irc.lamenet.org 6667 -> Non-SSL
/SERVER irc.lamenet.org +6697 -> SSL

/NEWSERVER irc.lamenet.org 6667 -> Non-SSL
/NEWSERVER irc.lamenet.org +6697 -> SSL

You may be thinking, ‘But what do we do if we want to connect to servers when we start XChat though’, unfortunately, the scripting isn’t as helpful in HexChat, so we’re going to have to do this through the Server List GUI, so lets review that.

Network List and Advanced Setup

So you’ve gotten this far, you’ve connected to servers or networks, but want to step up your game.

Lets see that picture of the network list again


Ok, so we have the global settings, your preferred nickname, and your second and third choice, and for the buttons, we have ‘Add’, ‘Remove’, ‘Edit’, ‘Sort’, and ‘Favor’

We’re going to click ‘Add’, then click where ‘New Network’ appeared, edit the name to your liking, then press ‘Enter’ or ‘Return’ on your keyboard, and it will set that as the name. Now click ‘Edit’, making sure that your new network is selected, and it will bring up another little window.

Since we want to connect on the start of the client, we’re going to select the ‘Connect automatically…’ box. You’re going to do this to each network that you want to connect to when HexChat starts.

HexChat: Edit LameNet_028

You’re going to click first up where it says ‘newserver/6667’, then type ‘irc.lamenet.org/6667’, if its SSL, just put ‘irc.lamenet.org/6697’, and then click the ‘Use SSL for all the servers on this network’. If you know them and know they sign their own SSL certificates, click the ‘Accept invalid SSL certificates’.

If you end up making yourself a services account, check out the ‘Login Method’ dropdown, and select what suits your situation. Usually you’re going to use ‘NickServ…’

That should be all that needs to be done, if you haven’t added your channels to NickServ’s ‘AJOIN’, or you don’t have a bnc, you can add channels to autojoin, click the tab ‘AutoJoin Channels’ then ‘Add’, enter the channel name and if it has a key (join password) put that where its supposed to be.

With that, you should be well on your way to having a fine time IRCing.

Scripting Tip

One more thingone_more_thing… If you write your scripts using xchat’s API, they will work in both XChat and HexChat.

Here’s a sample script taken from here

__module_name__ = "Cancel's HelloBot"
__module_version__ = "1.0.0"
__module_description__ = "HelloBot by Cancel"

print "\0034",__module_name__, __module_version__,"has been loaded\003"

import xchat

def on_join(word, word_eol, userdata):
      triggernick, triggerchannel, triggerhost = word
      destination = xchat.get_context()
      destination.command("say Hello " + triggernick + " and welcome to " + triggerchannel)

xchat.hook_print('Join', on_join)



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.


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.

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