I will try to update this tutorial on the release of new versions of the above softwares. They are both well known and widely used on IRC servers.

Ok, lets get started�

First of all download and install the Unreal setup file. This is a very simple process and requires just clicking next all the way through. DO NOT install it as a service if it asks. For novice users this can become very confusing.

Next you must copy the example config from the doc directory. Just enter the doc directory and copy example.conf into the main unreal install directory. You must now rename this file (example.conf) to unrealircd.conf. Now you must open the config file. The idea application for this is wordpad as windows notepad has line spacing trouble. On opening the config file there are a number of things you must change. All I will outline in this tutorial are the core basics to get your server up and running. There are many other options which you may use to customise your server to your own needs. These are all detailed in the Unreal IRCD docs.

Once you open the file you will see a number of things in it. I will now take you through step by step editing of this file to your needs.

Firstly, you will see the following 3 lines:

/* FOR Windows, uncomment the following 2 lines: */
//loadmodule �modules/commands.dll�;
//loadmodule �modules/cloak.dll�;

You must uncomment the 2nd and 3rd lines, that is remove the // from the front of them so that that block will look like this:

/* FOR Windows, uncomment the following 2 lines: */
loadmodule �modules/commands.dll�;
loadmodule �modules/cloak.dll�;

A little further down the file you will see:

me
{
name �IRC.foonet.com�;
info �FooNet Server�;
numeric 1;
};

This needs changing to the details of your own server. This can be ANYTHING you want. For example:

me
{
name �irc.pchowtos.co.uk�;
info �pchowtos IRC server�;
numeric 1;
};

A bit further down again you will see:

admin {
�Bob Smith�;
�bob�;
�widely@used.name�;
};

This is just for informational purpouses and just needs changing to your details. For example:

admin {
�Phil Lavin�;
�phil�;
�phil@pchowtos.co.uk�;
};

Now for config of the opers. Scroll down the file until you see the following:

oper bobsmith {
class clients;
from {
userhost bob@smithco.com;
};
password �f00?;
flags
{
netadmin;
can_zline;
can_gzline;
can_gkline;
global;
};
};

This is an example oper block config. This can be done unlimited times in a row to add new opers. You will need to edit this to your own details. oper bobsmith { is the oper username. This is what is typed when you oper-up on the server using the command /oper USERNAME PASSWORD.

userhost bob@smithco.com; This line tells the server where you are allowed to oper from. This is for security reasons to stop anyone stealing your password and opering up. bob is the ident and smithco.com is the host. This can be repeated as many times as you please. For example if you were to connect from home and work you may do:

userhost phil@*.home.host.com;
userhost phil@*.work.host.com;

* in the host is a wildcard. This means that those with a dynamic IP, like myself can still oper by using the static bit of the host.

The flags { section tells the server what you can do as oper. The only one you might want to add to this is �can_override�. This allows opers to override channel modes in which they do not have the access to do so.

Now a full example. In this example we will add two opers, jim and dave. They both connect from home and work and both have override privs.

oper jim {
class clients;
from {
userhost jimbo@*.dynamic.dsl.as9105.com;
userhost jimbo@*.vnnyca.adelphia.net;
};
password �j1msp4ss�;
flags
{
netadmin;
can_zline;
can_gzline;
can_gkline;
global;
can_override;
};
};

oper dave {
class clients;
from {
userhost davey@.ipt.aol.com;
userhost davey@.ip.alltel.net;
};
password �dav3sp4ss�;
flags
{
netadmin;
can_zline;
can_gzline;
can_gkline;
global;
can_override;
};
};

Next onto the listen block. This tells the IRCD where to wait for connections. Scroll down until you see:

listen *:6697
{
options
{
ssl;
clientsonly;
};
};

listen *:8067;
listen *:6667;

I will not go into what each bit means, but just trust me and change it to:

listen *:6667
{
options
{
};
};

listen *:7000;

The listen *:7000; is for when we link with Anope services later.

Next is the link block. This will give details as to how the IRCD will connect with services.

Scroll down until you see:

link hub.mynet.com
{
username *;
hostname 1.2.3.4;
bind-ip *;
port 7029;
hub *;
password-connect �LiNk�;
password-receive �LiNk�;
class servers;
options {
/* Note: You should not use autoconnect when linking services */
autoconnect;
ssl;
zip;
};
};

In this tutorial we will run services on the same server and on port 7000. For this you will need to change the link block to the following:

link services.YOURNET.COM
{
username *;
hostname 127.0.0.1;
bind-ip *;
port 7000;
hub *;
password-connect �PASSWORD�;
password-receive �PASSWORD�;
class servers;
options {
};
};

You must change YOURNET.COM to whatever the name of your network is. You must change PASSWORD to a hard to guess password of your choice.

Now scroll down until you see:

tld {
mask *@*.fr;
motd �IRCD.motd.fr�;
rules �IRCD.rules.fr�;
};

This is a really stupid dumbass bit of the conf about using different messages for different countries. Just delete this whole bit from tld { to };.

Now the easy �pretty pretty stuff�. Scroll down to:

set {
network-name �ROXnet�;
default-server �IRC.roxnet.org�;
services-server �services.roxnet.org�;
stats-server �stats.roxnet.org�;
help-channel �#ROXnet�;
hiddenhost-prefix �rox�;
}

And change the bit in the �s to your own network details. For example:

set {
network-name �PchowtosNet�;
default-server �IRC.pchowtos.co.uk�;
services-server �services.pchowtos.co.uk�;
stats-server �stats.pchowtos.co.uk�;
help-channel �#help�;
hiddenhost-prefix �pchowtos�;
}

Just under that you will see:

cloak-keys {
�aoAr1HnR6gl3sJ7hVz4Zb7�4YwpW�;
�and another one�;
�and another one�;
};

This is to do with cloaking the IPs of users. You need to edit the 2 lines shown here. You should make up keys of your own as these are important for the security of your users. An example (don�t use these) is:

cloak-keys {
�aoAr1HnR6gl3sJ7hVz4Zb7�4YwpW�;
�ksWj9ImW0k20dO3cWm9Ej2g9RbdG�;
�phTl4EiF7n26sI0jDw2Dn1c6RlfK�;
};

Next to set the final few details. Change:

kline-address �set.this.email�;

To something like:

kline-address �phil@pchowtos.co.uk�;

And FINALLY you�re all done. Save this config file.

Now double click the icon that should have been created on your desktop during install. This should open the Unreal Interface. This means the server is running.

Now just connect to it from your IRC client.

And now for services�

Simply install anope with the installer, as you did with unreal.

Now go into the data directory and rename example.conf to services.conf.

Now we must do the config like we did with Unreal. Again best to open services.conf up in wordpad. Once this is done we will begin�

First of all, scroll down a little bit until you see a list of IRCDs. Just under this you will see:

#IRCDModule �unreal32?

Because we are using unreal3.2 in this tutorial you can just uncomment this line (remove the # from the front so it reads:

IRCDModule �unreal32?

Now scoll down to the �Remote server configuration� section. In this you will see the line:

RemoteServer localhost 6667 �mypass�

This must be changed to the details you entered in the link block for the unreal config file:

RemoteServer 127.0.0.1 7000 �PASSWORD�

PASSWORD being the password you entered in the unreal config in the link block.

Next scroll down to the Services identification and pseudoclient names section. In this you need to change 3 values:

ServerName �services.localhost.net�

ServerDesc �Services for IRC Networks�

ServiceUser �services@localhost.net�

These can be changed to something like:

ServerName �services.pchowtos.co.uk�

ServerDesc �Services for pchowtos�

ServiceUser �services@pchowtos.co.uk�

Next scroll down to: NetworkName �LocalNet�

Change this to your network name you entered in the Unreal config e.g.:

NetworkName �PchowtosNet�

Next scroll down until you see:
These are to do with encryption and MUST be changed. You must first remove the #s from the beginning of each line and replace the 7 digit numbers with other real numbers (no 0s at the start). e.g.

UserKey1 8362804
UserKey2 1387025
UserKey3 9693746

Now scroll down to: SendFrom services@localhost.net

Replace this with a real mail address e.g.

SendFrom services@pchowtos.co.uk

Now scroll down quite a way until you see:
#ServicesRoot �dengel anope�

This gives the registered nicknames of those who are services roots. Services roots can do everything on the net. You first need to uncomment this line by removing the # and then replace dengel anope with the nicks of the services roots. Note that svsroot privs will only be given once the net is started up and the people have registered their nicks. e.g.

ServicesRoot �dave jim�

And you�re all done! Now you need to start the services by double clicking the icon that should have been created on your desktop. If this just opens and closes a black window, as it does with me, you will have to run them via cmd.

To do this, go to start and click run. In the box type:

cmd

Now press enter. This should bring up a black screen. In this type:

cd �PATH TO ANOPE�

This is most likely c:/program files/anope, so you would type:

cd �c:/program files/anope�

Note that on Vista, this will be �c:/Program Files (x86)/anope�.

Now press enter. Then just type the word anope. This should start anope. You will not get any physical messages or interfaces. The cmd screen will just look like it has frozen. Just minimize this window and go to your irc network.

Once services have started you should see them join the network if you are opered up.

Now go play!

As I said this tutorial is to get an IRC server working. You may read through the config files and change some of the options that take your fancy in order to make the network exactly how you want it.

Once you have made a change to the unreal conf you must be connected to the server and opered up. You can then just type /rehash to reload the config file. If you edit the services conf you must be a services root and type /msg operserv reload.

If you want the /os /cs /ns etc. to work you must include the aliases file in the unreal conf. Open up the unreal config file and find the lines which say:

include �help.conf�;
include �badwords.channel.conf�;
include �badwords.message.conf�;
include �badwords.quit.conf�;
include �spamfilter.conf�;

Add to the end of this:

include �aliases/anope.conf�;

This will allow you to use /ns /cs etc.

Note: Due to the way Anope was compiled for Windows, some of you may get the following error when you try to start it:

This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. or The system cannot execute the specified program.

This can be fixed by going into your anope directory, finding the file called anope.exe.manifest and replacing it with the version which can be obtained by clicking here. Many thanks to therock247uk for compiling that one [12-Aug-2009]. All of the files from therock247uk�s Anope compile can be found here or if you want them all as a zip, they can be found here.

And we�re all done here. Hope this tutorial helped you  Have a nice IRC day!