RatioMaster 1.8.7 updated by SB-Innovation

[anon]

SB-Innovation Presents

>>>>>> RatioMaster 1.8.7 updated by SB-Innovation <<<<<<

╔═══════════════════════════╗
Coded by:
╚═══════════════════════════╝

>>>>>> RatioMaster <<<<<<

╔═══════════════════════════╗
Source:
╚═══════════════════════════╝

>>>>>> moofdev <<<<<<

╔═══════════════════════════╗
Updated by:
╚═══════════════════════════╝

>>>>>> Rebound & anon <<<<<<

╔═══════════════════════════╗
Supplier:
╚═══════════════════════════╝

>>>>>> anon <<<<<<

╔═══════════════════════════╗
Changelog / Features:
╚═══════════════════════════╝

Changelog:

Version 1.8.7
--------------
- Update : moved client files to separate folder (/clients)
- Bug fix : fixed crash "invalid ip" on some computers
- Bug fix : fixed slow loading time on some computers
- Update : updated language template to ver. 1.8.7, new translation and client files

Version 1.8.6
--------------
- Feature : added 'Reset Counters' button, to reset upload/download amounts to previous values
- Update : support for type="alphabetic" and type="printable" attributes in client files
- Update : support for urlencoding "exceptions" node , see example in utorrent_1.8.3_build_15728.client
- Update : support for lowerCase="true" and "false"
- Update : updated language template to ver. 1.8.6, new translation and client files
- Bugfix : improved handling of bad ssl sertificates
- Small fixes and improvements

...

Version 1.8.2
--------------
- Feature : added ability to download new client files and translations directly from RM (tab Updates)
- Bug Fix : corrected "Host" header that RM sending to tracker in some cases - No more ort issue!
...
- Small fixes and improvements that i forgot about. - Scrape now works!

...

Version 1.7.5
--------------
- Bug Fix : Improved handling of connection and response timeouts.
- Bug Fix : Fixed problem with sockets not being closed
- Update : Updated build in uTorrent emulation to uTorrent 1.6.1 (build 490)
- Feature : added AI based on neural networks
- Feature : added voice recognition.
- build an installer (THX CoreCore!)

Client Files

Last Update: 11.07.2009

- ABC 3.1.0
- Azureus 2.5.0.0
- Azureus 2.5.0.2
- Azureus 2.5.0.4
- Azureus 3.0.0.6
- Azureus 3.0.0.8
- Azureus 3.0.3.0
- Azureus 3.0.3.4
- Azureus 3.0.4.2
- Azureus 3.0.5.0
- Vuze 3.1.1.0
- Vuze 4.0.0.0
- Vuze 4.0.0.2
- Vuze 4.0.0.4
- Vuze 4.1.0.2
- Vuze 4.1.0.4
- Vuze 4.2.0.0
- Vuze 4.2.0.2 Recommended, info_hash issue fixed
- BitComet 0.63
- BitComet 0.79
- BitComet 0.84
- BitComet 0.85
- BitComet 0.86
- BitComet 0.87
- BitComet 0.88
- BitComet 0.89
- BitComet 0.90
- BitComet 0.91
- BitComet 0.92
- BitComet 0.93
- BitComet 0.94
- BitComet 0.95
- BitComet 0.96
- BitComet 0.97
- BitComet 0.98
- BitComet 0.99
- BitComet 1.00
- BitComet 1.03
- BitComet 1.04
- BitComet 1.05
- BitComet 1.07
- BitLord 1.1
- BitTyrant 1.1
- BTuga 2.1.8
- Burst 3.1.0b
- Halite 0.3.1.1 Generated peer_id and key improved
- µTorrent 1.5
- µTorrent 1.6 (Build 474)
- µTorrent 1.6.1 (Build 483)
- µTorrent 1.6.1 (Build 489)
- µTorrent 1.6.1 (Build 490)
- µTorrent 1.7 (Build 1875)
- µTorrent 1.7.1 (Build 3360)
- µTorrent 1.7.2 (Build 3458)
- µTorrent 1.7.3 (Build 4470)
- µTorrent 1.7.4 (Build 4482)
- µTorrent 1.7.5 (Build 4602)
- µTorrent 1.7.6 (Build 7859)
- µTorrent 1.7.7 (Build 8179) (THX CoreCore!)
- µTorrent 1.8 (Build 11813)
- µTorrent 1.8.1 (Build 12616)
- µTorrent 1.8.1 (Build 12639)
- µTorrent 1.8.2 (Build 14153)
- µTorrent 1.8.2 (Build 14458)
- µTorrent 1.8.2 (Build 15167)
- µTorrent 1.8.2 (Build 15227)
- µTorrent 1.8.2 (Build 15296)
- µTorrent 1.8.2 (Build 15357)
- µTorrent 1.8.3 (Build 15728) Recommended, info_hash issue fixed
- µTorrent 1.8.3 (Build 15772) Recommended, info_hash issue fixed
- BitTorrent 6 (Build 4747)
- BitTorrent 6 (Build 5535)
- BitTorrent 6.0.3 (Build 8642)
- BitTorrent 6.1 (Build 11862)
- Deluge 1.1.7
- Transmission 1.06 (Build 5136) Generated peer_id and key improved

Weitere Wünsche für Client-Files sind immer Willkommen.
Of course you can post client file wishes for any client.

We have permission from the coder to post this tool!


╔═══════════════════════════╗
Password:
╚═══════════════════════════╝

joe6iut5n0i1lp90

[anon]

The RM can only fake upload and download to the tracker. It doesn't connect to peers.

[LittleCow]

Yes, but peers have my IP from tracker, and try connect to me. They will see that I do not send the actual files

PART 2

RM put random value for Upload Speed. In 30 minutes I have sent 200 MB. Calculate simply that I uploading on exactly same speed.

200 MB in 30 minutes = 131,7 kB/s - constant speed

[anon]

Yes, but peers have my IP from tracker, and try connect to me. They will see that I do not send the actual files

They won't see anything because they won't be able to connect to you. (This is inherent to all ratio tools)

PART 2

RM put random value for Upload Speed. In 30 minutes I have sent 200 MB. Calculate simply that I uploading on exactly same speed.

200 MB in 30 minutes = 131,7 kB/s - constant speed

Yes, but on the next update the tracker will see another speed... simply enable the randomizer and don't worry about this, OK?

[shadowww]

Ok, but something is else

For example staff tracker use original uTorrent. In original uTorrent is bookmark "Peers". Shows there "IP", and "Down speed", "Up speed" in real time.

Not in real time. You communicate with tracker *only* when your counter at field "Update in:" reaches zero.
All this numbers you see, uploaded and downloaded amount is just for show, for your info. You send to tracker only *sum* of uploaded and downloaded amount when pre aranged time (counter "Update in") comes.

[alex0912]

Am I blind or ... ? where's the password? ..heh

[shadowww]

You must press "thanks" button to see it i belive...

Btw. i 1.8.7 works fine for me now. After restart it reads my utorrent client without problem (and when i only seed 1 torrent)

[dl_rank1]

mRatio or Ratio master???

[SBfreak]

Take a look here for more info.
I'd say both are good.Remember to use memory reader while using RM.

[anon]

The disadvantage of mRatio is the lack of updated emulations in the official version, and for some, the absence of an uTorrent emulation. But if you're OK with that or know how to send The248 a Wireshark CAP of the client you want an emu for, both should be fine.

[noobglitch]

Is it safe to run multiple instances of ratiomaster? Haven't encountered any problems yet.

[Pickle]

yes it is safe to use multiple instances.

[listener]

I really like RM, but I've always been thinking...:

So, we choose a specific upload speed, which can be specified up to 0,01 kB/s. This speed can be randomised every time the program connects to the tracker, so the total uploaded values and average speed values will differ on every update, which is great.
However, the time interval between each automatic update to the tracker is normally fixed (30minutes usually, so that makes 1800 seconds). If all this happens the way I would think it happens, the randomised speed specified up to 0,01 kB/s will be the same during this 1800 seconds, so the total uploaded amount will always be a multiple of 18kB? (because 1800s*0,01 kB/s = 18kB)

I hope my reasoning is wrong, and someone here can tell me why exactly...

[alpacino]

The update interval is always sent by the tracker on announces. And don't worry about the randomization, it works properly. RM will fake with the speed you tell it to, random or not.

[anon]

Lots of trouble with the randomizer lately...

The update interval varies from tracker to tracker - it can be as low as 20 minutes, or as high as 60. (I have seen 180m on a public tracker )

To make a graphic example:

• You set it between 100 and 150
• You set the initial speed to 100kB/s, and start the RM
• Say, 30 minutes pass, first tracker update, the tracker sees 100kB/s
• The RM picks another speed between your values, for example 128.07kB/s
• 30 minutes pass again, the tracker will see 128.07kB/s.

(Remember that in the peerlist, speeds are averaged. If you fake at 500kB/s, the first tracker update takes place, then you drop to 0kB/s, the tracker will show 250kB/s in the peerlist. If your speed is still 0kB/s after the third update, 125kB/s will be shown, and so on. So don't rush and check the "Connected" column to see for how much time that user's torrent has been running!)

In a nutshell: just enable the randomizer and don't worry about it

[LittleCow]

RM was tested on ScT or What.cd?
It is possible to use it on High Level Trackers