RatioMaster 1.8.2 updated by SB-Innovation

[anon]

SB-Innovation Presents

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

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

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

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

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

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

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

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

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

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

Changelog:

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
- 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.

Version 1.8.1
--------------
- Feature : RightToLeft key to localization file, preliminary support for right to left languages (hebrew, arabic)
- Bug Fix : improved application start-up time, no more 2 second pause until RM window fully appears
- Bug Fix : added several missing strings to english.lng
- Update : added several more localization files (by forum members)

Version 1.8
--------------
- Feature : Added support for localization
- Bug Fix : fixed bug in decoding chunked HTTP response in some trackers
- Bug Fix : fixed bug in parsing tracker url in some cases
- Update : added several up to date client files into main package

Version 1.7.7
--------------
- Feature : Added support for HTTPS trackers
- Bug Fix : fixed but with new version dialog

Version 1.7.6
--------------
- Bug Fix : Several improvements and bug fixes
- Update : Updated client files to newest versions
- Update : Changed url for checking new version to www.moofdev.net, please update your bookmarks.

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: 17.04.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 *New*
- 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.0 (Build 474)
- µTorrent 1.6.1 (Build 483)
- µTorrent 1.6.1 (Build 489)
- µTorrent 1.6.1 (Build 490)
- µTorrent 1.7.0 (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 12639)
- µTorrent 1.8.2 (Build 14458)
- µTorrent 1.8.2 (Build 15167) *New*
- BitTorrent 6 (Build 4747)
- BitTorrent 6 (Build 5535)
- BitTorrent 6.0.3 (Build 8642)
- BitTorrent 6.1 (Build 11862)

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

2m15gs64l9g0jn8z

[alpacino]

I have a question:
RM never let me down emulating uTorrent 1.7.7 (the version I use). I've been sniffing the packets here and there and saw that uTorrent doesn't change the peer_id and key, unless you restart or close and reopen it. So RM emulates it OK.
My question is regarding Vuze, when sniffing the client every now and then, I realized it gives different peer_id and key at every announce thus making Vuze emulating not so secure?
Should I be worried about it? Or is it pure paranoia?

Can you explain me or point a faq/wiki of what these terms mean?
I can understand the need of a peer_id, it identifies your client and you with the rest of characters? So why the need for key string?

In Vuze spoofing uT with custom id, it keeps sending this same peer_id all over on the announces right? Why there's no field to input key in Vuze when uT spoofing?

Many questions sorry

[anon]

My question is regarding Vuze, when sniffing the client every now and then, I realized it gives different peer_id and key at every announce thus making Vuze emulating not so secure?
Should I be worried about it? Or is it pure paranoia?

That could be because the RM is finding the peer_ids and keys of different loaded Vuze torrents every time.

Can you explain me or point a faq/wiki of what these terms mean?
I can understand the need of a peer_id, it identifies your client and you with the rest of characters? So why the need for key string?

A peer_id is a 20-byte generated string that identifies your client both when communicating with the tracker and other clients.

The key value is for the tracker to be able to identify you even after an IP change.

In Vuze spoofing uT with custom id, it keeps sending this same peer_id all over on the announces right? Why there's no field to input key in Vuze when uT spoofing?

Yes.

There's no need for a custom key since they're only shared with the tracker, and the Extreme Mod can safely generate them.

[anon]

I assume you meant BitSoup, and if so, the PMR also works there, but your post isn't helpful at all if you don't state which speeds and torrent you used.

[alpacino]

Hey anon, remember when I told you my stats at TL weren't updating correctly using RM? I realized it doesn't always happen , but in 50% of the time . The fake download finishes in RM and hours later I check the snatchlist and it is reported as some 80 or 95% finished and then only keeps seeding. Today I've tried (real) downloading a big torrent with Vuze xtreme mod and same thing happened straight away, 96% of download reported in my snatchlist :(.

Which other reasons could make this kind of behavior happen?

I'm mad because I used a real client this time. Now I'm always fixing these bad stats using RM with correct emulation and using the finished % feature accordingly. Problem is, it doesn't fix with 100% accuracy.

[anon]

The only reason I can think of is your ISP interfering with announces.

Can you check if the issue with Vuze persists after using the semi-anonymous torrenting method in my sig?

[alpacino]

I could try that, but only TL is doing this with me. Other trackers seems good. TL never screwed the report for you?

[anon]

No, it has always worked fine for me.

[mirrormask]

I could try that, but only TL is doing this with me. Other trackers seems good. TL never screwed the report for you?

this has happened to me too in the past.
the tl tracker is quite often offline or unresponsive which results in faulty stats.

[Tinkle]

I could try that, but only TL is doing this with me. Other trackers seems good. TL never screwed the report for you?

my friend mostly this happens if the server doesnt get u r announces properly
another thing u must know TL is popular tracker so lot of ISP block and do stuff to avoid this site so that they dont have to face legal troubles
so it is high chance that it may be u r ISP

[alpacino]

my friend mostly this happens if the server doesnt get u r announces properly
another thing u must know TL is popular tracker so lot of ISP block and do stuff to avoid this site so that they dont have to face legal troubles
so it is high chance that it may be u r ISP

Thanks Tinkle, mirrormask and anon, but I think my ISP isn't the issue here. I am pretty sure it doesn't give a damn about p2p

I think it's time for me to upgrade to RM 1.8.3 after all

Will do some tests and get back to you.

I can tell you my cheating at sdbits, scenefz, goem, x264, revtt, iplay, bitgamer, ScL all reports 100% accuracy, all the time. Just TL and IPT gives me problems. IPT I really don't care, as it is buggy as hell, mainly their bonus system

[anon]

I think it's time for me to upgrade to RM 1.8.3 after all

I didn't even notice this was the 1.8.2 thread! You definitely should update. It takes 5 minutes

[alpacino]

I didn't even notice this was the 1.8.2 thread! You definitely should update. It takes 5 minutes

LOL anon, yes I promise I will update tonight!

Let me just insist on this matter 1 more time:

When tools or clients are announcing, do they send increments of how much it Dl/Ul? Or does it inform the partial % completion at every update?

My guess is that it's incremental and maybe some announces along the way aren't adding up? Maybe due to timeout or such. Just reminding as I told befere it's been happening randomly with RM and Vuze xtreme no spoof. I still have to try ut real client.

[anon]

When tools or clients are announcing, do they send increments of how much it Dl/Ul? Or does it inform the partial % completion at every update?

They send how many bytes you've &left= before finishing the torrent. This way issues like yours won't happen if your miss announces on real clients.

And TL updates stats even if the tracker connection times out.

[alpacino]

They send how many bytes you've &left= before finishing the torrent. This way issues like yours won't happen if your miss announces on real clients.

And TL updates stats even if the tracker connection times out.

Then I really don't know why I'm having this problem. I am left to think it's a tracker bug. Do you have any more suggestions I could try?

[anon]

Have you tried what I mentioned in post #171?