IRC Downloading

A tutorial to help users download files using IRC.

How to download files using IRC

This explanation will assume the user knows what mIRC is, and the basics of using it. If this is NOT the case then please go Download mIRC, and install it. Next go to IRChelp.org for general help. Return to this tutorial when you are familiar with connecting to an irc server and joining channels.

There are a number of methods to download files using IRC, the common ones are XDCC, and DCC. DCC usually uses what is called an fserv to allow you to see what is available, and then allow you to get what you want. XDCC while somewhat similar, will list its contents as PACKS and rather than getting a filename, you get a pack number.

DCC Fserv

In the channel window type !list. This will give you a list of the Advertisements for the fservs in channel. These ads will look similar to the following example:

[09:57:15] *gimboid[serv]* File Server Online Triggers:«/ctcp gimboid[serv] !tv-1 /ctcp gimboid[serv] !tv-2/ctcp gimboid[serv] !tv-scifi/ctcp gimboid[serv] !tv-british» Sends:«2/2» Queues:«20/20» Accessed:«28769 times» Online:«0/4» RCPS:«50.3 Kbs by somenick» Served:«819GB in 2502 files» Current BW:«47.2 Kbs»

You should be interested in the TRIGGER information in that ad. In this case, as is the case with many, if not most servers, there are multiple TRIGGERS. In the above example the triggers are in BLUE for easy identification. Triggers will often give you a hint on what you will find on the fserv using that trigger. In the example, the trigger /ctcp gimboid[serv] !tv-scifi will present you with Science Fiction shows, if you are looking for The Simpsons, using that trigger would not be very productive. Make a choice on which trigger to use then either type the exact trigger, or better yet, copy and paste the desired trigger into the channel window. /ctcp gimboid[serv] !tv-scifi Be careful that the / is in front of the ctcp, with no other characters preceeding it, and that what you have entered is what is in the ad. When you press enter, you should then be connected to the fserv.

Once connected, you are now in the fserv window. There are a group of commands that are valid while in the fserv window. If you are not familiar with the fserv commands, type help and you will be presented with a list of commands. Different fservs have somewhat differing commands, and will present them differently, but for the most part they are the same, and the objective is always the same in an fserv, to download a file. Using the example fserv these are the commands.

  • (cd,Change your current directory [cd <directory|..>])
  • (dir,List all the files in current directory)
  • (ls,List all the files in current directory [wide])
  • (get,Gets file from the file server [get <filename>])
  • (read,Reads file from file server [read <filename>])
  • (stats,Shows file server statistics)
  • (who,Shows a list of who is connected)
  • (sends,Shows a list of current sends)
  • (queues,Shows a list of waiting queues)
  • (clr_queues,Deletes all of your queues from server)
  • (terms,Shows you the terms you accept for using this file server)

Type dir and you should get a list of the files or folders in the home directory of that trigger. If what you see are files, you can get them, if they are folders then you need to do a cd <foldername> then another dir to list the files. Once you get to the file you want, type get <filename>. You must type the exact name or copy and paste the name. Be aware the filenames usually will display in the following manner. enterprise.s01e01e02broken.bow(ws.ac3.dvdrip.xvid-medieval).avi 701 mb The filename does NOT include the 701 mb. If you get a message about the file not existing, you probably entered the filename incorrectly. Do it again. The command to get the example file would be get enterprise.s01e01e02broken.bow(ws.ac3.dvdrip.xvid-medieval).avi.

There are some things to be aware of when using fservs to get files, it takes patience. The fserv will probably have only 1 or 2 sends, and there will be a QUEUE of other users waiting for their file to be sent. The file you are getting will probably not send right away, but will go into a queue. When you enter an fserv there is usually a message line that will tell you the status of the sends and queues. Current Queue Status:«20/20» Your Personal Queue Status:«0/1» If you see status like that, your only reason to be in this fserv is to look around, because even though your personal queue status is 0 of 1, the fserv queue status is 20 of 20 so there are no free slots for you. If there is a free queue slot, or a free send slot, then when you issue your get command, either your send will start, or your file will go at the bottom of a queue and you must remain online, in channel to get that file. Depending on the size of the queue, and how fast the fserv can send, the process to get a single file can take days before your file sends. Remember it requires PATIENCE.

XDCC

Using xdcc will usually get you the file in a shorter time. The disadvantage is not having much to choose from. The normal method of finding out what is on an XDCC is to issue the following command: /msg <NICK> xdcc list. Most of the FAST xdcc bots in #tv-hub do not respond to this command, so an alternative method has been provided. /msg <botnick> xdcc send list will trigger the bot to send you a text file of its packs. Find the pack you want in the text file then issue the appropriate command. /msg <BOTNICK> xdcc send x where x is the pack number you want, and <BOTNICK> is the nick of the bot where the pack is. There are also queues on xdcc bots, but the wait time is rarely more than 3 hours and often less than an hour. You can also obtain pack lists from the following link. PACKLIST