Leeching for Noobz (Properly)
This guide was made to help anime fans like you. It's also made to help me, because I don't have to teach you step by step (hehe I'm lazy). But you can't blame me, I've taught more than 20 people (around 200 now) before I decided to write this. I'm sure if more than 2 people ask you how to leech after you've read this, you wouldn't want to anymore. That's when you can send them this.
After reading this, you will be an official leecher and be able to enjoy downloading new releases of anime efficiently using IRC. This guide may seem long, but you do not need to read all of it to be able to leech. The only section that is pretty much mandatory are the file server sections, and maybe the XDCC section for channels that use bots for new releases. You do not need to read the other sections in order to leech, but knowing about them will help you, and make leeching more efficient. Have fun leeching!!
If you got this guide from somewhere other than my website, it is on my webserver at http://www.kasshin.net/Leeching_For_Noobz.html if you want to link to it.
To learn how to serve files, read my other guide about it here.
Setting Up mIRC
What is a File Server?
File Server Commands
Basic File Server Walkthrough
Setting up mIRC:
1) Make sure DCC Ignore is turned
off inside the DCC options.
2) Uncheck turn back on in: so that mIRC doesn't try to turn ignore back on.
3) Go to your Options, select the DCC tab, and select Autoget file and for the if file exists: part, select Resume.
When you first receive a file, select the option that makes it so that the popup message will not show up again. Auto-accepting files is a must on mIRC, or you would have to /dccallow many many people in order to get what you want. Auto-accepting means that you don't have to be at your computer, or at mIRC to receive the file. With that done, now you are ready to use a File Server.
What is a File Server?
A File Server is a place where one can download files like Anime off of someone's Server. A File Server in IRC is used by typing a trigger to enter the server, then one can request files for download, if possible.
The system of downloading files is that the server sends a certain number of files to a number of people, and if that number is reached then the next request becomes queue number 1, and the next one is number 2, and so on. Queue number 1 starts to send the file to the user when one of the sends finishes, and Queue number 2 receives the file requested after the next send finishes (could be the queued file). Maximum number of sends and queues vary depending on the file server. In some cases, the number of queues may be over the number of sends, because of priority. Priority sometimes lets a user go over the number of queues, or lets them skip other people's queues. Priority is usually only given to friends of the file server's host, or to Operators or Voices. (+o or +v)
After joining a channel, the first thing to do is type !rules. If typing !List is allowed, then type !List to display a list of File Servers that are currently Active in the channel. If the channel is a large one, (most popular ones are), you are most likely to get many, many responses. In small channels, say around 30 people, not as many will show up, and it is easier to see the ads.
Advanced: Typing !list <user name> (don't put in the <>'s) will display the ad of the user only. This works in the sysreset and upp file server scripts and some others. Some scripts respond even if you type something after !list, but this filters out other sysreset / upp ads.
A typical File Server Ad will be like this:
-Kirika- [Fserve Active] - Trigger:[ !Trigger] - Sends:[2/2] - Queues:[17/20] - Record CPS:[67.2kB/s by Bob] - Upload Speed:[60.6kB/s] - Message:[- Come look at my stuff!!! -] - SysReset 2.51
In this case, one knows this is a file server because of the first section where it says Fserve Active. The way to get inside the file server, is by typing the trigger. Here, the trigger is !Trigger, shown in the second part of the File Server Ad. Triggers are to be typed in the channel in order to access the File Server. Triggers can be anything, even a whole sentence like "I screw donkeys for fun". Usually they have a "!" next to them, for the non-silent ones.
Some other scripts use File Server Online or Fserve Online or something like that. File Server Ads usually display this and the trigger information. Sometimes they also tell you a bit more information, like the Sends and Queues.
Sends is the number of uploads the File Server allows, and how many are sending at the moment. In this case, there are 2/2 sends, which means 2 sends running out of 2 maximum sends. This means that one would have to wait for another send to be available, if the fileserver has available queues.
Queues is the number of people waiting, out of the maximum number of people allowed to wait. In the example there are 17/20 queues, meaning 17 people in line out of 20 maximum people in line. Requesting a file at the moment would result in waiting in queue 18. That means one would have to wait for the 17 people to finish their downloads to start downloading from the file server. The amount of time to wait depends on the file server's upload speed, the type of files it is serving, and how fast the first queues finish downloading.
File Servers also usually have a message of some sort; in this case it is Come look at my stuff!!!. Some messages describe what is inside the file servers, some advertise what the File Server's owner is requesting, and some (like the one above) serve pretty much no purpose at all. There are also many other things the Ad can contain, like the Record CPS (Highest upload speed recorded), Upload Speed (How fast the server is uploading at at the moment), and many others. The last part of the Ad, (SysReset 2.51) is the script's name given by the programmer, and the version. Each script functions pretty much the same, but most of them look different from eachother.
If a file server has two triggers, they are usually seperated by an "&". Some triggers are silent and begin with /ctcp. They are usually in the format [/ctcp <file server> <something> ] ( Exclude the < >'s and the [ ]'s when typing the trigger ). An example would be /ctcp Kirika anime fserve.These do not show up on the channel, and only the user and the file server know that the user typed it. Type them the same way normal triggers are typed. But to be safe, one should type them in the Status Window. This is because some channels kick/ban users that type the triggers wrong Eg. ( [/ctcp Kirika Anime ). That is an example of typing the trigger with the ['s.
In some cases, file servers are behind a firewall. They will prompt the user to type something in, and the user must type it in before he/she can access the file server or receive files. The "something" is usually /dccserver +sc on 59 or something close to that. After typing it, the user should be able to get into the file server. Sometimes if typing the firewall stuff doesn't work, it is not the user's fault, but the server's. So do not freak out if it does not work every time. Typing the /dccserver stuff or the file server trigger again sometimes seems to help. If you are behind a firewall yourself, usually this means that you probably can't connect to that server. Try a different file server.
File Server Commands
Once the user is inside the File Server, there are a number of commands to use in order to download / queue the file desired. The user is actually accessing the File Server's Owner's hard drive, and requesting files from it. This is like using DOS, so DOS users should have no problem with this.
Typing Dir will display a list of folders available. Users usually start in a root directory ( / ), and get go to a new directory by typing cd <new directory> (without the < >'s ). One can tell the difference between a file and a folder by seeing if the object has an extension. Objects without an extension, and with all CAPS, are folders. One can explore it using the cd <directory> command. Objects with extensions are files, like [ thisisafile.ext ].Those can be downloaded or queued, by typing get <file.ext> (without the < >'s ). E.g. [ get inuyasha_100.avi ]. Always type the exact file name with its extension, or else it will not work. Copying and Pasting comes in handy here. Below is a list of the commands available:
|cd <directory>||changes to another directory within the current one. (don't include the < >'s when typing)|
|cd..||goes up a directory (sort of like "up one level" in windows)|
|dir||lists the files in the current directory, from top to down|
|ls||wide directory listing.|
|get <file.ext>||asks the server to DCC Send / queue the specified file. (don't include the < >'s when typing)|
|say||send chat messages to all other users on the server.|
|sends||displays server send status|
|stats||displays current server statistics.|
|swap||allows queues to be swapped. (some servers may have it disabled)|
|queues||displays server queue status.|
|users||show users on server.|
|clr_queues||removes all of your queues.|
|clr_queue N||removes the queue in slot #N.|
|exit||terminates the connection.|
A list of commands that the current File Server uses can be obtained by typing "help" when inside the file server. Most servers use cd <directory>, dir, ls, get <file.ext>, and clr_queues. The command for going back up a directory is cd... This is the direct opposite of cd <directory>. After one is done queue-ing or requesting files, one should close the window the file server is in, and wait in the channel for the file to be sent. If you see the message "DCC Server Session Terminated", don't freak out, that's meant to happen. It makes sense not to have an extra window on your channel bar, doesn't it?
Basic File Server Walkthrough:
If you can't figure it out from the above, read this.
1) First, find out which files are available. Type dir for a list of files.
2) If you see a file that you want, great! Proceed to step 2a. If you don't, but there are directories, (stuff that doesn't have an extension) proceed to 2b. If you don't want any of the files listed and there aren't any directories listed, go to step 2c.
2a) Type get <filename>.<extension> (leave out the < >'s) to download / queue it. Proceed to step 3. Eg. get Inuyasha_100.avi
2b) Go inside the directory. Type cd <directory name> (leave out the < >'s) to go inside that directory. Once you're inside the new directory, repeat step 1 and 2. Eg. cd Inuyasha
2c) It appears the file server doesn't have the file(s) you are looking for. Type cd.. to go back up a directory, and try another folder. But, if you are already in the root directory of the file server and you can't go "up one level" anymore, that probably means the file server doesn't have what you are looking for. Proceed to step 3.
3) Close the file server window. If you found the file(s) you were looking for, great! If the file is already sending, even better. But if you are queued, just wait inside the channel you found the file from, for it to send. For the unfortunate users that haven't found what they wanted, try another file server.
Some, NOT ALL, file servers use something called @find. This is something a user types in the channel, ( @find anime ) and file servers with @find enabled will search the file server for files matching the name "anime". If something is found, the server will message the user, or /notice you (shows messages in your active mIRC window to you and you only), the names of the files found, how many found, and the information of the file server that contains the file(s). This is a really handy feature, since the inexperienced user will have no idea where to get a file he/she wants.
But, some channels do not allow @find since it really floods the file servers and the channel. So before any use of @find, type !rules to find out if it is allowed. The bad thing about @find is that many file servers don't have it enabled, and the user is only searching file servers that do. File Servers that do respond usually tell you the trigger for it, and the sends and queues. DO NOT type the trigger inside the PM window the server messages the user with, especially if it is a non-silent trigger. In doing so, the user is actually messaging the file server, and is very unnecessary and annoying to the file server. Doing so may result in a ban from a channel or file server. A safe thing to do is to always type triggers in channels. This would be a good habit to pick up.
TDCC's, are triggers that get a user one specific file. They are much handier than file servers for getting one file, and only require the user to type the trigger in the channel or status window (for ctcp triggers), and they will receive the file, or be queued for it. Using TDCC's does not require any file server browsing, and is usually used for new releases.
Here is an example of a TDCC ad:
-Kirika- [TDCC Active]- Trigger:[/ctcp Kirika How To Leech] - Description:[ How to Leech for Noobz, beginner's guide ] - Size:[5.2MB] - Sends:[3/5] - Queues:[0/10] - Record CPS:[67.2kB/s by Bob] - Upload Speed:[45kB/s] - Requests: - SysReset 2.51
TDCC Ads look pretty much just like File Server Ads, except in the first part TDCC Active is displayed. That signifies the ad is a TDCC, and is not a file server. The trigger is /ctcp Kirika How To leech; typing the trigger will result in downloading the file advertised. TDCC triggers also display how big the file is (size), how many times it has been requested, (Requests), and a description instead of a message, usually about the file being advertised. In this case, the file being advertised is this html help file, as described in the description.
XDCC's are sort of like TDCC's, except they have more than one file, and are always silent. There are generally two types of XDCC, the /ctcp kind and the /msg kind. The /msg kind is usually an iroffer bot, and is there for XDCC's only. Usually XDCC bots are on really fast connections, like T3 or OC 48 or whatever. Bots in anime channels usually have a tag next to their name, like A-Kraze|Bot. That is usually the way to tell bots from other users.
The way to view the "packs" being served on a bot, (files being served), is to msg them with XDCC LIST. This can be done by either opening a query with them, (double clicking their name) and typing it in the new window, or by using the command /msg, like [ /msg A-Kraze|Bot XDCC LIST ]. There is another way, by typing XDCC LIST in the channel. But, this way is very unsafe since most channels do not allow it because of the flooding, since there are many many bots in each channel. Either way, a list of packs being served will come up, like this:
-A-Kraze|Bot- ** 7 packs ** 20 of 20 slots open, Record: 530.2KB/s
-A-Kraze|Bot- ** Bandwidth Usage ** Current: 0.0KB/s, Cap: 5000.0KB/s, Record: 790.5KB/s
-A-Kraze|Bot- ** To request a file type: "/msg A-Kraze|Bot xdcc send #x" **
-A-Kraze|Bot- #1 10x [174M] Inuyasha 85
-A-Kraze|Bot- #2 2x [157M] Hack Sign 26
-A-Kraze|Bot- #3 0x [184M] Ai Yori Aoshi 22
-A-Kraze|Bot- #4 4x [173M] Tokyo Underground 20
-A-Kraze|Bot- #5 2x [182M] Samurai Deeper Kyo 11
-A-Kraze|Bot- #6 11x [204M] Gatekeepers21 OVA 03
-A-Kraze|Bot- #7 30x [192M] Chobits 26
-A-Kraze|Bot- ** Brought to you by Kirika **
-A-Kraze|Bot- Total Offered: 2089.4 MB Total Transferred: 209.8 GB
In this ad, there are 7 packs available. The 7 are listed from #1 to #7. the 10x and 2x stuff is how many requests the specific file has gotten. the [174M] and [157M] stuff is how large the file is, with M meaning megabytes, and K meaning kilobytes. The stuff after the file size is the description of the file. Sometimes a filename instead of a description is put here. To get the file desired, like maybe pack number 3 which is "Ai Yori Aoshi 22", type /msg A-Kraze|Bot XDCC send #3. The file will be queued or sent after you type the trigger, much like a TDCC. The file size is displayed next to the file, and is a good way to check if the file downloaded previously is complete. At the bottom where is says "Brought to you by Kirika", that is where the information of the bot owner goes. In this case the owner is Kirika, but in some cases a channel "owns" the bot.
Ctcp XDCC's are pretty much the same as bots' XDCCs, but are usually used by slower connections, (cable, dsl) and use /ctcp instead of /msg. They are part of a File Server script, and could also use the same queues and sends "pool" as the file server. The usage is pretty much the same as shown by the following:
-KiriKa- [#1] [199.6MB] - Inu Yasha - 85 [7 Gets]
-KiriKa- [#2] [178.7MB] - Tokyo Underground - 20 [3 Gets]
-KiriKa- [#3] [174.8MB] - Ai Yori Aoshi - 22 [3 Gets]
-KiriKa- [#4] [196.2MB] - Samurai Deeper Kyo - 11 [2 Gets]
-KiriKa- [#5] [169.2MB] - Chobits - 26 [1 Gets]
-KiriKa- [#6] [177.6MB] - .Hack//Sign - 26 [2 Gets]
-KiriKa- [#7] [119MB] - G-On Riders - 05 [7 Gets]
-KiriKa- [#8] [199.1MB] - Gatekeepers21 OVA - 03 [4 Gets]
-KiriKa- [#9] [326.7MB] - Hack Liminality (OVA) - 01 [52 Gets]
-KiriKa- [#10] [138.6MB] - RahXephon - 26 [3 Gets]
-KiriKa- Usage: /ctcp KiriKa XDCC GET ME #<pack number>
Ctcp XDCC's look pretty much the same as bot's XDCCs, and are used in a the same way. Typing /ctcp Kirika XDCC GET ME #3 would get file #3. The only difference is that in here the syntax is a little different.
Most file server scripts come with a request ad script, where the file server's owner can set up a request ad. Request ads are ads that are asking for something, sometimes files, and sometimes people who can help the server's group. Most request ads respond to !request, and will come up like fserve ads and TDCC's and XDCC's. If the user has the thing the file server's owner wants, he/she should send it to them, as it would be a great help to them. Some channels do not allow request ads, or does not allow non voices or ops to use them though.
Sometimes request ads aren't really requesting anything. This is because the user is probably using it to display something to tell the channel periodically, if their script does not have something else that does that. This may include information about the channel, like a web site. At new releases, some operators put the triggers of fast senders of the new release on the trigger, informing all the channel users about them. Those, are quite useful to leechers. : )
/msg me directly with any comments, suggestions. Direct your questions to the channel please. Other leechers can help you.
Send me comments, ideas, whatever, to email@example.com
AIM: Kasshin sama