Originally Posted by
anon
The problem is, you don't have a lot of choices. The ideal scenario would be one where both peer_id and key are individual and volatile, because then you could use the same port and look 100% realistic. However, in all major clients, at least one of them is either global or persistent. A client where both are global and persistent would also work in theory, except that mRatio does not support the input of "foreign" identification data (only exception: memory reader) and BiglyBT Extreme Mod only allows a custom peer_id. Keep in mind this wasn't designed to be used alongside another program.
I was going to write a long reply about how it could be done with uTorrent if you resort to several complicated workarounds that have considerate room for error, but it's not worth it. I suggest either separating your activity so that you never need to "move" torrents from the same tracker between programs, or using the BBTEM's ratio tool instead of mR.