This page details the process of downloading from IRC file servers. This guide is intended to be used with mIRC, since it's by far the most used IRC client. You can apply the information to other clients if you want to, it just requires you to actually learn about your client.. (For some reason, this seems to be exceedingly difficult for some people)From the following list you can jump to any topic you want within the page:
1. Setting up mIRC for downloading
2. First things to do when joining a channel
3. How to find and use file servers
4. Do-not's with file servers
5. General stuff about IRC
*Note that this guide assumes that you already know how to connect to an IRC server and join channels. I am not going to discuss those settings here.
First task is to set up mIRC so that it can download files without bugging you.
Open the settings dialog (file -> options) and go to the DCC tab.
In this dialog you need to turn on auto-get
*Note: even if auto-get is enabled, there is a chance that mIRC will ask you to accept the first download anyway, so keep sharp. It doesn't ask after the first one.
Also select Resume from the pull down menu to allow mIRC to automatically continue download in case it gets disconnected.
The other settings in this dialog aren't relevant in receiving files. You might want to turn on Auto-accept for DCC-chat to avoid having to click "Yes" all the time.Next part is the folders dialog under DCC.
In this dialog the important part is DCC ignore. You can set this to whatever you want, but be sure that you add/remove the file types you want to download. The options for Ignore are "Ignore all except...", "Ignore only..." and "Disabled".
-Ignore all except: If you select this option, check that the extensions of files you want to download (e.g. *.avi) are in the other pull-down menu's list.
-Ignore only: In this case, you need to confirm that the file
types you want are not in the other pull down menu.
-Disabled: Ignore is disabled, and your mIRC accepts whatever files are sent to it.
This menu also allows you to edit the destination folder where you want your downloaded files to end up. Just press edit under DCC Get folders.Last part in the options is the Server part under DCC.
Just put everything here as it is in the picture. This is a configuration that works.Return to the top
When you join a channel, there are few things you should do:
1. Read the topic. Topics usually contain useful information about the channel, it's rules and some such. If you see something like "!rules" in the topic, be sure to write it. It's most likely a trigger that tells you what you can and what you can't do in the channel.
2. If (and only if) there is no rules trigger, ask what you are allowed to do. Going agains channel rules will just earn you a kick. Don't blame others for your ignorance.Return to the top
In order to use file servers, you need to find the file server advertismements. How this is done, depends on channel. Some allow !list command, some don't. Channel rules probably have a note if !list is not allowed. If you can use it, at this point type "!list" (without quotes, of course). This will give you a list of file servers on the channel. There might be also some ftp servers, but I'm sure everyone knows how to use ftp, so I'm not going to talk about them :P. If list is not allowed, you need to wait for an ad to appear.The file serve ads are usually as follows
1. Trigger: this is what you type in order to get into the file server. Be sure to copy it exactly. If the file server can't accept new users at that time, it will give some kind of notification in your status window. (if you copy/paste the trigger, remember that mIRC copies it to clipboard with just highlighting. Do not use ctrl or ctrl+c when copying. Also check that you didn't copy any color or other codes before pressing enter). In this example the trigger would be "/ctcp Tsukushi^^ Unlicensed anime" (again without quotes).
2. Sends and Queues. When using file servers, your file requests are stored in a queue slot until a send slot is freed. You might want to read this part of every fserv ad, because if there are no free queues, you can't get a file from the server.
3. /dccserver: Some file servers that are behind firewall have this option. Use the
command that's given to allow the server to send you files.
*Note: If you use multiple different /dccserver commands, only latest remains in effect.
*Note: If you are behind firewall also, there is a big possibility these servers don't work for you.
Inside this window use the following commands:
help: gives a list of the commands usable at the fserv
dir or ls: lists the files and directiories. Directories are displayed in capital letters on most cases, while files have some extension.
cd: changes to a directory ("cd directory". You can get back to the main directory by using "cd..")
get: queues a file for download (e.g. "get example.txt"). Don't include the file size in the command line
sends: displays information about on-going sends
*Note: some servers may have this and queues hidden. repeating the command isn't going to help in that case
queues: information on queues. Also shows where your queue is in the list.
clr_queues: removes your queue from the list
clr_failqueues: removes your failqueues
*Note: failqueues are present on servers that support them. They're used for resending failed sends and giving priority queues to other people
1. Do not camp. Camping means trying to keep the dcc chat open by typing sends or queues repeatedly. This is considered to be very bad (not to mention annoying) and will earn you a ban from the server most likely. Also, the file server chat is supposed to close! You do not lose your queues when this happens. Proper way of exiting a file server is to use command "exit" to close the chat once you have queued.
2. Do not hammer. Constant usage of the trigger to check queues or sends is also considered very bad. 30 minutes is the minimum time between attempts. If the server has a send that ends sooner, write up the time, and try again only when it should have ended. Also, using the trigger multiple times in a row is stupid, it will just flood the server so no one can access.
3. Unless the file server clearly states that its owner can send on request, do not message him/her about sending you a file. That's at best irritating.
4. Do not use auto-queueing scripts. These take away other people's chances to get into queue, and generally tend to hammer the server too much. I personally shitlist everyone I see using those scripts for auto-queueing purposes.Return to the top