What's New: RMP 1.4.1:
- New : Logger now uses 24 hours time system.
- BugFix: Windows 10 detected as Windows 8 (New Algorithm).
SpoilerComplete changelog::
RMP 1.4.1:
- New : Logger now uses 24 hours time system.
- BugFix: Windows 10 detected as Windows 8 (New Algorithm). RMP 1.4:
- New : Tixati peerId & Key validator.
- New : Upload & Download rate show in Real time.
- New : You can change Upload & Download rate in Real time.
- New : More finished options (seeding, Leeching, Custom (%, Byte, KB, MB, GB)).
- New : Total upload, Total download, Left and Ratio numbers. (Needs translating)
- New : Total upload, Total download and Ratio stop conditions. (Needs translating)
- New : Torrent & over-all settings now save at Tracker update besides at Exit.
- BugFix: uTorrent peerId validator failed in some rare special cases. RMP 1.3.3:
- New : Tixati peerId and key support.
- New : Can't add new torrent while working on another.
- BugFix: Over logging in some cases (Like moving your mouse on tray icon). RMP 1.3.2:
- BugFix: Special log message for empty tracker respond.
- BugFix: Tracker URL is repeated in Trackers ComboBox.
- BugFix: Selected tracker url is not saved correctly.
- BugFix: Can't load HTTPs Tracker URL in some cases.
- BugFix: Can't decode tracker respond if its encoding is gzip. RMP 1.3.1:
- BugFix: Tracker Respond logged as empty text.
- BugFix: TorrentDay trackers URLs not get correctly loading. (Reported: greenberet)
- BugFix: Tracker request not valid for HTTPs trackers. (Working on the latency) RMP 1.3:
- New : GUI icons and arranged controls.
- New : You can now use uTorrent client without memory reader (uT versions >3.4.x, Change bt.randomize_peer_id to false).
- New : You can now use Transmission client without memory reader.
- New : PeerId and Key get generated at start-up by default.
- New : Port generated at start-up IF the port text box is empty.
- New : Tracker URL & Torrent hash is read only now.
- New : All torrent trackers loaded at the start-up and you can choose one to use.
- New : Faster Memory reader and the GUI still responsive while reading memory.(with uT > 3.4.x support)
- New : Memory reader now respect if the PeerID & Key is global or not.
- New : PeerId validation for uTorrent & Transmission peerIds.
- BugFix: PeerId exceptions ignored and always passed as fixed value.
- BugFix: New port generated with 'every' announce.
- BugFix: Wrong Java version detection in special cases (New detection algorithm).
- BugFix: Can't load tracker URL in some cases. (Reported)
- BugFix: RM+ can't remember the last used client between starts.
- Remove: Internal clients removed.
- Remove: Client files update manager is removed.
ClientFile Changelog:
- New : New extension ".pclient" (had to, because of the many changes).
- New : randomize="" attributes for peerId & Key.
- New : urlencoding="upperCase" & urlencoding="lowerCase" to specify %AB or %ab
- New : global="" attributes for peerId & Key.
- New : query {localip},{ipv6},{ip} place-holders support.
- New : headers {customport},{allports} place-holders support.
- New : PeerId type value "uT" or "ut" for generating valid uTorrent peerId without memory reader. <peer_id type="ut"
- New : PeerId type value "Tr" or "tr" for generating valid Transmission peerId without memory reader. <peer_id type="tr"
- New : <peer_id node has exceptions="" attribute now.
- New : <hash node has exceptions="" attribute now.
- Change: No <urlencoding node anymore (use <hash & <peer_id to add exceptions by exceptions="" attribute).
- Change: No value="" in PeerId and key node in client file anymore.
RMP 1.2:
- New : RM+ now simulates the real client accurately.
- Fixed : RM+ doesn't save Torrent's config file if there is no language file loaded.
- Fixed : Couldn't decode tracker respond correctly (Reported: Rebound)
- Fixed : BitComet 0.70 wrong peerID prefix
- UI : SB-I reference in Title bar.
- New : Auto uTorrent peerID prefix -not whole pId- generator.
- Client Files: up-to-date client files serving the new changes.
RMP 1.1:
- Fixed : "Check for updates" button is not greyed while updating.
- Fixed : Wrong add at log window (example : "unNumUpdatesFounjd=Found {0} updates" after update).
- Fixed : No log messages if language file exist.
- New : IPv6 support {ipv6}
- New : New Icon (Thanks anon)
RMP 1.0:
- New : Client updates via SB-I's server.
- Removed: Check for new version at start-up.
- Removed: "Check for new version" CheckBox.
- Removed: "Help with proxies" at "Network" tab.
- Fixed : Wrong Windows(7 X64) version detection.
- Fixed : Wrong Windows(8,8.1) version detection.
- Fixed : Java wrong version detection.
very important points:
- You can now use RatioMaster plus without memory reader if you run it standalone.
- RatioMaster's Client files is not valid for the plus version anymore.
thanks a lot first of all!
I have a little question about the "memory reader"
I put my utorrent version and it successfully loaded...
Do I need to do it every torrent I load? or one time is enough?
Rm+ is the updated version of Rm 1.9.2 and no there is no support for rTorrent because this client used a lot with seedboxes and there is no point in cheating while you've a seedbox.
Originally Posted by randoma
thanks a lot first of all!
I have a little question about the "memory reader"
I put my utorrent version and it successfully loaded...
Do I need to do it every torrent I load? or one time is enough?
thanks
It's better to just let Rm+ doing the memory reader and then decide what is the best for you (there is some calculation to decide). But I don't know if you're talking about multi-torrent cheating at the same time or you're talking about after restarting uT, please elaborate.
well, let's say I'm downloading a torrent from TL. after I downloaded it I just want to use RM+ to "upload" it back to TL and have a stable ratio. So what I'm doing right now is after the file was completely downloaded I'm running RM+ on that file...(the Utorrent is closed when RM+ is on)
So am I doing it right? Should I run the memory reader each time, or is it automatically works after one time?
Thank a lot!
first of all thank you very much for sharing this amazing tool with us all. Reading through the posts here I have noticed that it seems to be a very friendly community with a great support on problems.
I am pretty new here and also new with using such software. I have tried it for some days and noticed some problems.
Frankly said my ratio got worse after using RM+ and I think I know what mistake I did:
I have finished downloading a torrent and stopped seeding it in utorrent, but I kept utorrent seeding other torrent files from the same tracker.
Then I have loaded RM+ with the same torrent file (with memory reader) and started to fake upload until I have reached my desired amount. After closing RM+ I have started seeding the same file via utorrent again.
Checking my ratio on the tracker page, showed me it has dropped from 1.55 to 1.49.
Here my questions:
1. Can someone tell me, what happens when I close RM+ and start seeding via utorrent again?
2. Can I avoid this mistake by closing and restart utorrent?
Maybe you will ask, why in the hell I would continue seeding via utorrent after I have fake seeded my desired amount? The answer is the private tracker wants me to keep seeding each torrent for two weeks irrespective how much I have seeded already.
1. Can someone tell me, what happens when I close RM+ and start seeding via utorrent again?
In general there is no harm running uT after Rm+ finished seeding just avoid running them both at the same time (for the same torrent) and you'll be safe. and always use the memory reader.
2. Can I avoid this mistake by closing and restart utorrent?
what you did has nothing related to the ratio dropping. just review what happened this day because what you're saying has nothing to do with the dropping in ratio.
Thx a lot for your replies.
As you have mentioned Lucius I have checked my downloads and found out that files were downloaded from a third party, hence my account was hacked.
After changing my PW, everything works well.
Thx a lot.
Bookmarks