RatioMaster 1.8.8 updated by SB-Innovation

[anon]

SB-Innovation Presents

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

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

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

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

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

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

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

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

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

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

Changelog:

Version 1.8.8
--------------
...
- Feature : added ability to save list of peers per torrent ("Save list of peers" checkbox in Network/Miscellaneous).
...

Version 1.8.6
--------------
- Feature : added 'Reset Counters' button, to reset upload/download amounts to previous values
...

Version 1.8.5
--------------
- Feature : added another HTTP proxy support (UltraSurf and similar programs)
...
- Update : improvements to memory reader
...

Version 1.8.4
--------------
- Feature : added HTTP and SOCKS4a proxy support
- Feature : added UPnP port forwarding support
- Feature : added option to ignore connection timeouts
...

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.
- built an installer (THX CoreCore!)

Client Files

Last Update: 29.07.2009

- 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 *
- 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
- BitSpirit v3.5.0.275 *
- BitTorrent 6 (Build 4747) *
- BitTorrent 6 (Build 5535) *
- BitTorrent 6.0.3 (Build 8642) *
- BitTorrent 6.1 (Build 11862) *
- Deluge 1.1.7 **
- Halite 0.3.1.1 **
- Transmission 1.06 (Build 5136) **
- µ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) *
- µTorrent 1.8.3 (Build 15772) *

* = info_hash issue fixed
** = 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:
╚═══════════════════════════╝

typb71d664s58sae

[TD21]

Okay i'm having trouble finding the peer_id line. Here's a step by step of what i did

Enabled logging
Enabled logging to file
added a logfile directory and only checked tracker
restarted azureus
went to console and logifle but no peer_id

[anon]

Double-clicking the torrent and going to the Console tab is enough here.

Check the announce line to fetch the peer_id.

[TD21]

Okay got it! Where do i find the key though? How about the port and numwant?

[anon]

Edited!

After &key=, &port= and &numwant=, respectively.

[TD21]

I'm getting multiple keys so i was wondering if i could use any of them?

[anon]

I don't know what you mean with "multiple keys", but just use one. A typical Vuze key looks like S0zC2VBi.

[TD21]

Yes my log has lots of em lol! Maybe it's because i have alot of torrents running? Thanks alot for helping a noob out lol!

[anon]

Maybe it's because i have alot of torrents running?

Yes, I suppose that's why. Either way, Vuze and memory reading should no longer be a problem for you.

[TD21]

Btw, can i just save ID KEY PORT NUMWANT or do i have to get a new one each time i load up RM? I won't be changing my port or Vuze client anytime soon other than grabbing the latest Extreme mods.

[anon]

I'd say a new one every time. Vuze generates a new peer_id every time you start a torrent.

[mmmmm]

The memory reader doesn't work on Vuze 90% of the time.

Hi anon,

I have noticed the RM sends printable characters in the info_hash as URL-encoded (i.e. %2F rather than /). Some clients send them as the chars they really are (2A is *, 2B is +, etc.), so it'd be great to have an setting inside the .client files to do this as well.

Secondly, another setting for peer_ids that are only alphabetic , rather than alphanumeric, would also come handy to avoid using the memory reader when emulating open-source clients.

Version 1.8.6

* Update : support for type="alphabetic" and type="printable" attributes in client files

isn't vuze open source!!then should RM get correct per-id without using memory reader!!
I wish you and DigitalDJ can help Mr.RM fixing that problem.

[anon]

isn't vuze open source!!then should RM get correct per-id without using memory reader!!
I wish you and DigitalDJ can help Mr.RM fixing that problem.

Yes, theoretically Mr. RatioMaster could check Vuze's source code, and implement a setting to generate Vuze peer_ids in client files.

[mmmmm]

can you explain that to him?

[anon]

I have fired him a PM about this five minutes ago.

[okorn]

Any news about Client Files por uTorrent Build 16010?

Thanxs in advance.