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.
RMP 1.3 Via memory reader now is safe to use with all included Bittorrent clients even those change peer-id and / or key per torrent and / or start ,
You can also use RMP 1.3 without memory reader while using another Bittorrent client (Its safe now).
Lucius did a perfect work .
Last edited by mmmmm; 23.05.15 at 18:43.
Reason: add more info
Busy , new things always comes
Its the time for personal life ,Still here from time to time, Greeting for everybody All .
You can also use RMP 1.3 without memory reader while using another Bittorrent client (Its safe now).
You can use this version without memory reader if you use it alone without the real client beside, but if you have the real client opened it's better to memory read it then RM+ will check if the peerid/key is global or not and will decide if it's safe to use the same peerId of the real client or just use the (safe) generated one
I think this is the most secure behavior of a ratio tool (respecting the global/not global peerId)
is this better than the standard ratiomaster 1.9.1 ? works better ??
You can consider RM+ 1.0 as RM 1.9.3 , simply it is an updated and much more secure than regular RM.
Simple equation, by using rm+ you'll have just the same rm with new features and new security measures.
Just take original rm then add the changelog in the post #1 in this thread and you'll have RM+
as The248 said before, the tracker can detect RM from the first announce, while all those bugs got filled in RM+ (if you know one that doesn't contact me)
Thankyou very much sir! unfortunately i can't use this version with torrentday since i can't put the tracker manually
TD uses 2 trackers one HTTPS(the first one) and one normal HTTP,when i select the torrent just gives a error: this torrent has no http tracker URLs.
older versions just give blank tracker field but i just put the tracker in manually.
Thankyou very much sir! unfortunately i can't use this version with torrentday since i can't put the tracker manually
TD uses 2 trackers one HTTPS(the first one) and one normal HTTP,when i select the torrent just gives a error: this torrent has no http tracker URLs.
older versions just give blank tracker field but i just put the tracker in manually.
I modified the tracker loading code and it supposed to work well with TD, we have tried it many times.
Can you send the torrent to me via PM
I modified the tracker loading code and it supposed to work well with TD, we have tried it many times.
Can you send the torrent to me via PM
[Edit]
Never mind, I work on it
Oh don't worry you did an awesome job,also got it kinda working by editing the torrent file and removing the https tracker.
But you still want the torrent(original with the 2 trackers)via PM?
Oh don't worry you did an awesome job,also got it kinda working by editing the torrent file and removing the https tracker.
But you still want the torrent(original with the 2 trackers)via PM?
You just need to copy the http one to the announce no need to remove the https one, RM+ ignore the https urls.
No Thank you, I already fixed the bug and the hot fix will be released very soon
Thanks for reporting greenberet
I had a problem with Original RM 1.9.1 (maybe a bug)
I started a torrent with upload speed between 50-500 kbps (random) used memory reader(for announce, used another torrent from another tracker) and nothing was ticked in NETWORK TAB except bind to ip.
I stopped a torrent @ 111.12kbps and closed RM. After sometime i restarted the torrent with same speed and got my a/c disabled after 5 mins.
Maybe the same speed gave me away.
So i think i should have changed speed before restarting to cheat. But maybe there is some speed bug in original RM. Did u notice this @Lucius and other members ????
Bookmarks