RatioMaster 1.8.6 updated by SB-Innovation

[anon]

SB-Innovation Presents

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

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

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

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

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

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

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

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

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

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

Changelog:

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!
- Bug Fix : corrected torrent hash URL encoding in some cases
- Update : main languge template is renamed to 1english.lng to be on top of the list (default)
- Update : added new strings to language template for 1.8.2, please update your translations
- Update : included 15 language files done by forum members
- Update : removed RatioMaster-vs.exe from package
- 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: 06.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
- µ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)

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:
╚═══════════════════════════╝

49oa61d664ln8rad

[mmmmm]

Hi anon ,want to ask some questions about new updates since Mr.RM busy these days and i excepect quick answer as always you the best in that:

What the difference between Reset Counters and manual update?
what these means:
support for urlencoding "exceptions" node

<urlencoding exceptions="_()~._-" />

support for lowerCase="true" and "false"

Many thanks for you.

[anon]

What the difference between Reset Counters and manual update?

Reset Counters resets the downloaded, uploaded and finished % to 0 and does not update or stop the torrent.

support for urlencoding "exceptions" node

It prevents the specified characters from being percent-encoded when sent in the info_hash. These vary from client to client. Further prevents the RM from being detected.

support for lowerCase="true" and "false"

It makes all characters on a generated peer_id be lowercase, like Transmission's, for example.

[sbrocks]

wow first page so after we fake 1Gb like in what.cd, then stop the torrent, click the reset button, it will show me 0kb in peerlist?

[Kyllyee]

wow first page so after we fake 1Gb like in what.cd, then stop the torrent, click the reset button, it will show me 0kb in peerlist?

No......not quite. If you click stop, then RM will report what you uploaded/downloaded to the tracker. If however you click JUST the reset button then it will start over with what ever new speeds you want.

If you do the following, if will report to tracker:
-Click Stop
-Torrent finishes ( 100% Done )
or if it just reports normally. ( Like it would every 30 - 45 min. )

If you do any of those and then click reset, it would not change what you did before.....

[alpacino]

No, if you click reset after stop button, nothing is bound to happen, the reset button is there to save you while the RM is working in case you mess up by choosing unrealistic speeds.

Reset Counters resets the downloaded, uploaded and finished % to 0 and does not update or stop the torrent.

[Kyllyee]

No, if you click reset after stop button, nothing is bound to happen, the reset button is there to save you while the RM is working in case you mess up by choosing unrealistic speeds.

Im confused..... shouldn't it report the 1 gig uplaoded??
( Hit stop then reset.......defeats purpose of the reset button, no? )

[alpacino]

Im confused..... shouldn't it report the 1 gig uplaoded??
( Hit stop then reset.......defeats purpose of the reset button, no? )

Yes, his 1Gb upload will be added to snatchlist, when I answered "no" I was referring to the "click reset after stop button" action and meant to explain the reason why "reset" button was created. Sorry if it sounded strange.

[noobglitch]

Will I have any problems if I use 1.8.5 & 1.8.6 at the same time?

[Kyllyee]

Will I have any problems if I use 1.8.5 & 1.8.6 at the same time?

Correct me if I am wrong, but I don't see an issue IF you don't use the same torrent for both.....or be seeding on the same tracker with 2 different 'clients' ( well, that might pass because people do have seed boxes... ). Just don't do it with the same torrent. ( As anonftw said 2 posts down. )

[stinson]

how will it pass?
since when seedboxes have the same IP as ur own?

[anonftw]

Correct me if I am wrong, but I don't see an issue IF you don't use the same torrent for both.....or be seeding on the same tracker with 2 different 'clients' ( well, that might pass because people do have seed boxes... )

Never seed the same torrent from two different clients on the same IP. How is this supposed to work ? The 2 seperate send and receive announces from the same IP will be different using the same passkey and you will almost surely be banned.

1 IP + multiple announces on same torrent to same tracker= BAD
2 IP + same torrent=OK

[Kyllyee]

how will it pass?
since when seedboxes have the same IP as ur own?

Unless the staff of a tracker take the time to actually look at your IP and details about the clients you have used, then there should be no reason to investigate.( Don't give them a reason to do so, lol. )

Never seed the same torrent from two different clients on the same IP. How is this supposed to work ? The 2 seperate send and receive announces from the same IP will be different using the same passkey and you will almost surely be banned.

1 IP + multiple announces on same torrent to same tracker= BAD
2 IP + same torrent=OK

Well of course :)
But two IPs for one torrent may also seem suspicious if no one knows you have seedbox, right??

[divlord]

If anyone is using this tool I think its a good idea if we report over here
1) Tracker you cheated on
2) Download upload speed settings
3) Success or banned

I used nrpg ratiomaster and haven't been banned except IPT.
But nrpg is not consistent sometimes it reports

An existing connection was forcibly closed by the remote host
[09:09:24] No connection in sendEventToTracker() !!!

But on the same tracker it works somtimes

[Options]

this and mratio, which one is safer?

[ip8gb]

Both work great according to most users, so use the one you prefer. But be careful with what you seed. i'll definitely try RM after I get the password.

Edit: and now I do...muahahahaha!!