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

[lifesaball]

Does anyone know what "Failed to decode tracker response" mean? This happens to me sometimes.

When this happens, the seeders/leechers info will always be blank and but the time (total time/ update in) still keeps running.

And sometimes the download/upload data does not update either, still with the time running.

[Kyllyee]

Does anyone know what "Failed to decode tracker response" mean? This happens to me sometimes.

When this happens, the seeders/leechers info will always be blank and but the time (total time/ update in) still keeps running.

And sometimes the download/upload data does not update either, still with the time running.

Humm, I have never gotten that error. What tracker is giving you this problem,?

[alpacino]

Does anyone know what "Failed to decode tracker response" mean? This happens to me sometimes.

When this happens, the seeders/leechers info will always be blank and but the time (total time/ update in) still keeps running.

This happens in some trackers like TTi for example. I think it's because some trackers have incompatibility issues with the scrape method RM uses. So if you disable "Get Seeders/Leechers stats..." you won't receive this error anymore and anyway you will have to keep an eye on the tracker for the correct number of peers and seeds.

And sometimes the download/upload data does not update either, still with the time running.

This could be caused by timeout problems.

[anonftw]

I also get the "Failed to decode tracker response" on Zamunda. Sometimes, it repeatedly gives me improper peer stats(fortunately anything goes there). On TTi, I just get nothing, so it makes it scary unless I'm on a really big fresh pack. It will be awesome if this ever gets fixed !

[lifesaball]

Will it look suspicious with no seeders/leechers info in RM, if having the 'decoding' error?

[anonftw]

Will it look suspicious with no seeders/leechers info in RM, if having the 'decoding' error?

The No Seeders/Leechers problem mentioned is only on the client side.(in RM itself) The trackers stays the same, but you cannot tell how many seeders or leechers are on the torrent without logging into the tracker to check. This makes it a little more work to be safe.

[anon]

Yes, it's an scrape bug... if the tracker doesn't return the amount of seeders and leechers in normal announces, and scrape gives you that error, you'll have to do it the old-fashioned way - refreshing the page.

(By the way, the term "scrape" comes from the fact that it automates that manual procedure, called "screen scraping". )

Look at the positive side - the amounts will always be up to date.

[cheatos]

great work, thanks for the update,
it must on the main page right ? or you are waiting for 1.8.8 ?

[Reichsadler]

Yes, it's an scrape bug... if the tracker doesn't return the amount of seeders and leechers in normal announces, and scrape gives you that error, you'll have to do it the old-fashioned way - refreshing the page.

Does Mr. RM know this bug? Will he correct this bug or can he do this because it is very nerved always to look at the tracker page.

[shoulder]

it must on the main page right ? or you are waiting for 1.8.8 ?

~ done

[alpacino]

Does Mr. RM know this bug? Will he correct this bug or can he do this because it is very nerved always to look at the tracker page.

I'm sure he does and that he will fix it in due time. Remember, as anon said once, we should be thankful for Mr RM recently releases and updates as the project was stuck at 1.7.5 and stopped for several months before.

[xixifrank]

should "update peer_id and key on startup" be ticked?

[anon]

It doesn't really matter, because you should always use the memory reader anyway.

[Haggar]

I know that sometimes the best thing is to use the latest version, but are these bugfixes important enough to use this instead of version 1.8.6? BTW, thanks for the new toy, bye

[shawshankraj]

I know that sometimes the best thing is to use the latest version, but are these bugfixes important enough to use this instead of version 1.8.6? BTW, thanks for the new toy, bye

Always try to use New release,B'cozit's come with Bug fixes,New client emulation etc..