AroFxp professional Helpfile for Dummies

Version 1.4
/o\ By the best Juice in the world /o\
1. INTRODUCTION
For AroFxp you need:

1. Tzftp – ftpclient
2. mirc
3. AroFxp Professional

2. INSTALLATION
2.1. Installation of Tzftp

• Installation of the win32 version

1. Put all the Tzftp files in any folder in local or on a shell and run tzftp.exe
2. When you start it for the first time it will give you your identity key which you then copy to the
author of Tzftp and he will then give you a generated key which you will enter
3. Choose a password by which the site database will be crypted (if you already have a crypted site
database you enter that password in Tzftp)

• Installation of the linux version

1. Put all the Tzftp files in any folder in local or on a shell

2. chmod +x tzftp and ./tzftp
3. check 2. and 3. of the win32 version (it’s the same)

!Tzftp listens on port 16666 (unless you specify otherwise in config.ini). You can connect to your
ftp client via the tool (check ftp client settings) by connecting to host:port. If you are running Tzftp
on your local computer you have to connect to 127.0.0.1:16666.

2.2. Installation of AroFxp Professional

1. Unzip race2.zip in any folder
2. Download the latest Arotool.exe and overwright the existing one (!this is how you can constantly
update the tool…because only the .exe changes so be sure to update regulary)
3. Put Arofxp.dll and Arofxp.mrc from your tool/mirc folder to the root of your mIRC
4. Open mIRC and run /load -rs Arofxp.mrc (this will transfer every line from selected sitebots in
mIRC to AroFxp Professional)

3. Setting up the tool

3.1. Site settings
Add all your sites and configure them properly.
3.1.1. General settings

1. Sitename: name of the site (same as in Tzftp)

2. Location: This is for your consideration only for example: .se, .nl, .uk…
3. Rank: From 0-99 (0 means the best site): You can have more sites ranked with the same number.
When release comes it will fxp to the best ranked site first (from the best ranked site that has the
best speed to it). If more sites have the same rank it will fxp amongst the sites that have good speed
between each other.
4. Max pretime: maximum pretime (in minutes) that is allowed on the site
5. Min Speed: if speed is below xx kb/s then it will stop fxping to that site after the file is finished.
If you want to disable this option just set it to 0.
6. Site invite allowed: If enabled you can invite to the sites channel through this tool
7. Site is up: If unchecked, site is down and it will exclude it from the chain
8. Affils: Set affils so the tool will not race them on that site. Separate them by space
9. Banned groups: Set groups that are not allowed on the site. Separate them by space
10. Virtual Affils: If you have a site that has seperate channels for each section and you for an
example only trade mp3 (so you are only on the mp3 channel), but you can leech iso anyway by
setting virtual affils you can trade these releases from this site also (although you dont see the
announce because you are not on the channel the tool will know it can leech the release from this
site).
11. Store/update to/from siteDB: You can save your site settings and rules to our database so you
and other curries wont have to set them from scratch. In order to do that you have to enter all the
settings for central server in environmental settings.

12. Logins: This logins are not the same as the ones in Ftpclient settings tab. They tell the tool how
many times it can upload and download THE SAME (single) release to this site.

Example 1:

If on site A in general you have total:3, up:1, down:2 and GAME-RELOADED is released it means
that you are allowed to fxp this game from this site with 2 download logins at the same time but you
can only fxp this release to this site once (for example: X->A; A->B and A->C).
If it was total:5, up:3, down 2 it would mean that it is allowed to fxp GAME-RELOADED from 3
different sources to this site. (for example: X->A and Z->A and Y->A; A->B and A->C) and leech
from this site twice at the same time to some other two sites.

Example 2:

If on site A in general logins you would have total:3, up:1, down:2 and in ftp client settings you
would have total:2, up:1, down:1 then it would put two download releases to queue and start fxping
after the first is finished. So this would not be a good idea

Example 3:

If on site A you would have in general logins total:3, up:1, down:2 and in ftp client settings
you would have total:4, up:3, down:1 it could only fxp GAME-RELOADED on this site once. But
if there would be a PRE-flood and GAME2-RELOADED and GAME3-RELOADED would also be
released all 3 games could fxp to this site at the same time.

13. Constant Rank: If you don’t want the tool to change rank of sites (based on statistics of how
sites are fast…when releases are finished) keep this option enabled. If you have a lot of sites it is
good to disable this option and let the tool figure out which site is the best by looking at race stats.

3.1.2. Catcher

First you have to add all sections to the site and then configure each section separately.

!All the settings in this section are very easy to configure. The tool will find the
release/genre/pretime/complete by itself you only have to put in some words or part of words that
are typical (are always the same) for the particular announce (new-race, pre, pretime, genre,
complete line) that you are setting for.

• mp3 section
1. Newdir line: This is the line where the sitebot announces new races

!It is very important that you put the phrase for new announce and for the section in this line

Example 1:

<sitebot> NEW: VA-Melodic_Morning-2000-ELiA in MP3 by curry/group

Newdir line: NEW: MP3

Example 2:

<sitebot> [MP3] 0621/Eskimo_Joe-Breaking_Up-CDS-2007-WRE => from curry/group

Newdir line: [MP3] => from

2. Pre line: This is the line that announce PRE`s of affils

!It is very important that you put the phrase for pre announce and for the section in this line

Example 1:

<sitebot> ::==[PRE]==:: in [MP3] :::::>

Klubbingman_Feat._Beatrix_Delgado__Never_Stop_that_Feeling-(KSR020)-Vinyl-2007-DJ with a
total of 33.0MB in 4F
Pre line: ::==[PRE]==:: [MP3]

Example 2:

<sitebot> [MOD-pre] -> VA_-_Italo_Fresh_Hits_2007_2.0-2CD-2007-MOD

(40f/210.7mb/Dance/180kbps VBR)
Pre line: -pre] ->

3. Path on site: Path on ftp where section is located for an example: /incoming/mp3/

4. Race is allowed: If enabled it is allowed to race in this section otherwise it is affils only

5. Custom rank for this section: On some sites some sections are better supported then the other
that is why it is hard to say that all sections should have the same rank on a site. You can for an
example have really good mp3 support and sucky divx support. That’s why you can also set ranks
for each section. If you leave it empty the rank of the section will automatically be the same as the
rank of the whole site.

!Incoming/archive dir, Genre info, pretime info and complete lines are not necessary to set up.

6. Incoming/archive dir has two functions:

• The first one is for Backfilling mp3s (the Backfill function in ctrl+r). They have to be both
incoming and archive because after a few days usually the daily mp3 directory is moved
from incoming to archive. You can set how the site writes directories by using YYYY(year),
MM (month) and DD(day). For an example if /incoming/mp3/2007-10-15 then you should
write /incoming/mp3/YYYY-MM-DD and /archive/mp3/YYYY-MM-DD.
• The second function is for making speed tests for the routing table (you can find more about
the routing table in section 3.4 of this helpfile). In order for being able to make speedtest
 you have to add a section called SPEEDTEST to each site. For “section” SPEEDTEST you
have to fill:

- path on site: This is the directory where on this site a file (for making speedtest) will be fxped
Example: /requests/speedtest

!make sure that you put a directory that has writing permission. If for an example you would put
/incoming/divx you probably don’t have writing permission and it wouldn’t work. On the other
hand if you use actual speedtest directory its not good if the site announces speedtests that users
make in the channel (because if you do speedtest with 20 sites it will show that on channel).

- archive dir: Here you put a path from which it will choose a file to transfer from when fxping
from this site to another.
Example: /archive/divx

!Leave incoming dir empty

7. Botnick: In here you type nick of the site bot that announces releases and of the bot that
announces pretime (!prebot is not necessary). You have to separate them by space: bot1 bot2
8. Genre info: From this line it will read the genre of the mp3 release (it uses this information for
fxping to site that only allows some genres. All sites don’t eaven announce this.

Example 1:

<sitebot> ( MP3!UPDATE ) curry!group uploaded first file on Man_On_Earth-

Something_Better-2007-MTD. Uploading some Progressive Rock from 2007 at 44100Hz in Joint
Stereo 210kbps (VBR V2) at 3.03MB/s.
Genre info: MP3!UPDATE

!You only need to put in a word or more words that are always announced when genre is
allowed. The tool will find the genre itself. ((MP3!UPDATE uploaded in) etc would also be
ok)

Example 2:

<sitebot> | NFO | 0621/VA-Facedown_Records_-_Something_Worth_Fighting_For(Trackfix)-

2007-MTD has 1 files of Hardcore from 2007
Genre info: NFO (also (NFO from) would be fine)

!If the genre is announced in the complete line then skip Genre info and just fill the complete line (it
will catch genre from there or from any other site)

9. Pretime info: From this line the tool will know how old the release is and on sites that the
release is a backfill it will automatically be deleted. This option is of course only possible if there is
a prebot on the channel.

Example 1:

<prebot> [ OK .:. VA-Facedown_Records_-_Something_Worth_Fighting_For-(Trackfix)2007-

MTD pred 3s ago ]
Pretime info: pred ago
!The tool will catch the time by itself

Example 2:

<prebot> PRETiME: VA-Facedown_Records_-_Something_Worth_Fighting_For-(Trackfix)2007-

MTD released 2 seconds ago
Pretime info: released ago

10. Complete: From this line it will read when the release was finished (this is important so the tool
knows how good support each site has - for ranking purposes). There are two Complete lines
because sometime the announce is different if one user completes the release or more.

Example 1:

<sitebot> ( MP3!DONE ) VA-Facedown_Records_-_Something_Worth_Fighting_For-

(Trackfix)-2007-MTD got uploaded by curry!group. It took 2s to upload 7MB in 1 files with
3.50MB/s average.
Complete1: MP3!DONE

Example 2:

<sitebot> [MP3] Andy_Farley-The_Killer_2007_Remixes-Vinyl-2007-USF =>

(2F/26MB/Trance/2007) (avg.1.20MB/s) at 22s by 2U/2G.
Complete1: [MP3] at by

11. Blowkey: You have to type it if you are connected to the tool via BNC (for that u also have to
set-up your PsyBnc settings

12. Test: Insert a real new line, preline, pretime line, complete line or genre line to test if your
settings are ok.

• Other sections

Same logic as for mp3, except that u leave Genre line empty!

Example for PSP:

<sitebot> (site|new) curry shoves Hot_Brain_USA_PSP-pSyPSP up our psp section.

Newdirline: (site|new) PSP

<sitebot> PSP-PRE pSyPSP drops Hot_Brain_USA_PSP-pSyPSP (25F/353.4MB)

Pre line: PSP-PRE drops

<sitebot> Hot_Brain_USA_PSP-pSyPSP was pred 12secs ago

Pretime info: was pred ago

3.1.3. Rules

!If in a list there is something allowed, everything else that is not checked is automatically banned
1. Group names: For making exceptions (allowing or banning) of some groups. For an example if
Live is not allowed unless it is released by 1REAL
2. Min. Year: Put minimum allowed year
3. Max CD: Put in maximum number of CD`s allowed
4. Sources: List of all possible sources
5. Countries: List of all possible countries
6. Genres: List of all possible genres
7. Allowed: Here you put rules that are allowed
8. Banned: Here you put rules that are banned
9. Skiplist with wildcard: For being able to allow/ban different words in releasename (like for
setting up Various artist settings)
10. Test release for rules: Put in a release and see if it is allowed by rules
11. Rules Test: here you can test if a release & genre is allowed

!You can add mp3 rules in two steps:

Example:

Lets say that site rules are:

-------------------------------------------------------------------------------------------------
- allowed soures: CD, DVD
- max CD = 3
- allowed year 2006+, allowed languages: English, Italian, Hungarian, Japanese
-------------------------------------------------------------------------------------------------

STEP 1: Set up rules for English releases

Put in Min year, Max CD, Sources (if all genres are allowed leave it empty)
STEP 2: Set up rules for Foreign releases

Put in Min year, Max CD, Sources and countries (if all genres are allowed leave it empty)
 • Imdb.com rules (for movie related sections: DIVX, DVDR, HDDVD…)

1. Genre: Here you can set allowed/banned Genres for the site. The data comes from imdb…you
can add genres in keywords/imdb/imdbgenre.txt. If you leave everything unchecked it means all
genres are allowed for this site.
2. Source in Releasename: Allowed/banned sources, which the tool reads from the releasename.
Everything that is not allowed (checked) is automatically banned.
3. Languages in releasenames: here you can allow or ban languages that the tool reads from the
releasename.
4. Language on imdb.com: Language in which the movie is made. It gets the info from imdb.com.
You have to choose something (in most cases English) otherwise the tool will say the movie is
banned.
5. Allowed rules: Here you add/modify/del the above rules
6. Test release for rules: here you can test if a movie is banned or allowed by the rules you have
set for this site.

!you have to set imdb.com rules in 3 steps. First add rules for normal movies(theater), then limited
and finaly for STV movies.

Example: if the rules for a site for divx/xvid section would be:
Allowed source: retail DVD, All wide movies allowed, Limited allowed if (10+ screens in US/UK)
and imdb 5.0 with at least 300 votes, STV only if IMDB is 7.0+ and 500 votes, All movies must be
2005+ with English audio.
Step 1: Allowed rules for theater movies

!I used minimum rating 0.0 because all rated movies are allowed.. In this case Xvid is also checked
in allowed but you cannot see that in the picture….because if you don’t add xvid also and release is
a xvid it will be banned. Theater Movies are the ones that have minimum 250 screens in UK and
minimum 500 screens in US…that is why I added 250 to the list. Max year is 2010 because all from
2005+ are allowed, but in the tool you have to set an interval because on some site u have rules like:
2000-2002 if imdb is 5.0+ and 2003-2007 if imdb is 4.0+ etc.
Step 2: Allowed for Limited movies

!Limited means it has between 1 and 500 screens US or between 1 and 250 UK screens, so if there
is no restriction about number of screens put this value to 1. Don’t forget to check that this rules are
for limited movies

Step3: Allowed for STV movies

!stv (straight to video) means it has no screens, you don’t need to set this value to 0, because the
tool knows its 0.

• Tvrage.com rules (for series related sections, tv, tv-dvdrip, tvdvdr…)

1. Countries: Here you can set up shows from allowed countries (it gets the data from tvrage.com.)
2. Sources: Allowed sources separately for dvdrips, tvrips, hr… which the tool reads from the
releasename
3. Languages: allowed/banned languages which the tool reads from releasename (usually no need
for this)
4. Show classification: Genres of the shows, which the tool gets from tvrage.com.
5. Allowed groups: If the groups that are in the list are not selected they will be banned on the site
regardless what tvrage says (coz it can get wrong data) For an example groups like RADAR, Hype
etc.
6. Titles: If only some shows are allowed you can select them.
7. Only latest episode: It will check on tvrage.com if it really is the latest episode…but be carefull
with this because tvrage.com is not always up to date and the tool can therefore tell you its not the
latest ep.
8. Daily allowed: here you can allow daily shows (which are aired every day or every day during
the week) which are usually not allowed. (you have to make a special allowed rule for daily shows).
9. Premiered in year: This is used for tv-dvdrips. It means in which year the Show was premiered.
10. SxxExx needed in rlsname: If you check this it will skip releases which are not tagged with
Season and episode number.
11. Skiplist with wildcard: Sometimes shows are allowed that are not listed on tvrage…for an
example: Discovery.channel, shows from small countries etc. In this case we can use a wild card
and the tool will check only releasename and sources (it will not check stuff on tvrage.com)

So if for an example all Discovery channel shows are allowed you can put in wildcard
Discovery.channel* and then check sources that are allowed.
12. Season in (year): It calculates in which year this season was premiered (premiered year +
number of the season). Use this only if needed otherwise leave it as 0.
 • Games rules (pc, console…)

1. Languages in releasename: If nothing is checked and put in allowed or banned rules everything
is allowed.
2. Additional info: Check rules depending on the section (pc games, console) and put them in
allowed/banned.
3. Allowed/banned rules: here you put what is allowed or banned.

!for normal pc games if clone is not allowed in the additional info list there is nothing to check. So
in this case you leave everything empty and hit add, because if nothing is in allowed rules
everything is banned. If a game is released that has any of the words in additional info list it will
then be banned.
 • Utils, bookware rules

1. Non-industrial utils: If only non industrial utils are allowed select them and add them to allowed
rules
2. Bookware groups: List of bookware groups. If your section is Utils then don’t allow this, if it is
bookware you have to check all and allow them.
3. All allowed from these grps: it will allow everything from the selected groups regardless of
previous rules.
4. Languages in releasenames: If nothing is selected everything is allowed.
5. Industrial+non indu allowed: If this is checked industrial and non industrial appz will be
allowed on site.
 • XXX rules
If only some groups are allowed being raced to XXX you have to add it like this:

• Other section rules

!In every other section that specific rules are not made for, you have to set them in Rlsdir tab. If
everything is allowed you have to add . and – into allowed rules (because in every releasename
there is a . or -).
3.2 Environment settings

3.2.1. Environment

1. Skip similar releases: It will skip similar releases like Bon_jovi_Best_Of-MOD;

Bon_jovi_Best_Of-SQ
2. Max Timeout for newdir race: If on source race is stopped and there are no more new files for
xx seconds race to destination site will be stopped.
3. Del release if it’s a backfill: If backfill release will be automatically deleted on that site.
4. Auto speed test update in every XX min: Update speed every XX minutes
5. Auto site status sync in every XX min: Automaticaly sync status every XX minutes
6. Max destination site count on 1 release: If you have 30 sites and this value is set to 15 it will
just race the best ranked 15 sites where the release is allowed (so you don’t waste logins for crap
sites)
7. Lowest “high” ranked sites rank: That is a limit between high/low ranked sites. If u have sites
ranked from 0-3 and this value is set to 2 it will support sites ranked 0,1,2 with all possible upload
logins - it will be supported the best it can be.
8. Tvrage cache: It is good to regulary update your database from tvrage.com at least once a week.
It will download all the newest data about all the shows you have listed in your db. This is essential
especially if you use the function to only race the latest episode.

3.2.2. Central server

This settings are used for connecting to sites Database. You can save or retrieve settings for sites.
You have to type host, port and your username.
3.2.3. Sounds

Here you can choose if you want to hear a sound when new release comes. You can turn it off, use
default sound or your own.

3.2.4. Filters

1. Filters: For mp3 (it is suggested that most of them are enabled in order to ignore fake releases)
2. Always ignored: here you put words like NUKED, req-, incomplete-
3. Banned Groups: groups that you don’t want to race to any site
3.2.5. Subsections
On some sites there is one directory for the whole section and on other sites that same section is
split into many directories. That is why you have to set subsections right.

Example 1:

On site A there is only one directory for section TV. In it there are allowed shows in pdtv/hdtv
format, tv-dvdrip and on it there are also affils that pre x264. Everything goes into one directory:
TV: incoming/series

On site B there are three directories for section TV (pdtv/hdtv shows, tv dvdrips and x264 shows):
TV: incoming/tv
TV-DVDRIP: incoming/tv-dvdrip
X264: incoming/tv-x264-720p

You have to set subsections so that the tool will know when something is pred or raced on site A to
which directory to site B it has to send it to. That is why you have to specify which subsections
mean the same section. It will then fxp between the subsections (because you will tell the tool that
this subsection means the same general section) based on which source is allowed on the rules of
each subsection. In this case you have to specify that tv=tv-dvdrip=x264 (that this are the same
sections on some sites)

1. Add main section name (you can make this up)

2. Select main section and choose which subsections mean the same general section
3. Select main section and hit modify.

Example 2:

On site A you have divx (normal dvdrip allowed) and cine (TS, TC. R5 allowed)
DIVX: /divx/
CINE: /divx-cinema/
On site B you have divx (where dvdrip, R5 is allowed) There are also groups that PRE TC but its
affils only. You also have divx-pl section because it’s a polish site
DIVX : incoming/divx
DIVX-PL: incoming/divx-pl

Site C has only one section for divx. In it dvdrips, r5, tc and polish releases are allowed.
DIVX: /xvid/

1. Tell the tool that DIVX=CINE=DIVX-pl (that they are the same subsection)

2. Since cine (R5,TS,TC) and normal divx (DVDRIP) is defined in allowed sources in each section
it will know to which directory it has to fxp. But for polish tagged releases it will not know where it
has to put it since that is not defined in source. So that is why you have to allow PL releases in
DIVX-PL section on site B and in DIVX section on site B. You can do that by adding another set of
rules to imdb.com tab that allow PL releases (see below) – you have to do this on both sites…rules
ofcourse don’t need to be the same (they can have different rating etc) but PL has to be enabled on
both sites.
• Site B, section DIVX-PL
 • Site C, section DIVX

!note that you have to separately add rules in imdb.com for .pl releases because if .pl is allowed in
language in releasename then normal releases (because they don’t have tag .pl.) are not allowed. So
you need to add rules for English movies and polish movies separately.

3.3 FTP client settings

This settings are for Tzftp

STEP 1: Connect to your host:16666 server (port is 16666 unless you specify otherwise in
config.ini). If you are running tzftp on your home computer connect to 127.0.0.1:16666. Before
connecting enter your tzftp password (the one you have set when you ran Tzftp for the first time)

STEP 2: Add your sites (they have to have the same name as in Site Settings. All the settings are
self explanatory ;)

For iso racers be sure to set in config.ini use_fastest_bnc=0 and use_minus=0

!if you use ident you have to have the same ident on mirc as on sites (it will use ident from mirc to
connect to sites).

3.4 Routing table

Routing table is a table that shows speeds between all sites that you have. It shows for every site
what kind of speed it has to all other sites and from all other sites to this site. It is essential that after
you set up the tool or add a new site you make a speedtest between all sites so the tool will know
between which sites the routing is good. Otherwise it cannot generate a good chain.

1. Routing table/matrix: On the top you have source sites and on the left you have destination
sites. In the case shown here it means if you fxp from site A to site B speed is 1000kb/s but if you
fxp from site B to site A speed is 2000kb/s. You have to make a speedtest in order to get this data.

2. Min/max filesize: When you make a speedtest you have to select a minimum and maximum
value which actually matches a file that exists on the site. For mp3 that value can usually be from 1-
15mb but for iso it is between 14 and 50mb (coz min rar size is 15mb and max 48mb if it’s a dvd).

3. Incoming/outgoing: If you select a site and Incoming it will make speedtests from all sites to
that particular site. If you select a site and Outgoing it will make a speedtest from this site to all
other sites. If you select incoming+outgoing it will make a speedtest between all sites (between all
sites in the list). If you select a field and between it will only make a speedtest between those two
sites (from site in source to site in destination field).

!When you get a new site you ofcourse cannot make a outgoing speedtest because you don’t have
any credits.
!If you don’t want to fxp between selected two sites at all put a - in the field that matches both of
them.

In order for the tool to know from which directory on source site to which directory on destination
site it can fxp you have to set up those paths. It is explained in section 3.1.2. Catcher under number
6.

4. Racing
For racing you have to be in:

• Releases Tab

Or
• Minimised window (ctrl+m)

/o\ Happy racing /o\