What's the tracker status (shown in RM+) when you stop the torrent, and after you restart it? Also, what does the error log say? Knowing the tracker's name and emulation you're using may also help.
Printable View
What's the tracker status (shown in RM+) when you stop the torrent, and after you restart it? Also, what does the error log say? Knowing the tracker's name and emulation you're using may also help.
When I restart the torrent, the tracker status becomes all 0 just like I am starting fresh new leaching. The torrent typically stops when the auto-stop criteria meet (like 0 seeder), or there's an error in the tracker response (like an empty response). Also, even when the torrent is not stopped and finished normally, the tracker often shows 0.01GB difference between the downloaded and actual file size. This could be very concerning as it is not normal. :frown:
How about those =]
This is very worrying if the completion percentage also drops to zero. Here's where the information I requested above could be of great assistance.
Possibly a bug, although a difference of ~10 MB is acceptable for a GB-sized file. Real clients can also overdownload due to hash fails (you'll see this mentioned in the FAQ of most TB source-based trackers), but these days they place this extra traffic in the "corrupt" parameter, which RM+ always reports as zero.Quote:
Also, even when the torrent is not stopped and finished normally, the tracker often shows 0.01GB difference between the downloaded and actual file size. This could be very concerning as it is not normal. :frown:
Sorry that I didn't supply enough information.
When you say error log, do you mean the log for each torrent?
I just started a new torrent, leach to 5% and stopped it.
It shown as below:
Then I restart the torrent:Code:[2020-06-07 16:59:44.8214] [INFO] [587] : Torrent data saved successfully.
[2020-06-07 17:01:14.2522] [INFO] [587] : Starting torrent ..
[2020-06-07 17:01:14.2522] [INFO] [587] : Sending Command to Tracker..
GET /announce.php?passkey=xxxxxxxx&info_hash=IqU%00%f3%3e%eb3P%06%a5%dd%bd%09%26%c8%e7_%f4%e9&peer_id=-UT2210-Bb%08%0c%18%fe.w%dcF%21%df&port=57530&uploaded=0&downloaded=0&left=17233152780&corrupt=0&key=643074C9&event=started&numwant=200&compact=1&no_peer_id=1 HTTP/1.1
Host: announce.leaguehd.com:443
User-Agent: uTorrent/2210(25154)
Accept-Encoding: gzip
Connection: Close
[2020-06-07 17:01:25.3719] [INFO] [587] : Received 1 Seeders and 84 Leechers.
[2020-06-07 17:05:14.6711] [INFO] [587] : Stopping torrent by user request..
[2020-06-07 17:05:14.6711] [INFO] [587] : Sending Command to Tracker..
GET /announce.php?passkey=xxxxxxxx&info_hash=IqU%00%f3%3e%eb3P%06%a5%dd%bd%09%26%c8%e7_%f4%e9&peer_id=-UT2210-Bb%08%0c%18%fe.w%dcF%21%df&port=57530&uploaded=700628992&downloaded=1342177280&left=15890972672&corrupt=0&key=643074C9&event=stopped&numwant=0&compact=1&no_peer_id=1 HTTP/1.1
Host: announce.leaguehd.com:443
User-Agent: uTorrent/2210(25154)
Accept-Encoding: gzip
Connection: Close
The trackers I use are listed below:Code:[2020-06-07 17:07:07.8687] [INFO] [587] : Starting torrent ..
[2020-06-07 17:07:07.8687] [INFO] [587] : Sending Command to Tracker..
GET /announce.php?passkey=xxxxxxxx&info_hash=IqU%00%f3%3e%eb3P%06%a5%dd%bd%09%26%c8%e7_%f4%e9&peer_id=-UT2210-Bb%08%0c%18%fe.w%dcF%21%df&port=57530&uploaded=0&downloaded=0&left=17233149952&corrupt=0&key=643074C9&event=started&numwant=200&compact=1&no_peer_id=1 HTTP/1.1
Host: announce.leaguehd.com:443
User-Agent: uTorrent/2210(25154)
Accept-Encoding: gzip
Connection: Close
[2020-06-07 17:07:19.3184] [INFO] [587] : Received 1 Seeders and 85 Leechers.
announce.leaguehd.com:443
tracker.pterclub.com:443
pt4.moecat.best:443
And the client profile I use is µTorrent 2.2.1.25154
Could it be the memory reader function as I never used it?
I also have another client downloading the file that I actually need.
The client is µTorrent 2.2.1.25273
When I type the memory reader, it shows my local client is 2.2.1.13644.
I am feeling there could be some bugs here but I don't know what to do now.:frown:
Based on those error logs, the "left" value is resetting itself to 0% finished levels when you restart the torrent. This should never happen and must definitely be a bug. Let's wait for Lucius to read this and comment; in the meantime, you could try using mRatio instead.
The memory reader has no bearing on this issue, although it's still highly recommended to use for uTorrent. If your client emulation doesn't match the build you're actually running, then fix that.
Thanks for the suggestion.
I haven't used mRatio but will look into it.
Is there any file or other information I can supply that is potentially useful?
update:
I tried the mRatio and it does work as normal.
It reports the progress as normal and hopefully won't cause over download.
I will use it for now.
The only thing is mRatio does not have a speed control when there are no leachers.
So I will have to manually stop upload to avoid obvious cheating.
Look harder, because that setting does exist :gwink: Unfortunately, though, it cannot be relied on because 1. not all client emulations support scraping the amounts of seeders and leechers; 2. if scraping is not supported, mRatio relies on the tracker giving this information anyway (which is not guaranteed) but parses it incorrectly if it does; 3. it's impossible for any ratio tool to react to changes in the swarm in real time like an actual client would.
Accurate counting can be happened and was on my to-do list to be added to RM+ by the way :)Quote:
3. it's impossible for any ratio tool to react to changes in the swarm in real time like an actual client would.
Actually, RM+ connects to the swarm to some level to avoid some detection techniques.
Modding a client is better because you only have to focus on adding cheating features. Everything else is already taken care of for you. Things are easier (although not necessarily easy) and there's less room for errors. Compare that against writing a ratio tool and having to add all base functionality yourself, then account for every possible error scenario and every quirk in every client that is emulated. I actually attempted to create my own tool back on 2010, and gave up halfway through because of this... although I did get it to correctly emulate uTorrent 1.8.5 and send announces to the tracker, making it theoretically usable, so yay me :ninja:
Anyway, the downside is that you're locked in to the client you chose and must accept its base functionality, OS support, tracker whitelist status and so on. (The question "can I use Extreme Mod in uTorrent?" and its answer "no, you can't" have been thrown around a few dozen times since I joined this forum.)