I'm getting a torrent with 12 peers all at 99% for a day or more (and getting good download speeds). Damn to hell the seeder who bailed at that point... But it cannot be possible that ALL those peers between them have 100% of the file, otherwise they would all be seeding by now or have left off leeching.

So why does the main properties page for the torrent say there is "1.000 Available Copies"? That would be 100%, which must be wrong. The fact that it gives this WRONG information with three decimal places of accuracy is also rather fatuous. At least I can see it is wrong because when there is a complete copy of the torrent spread out or with at least one completed seeder the numbers of "Available Copies" add up beyond 1.

But there's clearly an addition/display/rounding error right there in this case (and if it's rounding, then the three decimal places is even more ridiculous). Using 2.31 right now, will be updating shortly.

Thank you *NOT* for your oh-so-useful contribution to this BUG REPORT. Do you understand what that is? A bug is not something to be "chilled" about. It's something to be fixed so that software improves and gives useful, accurate information to the user.

The error is confirmed - download stopped at 1 missing piece out of 4801, torrent properties "Details" tab still showing "1.000 Available Copies", ie. apparently 100%. So this is a dumb rounding error where it should NOT be rounded up if the torrent is incompletely seeded.

bug reports are certainly appreciated, and welcome.

However, supererogatory, superfluous hyperbole, i.e. screaming "WRONG", "dumb", "fatuous", "ridiculous", "meaningless", "a joke", "amateur", "pseudo-accuracy", "you (the DEV) are too lazy", "useless", "distracting", "you do NOT provide" and a demanding "Give us..." which tend to denigrate, disparage and demean the dedicated DEVteam have NO place in a bug report.

My advice is take a chill pill and show some damn respect Ingrate.

I will not debate you until you change your tone.

Was this fixed? Because I have turned off "include local count for availability"... And sometimes I see "Remaining Byte" column sit at 1 ... for a while when finishing a download. I imagine this is because the last pieces are downloading/hashing.
Can anyone else confirm?