on 2022/09/24 11:37:24 AM
Hmm, are you sure the torrent is V2 or V1+V2?
Working fine on my end, if the torrent is v1 it'll just place "1220" in the place where the v2 hash would have been.
I do not know what the torrent is. But5 this issue remains for v3.14
Might it be possible to internally analyze the meta data, determine that and if it does not support BTv2, then gray that share option out?