Using fserves

Fileservers in mIRC are usually hosted as a dcc session, where the server attempts to dcc chat you (the client). In this dcc chat session, you may enter certain commands to navigate around the server (which just is a limited part of the server's computer). The commands used in a fileserver are very similar to the commands used in DOS, if you ever have used it.

How do I find and enter a Fserve?

Well, first off, be aware that mIRC in general, and fserve's in special, have NOTHING to do with specialized file exchange software like P2P programs such as Kazaa or Napster. mIRC is a chat program that incidentally has capabilities for exchanging files. Because it's not the foremost purpose of IRC, there's no centralized database of fserves and files available, no multipeer 'supernode' network where you download a single file from multiple people at a time, and not necessarily any way of getting a file you were getting from a specific person, from somebody else if that person should sign off.

With that in mind, we can continue. First, you need to join a channel where fserves are likely to be. Be it a mp3 channel, pic trading channel or the like, find it (by using /list *topic you're interested in*, for instance /list *vacationpics*) and /join that channel (for instance, /join #spainvacations). Once you're there, stop a little and just watch what's going on.

(Many fserves now incorporate an @find command to locate files before entering the server.  If you wish to locate vacation pics of spain you may want to try @find vacation*spain or @find vacation spain in the channel.  Fserves employing the @find feature will then send you a message listing the files they host matching your inquire.  DO NOT ABUSE THIS FEATURE, spamming a channel can and most often will result in a kick and/or ban as well as bogging down fserves who have to process your request.  If you do not get a result right away, change your request, or there may not be any matching files.  NOT ALL CHANNELS ALLOW OR USE @find commands, please check before using


You'll most likely see several people sending messages that says something like

<@XXXXX> File Server Online Triggers:«/ctcp XXXXX !blahblah» Sends:«2/2» Queues:«12/15» Current BW:«19.9 Kbs» MOTD: -= Movies/Eps in #thischannel - Star Wars: A New Hope - Divx WM2K3 Optimized =-

<+Leto> File Server Online Triggers!Leto» Sends:«1/5» Queues:«0/10» Current BW:«20 Kbs» AQT:«No Wait» MOTD: -= Looking for TomTom Navigator 2 maps of Mars. =-

 These messages are advertisements for the fserve, and means that that person is running a fserve. If the advertisement is running, the server has open slots (the number of slots total mean how many people can be on the fserve at the same time, one open slot means there's room for one more person) and you may try to enter it. If a person is not running an ad, he's most likely not running a fserve or haven't got any openings at present, so do NOT attempt to trigger his/her's fserve until you see the ad (for reasons explained below).

DO NOT ATTEMPT TO MSG THE FSERVE the !trigger, get or dir commands, etc.  Triggers only work from either /ctcp or in the channel. Fserve commands only work when used in the dcc chat with the server.

You enter it with whatever trigger that server is using, usually the advertisement will announce this as trigger, and the trigger word usually looks something like ”!Leto” or “/ctcp XXXXX !blahblah. To access the fserve, simply type the trigger word in the channel or /ctcp the trigger (this will not be shown in the channel but will send the request directly to the fserve). ONCE. Typing it several times does nothing and is very annoying for people in the channel, as well as causing some little extra strain on the server as it will automatically check if there are open slots every time you type the trigger word. So type it once every minute or so, that is more than sufficient. If the fserve has an open slot for you, it will now attempt to initiate a dcc chat with you, accept this chat and you'll enter the fserve. If it doesn't have an open slot, you may get a notice saying the fserve is full, or no notice at all, depending on the script used by the server.

What do you see when you enter the fserve?

Well, again depending on the fserve script, you may be dumped straight into the server, or you may see a welcome message then the comand prompt, or you may have a welcome message that prompts you to type something (typically Rules, for one of the most common fserve scripts, Panzer) in order to grant you further access. Just read the welcome message and don't stress out, you are already accepted on the fserve and you won't be kicked out unless you break any of the rules on the fserves, which means you've got a yet better reason to actually read the welcome msg. Some scripts (again, Panzer) has an option where it does not let you enter the fserve itself unless you actually type Rules first. Once you've cleared out this, you should have a command line prompt ready for you to enter on, and you can begin your fserve session :)

How do I USE the fserve then? How do I get the files??

As before mentioned, using a fserve is similar to using DOS in several regards, the commands are basically similar, so if you've ever used DOS, you'll know what to do. You will not be able to go to a higher-level folder than your root folder (the folder you enter when you first enter the fserve), and some fserves also have other folders set as unavailable. The commands for using the fserve are as follows:

  • Dir: (Directory) Lists the content of the current folder. You may also use ls to get a column-formatted list.
  • Cd: (Change Directory) Changes folder. Use cd foldername to enter that folder (must be a folder within the folder you're currently in), or cd .. to leave the current folder.
  • Get: Retrieves a file (dcc sends it to you). Usage get filename.ext, for instance get volleyball01.jpg. Many servers operate with a ratio, which means the number of bytes you are able to download (get from the server) for each byte uploaded to the server. If the fserve is ratio-based and your credit (the number of bytes available for you to download with) is too low, you need to upload some files to the fserve, you do this by dcc sending the files to the nick of the fserve owner. If he/she has stated certain files he want/doesn't want in his/her's rules, you should obey this. Most fserve owners check what is being uploaded and may kickban you out of the fileserver (and out of the channel, if they're channelOp's) at any time if you break the rules. If you have available credit and all that, you may now download the file you wish.
  • Read: Reads a txt (text) file, what this command practically does is to /play it to your chat window, so you can read the contents of the text-file in the chat window. Read is not limited by available credits. Some fserve owners does not allow the use of 'read' if they offer mainly text-files and are ratio-based. Usage read filename.txt.
  • Help: Gives you the available help in the fserve, some fserves have more help than others, but they all have some help. Plain help gives you the available help commands, help command (for instance help read) gives help on the command specified.
  • Exit: Ends the fserve and the dcc chat session. Dependant on the fserve script used, it may or may not keep your credits so if you return at a later time, you will still have your credits available to download with.
  • Queues: This command will list where your send is in the queue, how many files you need to wait behind before yours are sent


Trouble getting files….. This is often caused by the dcc ignore setting (DCC -> options -> Folders -> DCC Ignore) this should be set to accept the file type you are trying to get (most people just set this to disabled) do not check the turn back on in (blank) min, this will require you to disable the ignore each time you want to get a file.

Routers/Firewalls may also cause problems but will not be covered in this file at this time


In addition, the fserve owner can see what you type (the commands you type, as well as any other text), so you may ask him for help and hope he's paying attention. Or even /msg him privately, though some people don't appreciate that. The most important thing to remember is to use your head and don't try to rip anybody off, if you do you'll quickly find yourself banned from all fserves in that channel, and often also in other channels. That is after all what you do not want to happen :)

This tutorial taken from with permission(kinda) and changed to add /ctcp triggers, @find, dcc ignore,  and Queues


For help with setting up your own fserve, refer to the distributor of the script or program you are using as each script is different.

Common fserves for Windows are;



Garnaxbot- (BSD, SunOS, Linux, and Windows)