downloaded elsewhere to seed here, but it still shows as downloaded on my ratio

[drftnv]

just wondering if i did it wrong or if its a bug?

recently my ratio was looking a bit bad, so i went through the list of offers, chose a few good looking ones and sourced them elsewhere. i checked the file hash and got matching copies. recently one of the torrents was approved, so (while logged in) i downloaded the new .torrent, started it momentarily so it created the folder, stopped it, copied the already downloaded files into the new folder, then started the new torrent. i'm using rtorrent, so i hit hash straight away and it went and checked the ~5gb of files, marks it as done and started to seed.

later that day i check my ratio on bakabt and it shows that i've downloaded the whole thing from bakabt, while my client showed only a couple of kb.

ordinarily i'd not care, but i'm trying to resurrect my ratio here...

[Tiffanys]

You need to add the torrent as stopped and do a force recheck. Once it finishes checking it'll change it to paused then you can start it.

If you don't add it as stopped and do a forced recheck first it'll just redownload everything even if you already have it.

[Freedom Kira]

Actually, this sounds familiar. I've heard similar stories before. I can't remember what the conclusion was, but I do believe it's a bug.

[drftnv]

i'll try adding them without using the watch directory next time, but i don't think thats it. bakabt just wants me to have a horrible ratio (that my excuse and i'm sticking with it!).

[Freedom Kira]

If anything's the issue, it's your client. You're not so special that the tracker would want to behave differently just for you, believe me.

Anyway, if you pick the right key words to search on the forum, you might find some old threads made by other people who experienced the same issue and what the conclusion was.

[drftnv]

apologies, its rather remiss of me, not sure why i didn't search first.

i did find a thread  from 2009 talking about a bug in rtorrent. if the bug has survived since then its now evolved from a bug into an "undocumented feature". considering the 2009 bug related to the torrent being started before hashing, and that is precisely what i did, clearly i did it wrong.

[Big Teeth]

The average bittorrent-client has 'some' intelligence.
When you add a torrent to the client AND the content is NOT already at the location where the client expected it to be, the client 'knows' the content is NOT there.
When you later add the content, the client still remembered the content wasn't there and won't look for it again.
Thats why the forced hashcheck is required to let the client figure out the content is there, for what reason.
When the hash doesn't match it now knows for sure downloading is required

When the tracker 'shows as downloaded', the client has told the tracker there was some downloading done at some point.
YOU could/should have seen the client had started downloading something.
More exact YOU told the client to download. By setting (autostart torrents) or manually.

Bottomline: don't blame the tracker or your bittorrent-client. YOU are to blame!
Never let a client autostart torrents. It can screw things when YOU make a mistake.