Dear Theodore R. Smith:
It has come to my attention that you're trying us to debug your code. Of course, to get so, and after Xaignar, one of our admins, has already told you which parts of your code are wrong, you have come here and told people to download your clients.
Hum....
In the original post, you also spread lies and flames again. I'll reply them there instead of here.
Theodore, your client is buggy. Xaignar told you where is the bug, I told you where is the bug, it's a on-liner and you could have fixed it easily just by changing that line. Instead, you come here telling people to download your client.
Hum....
You also refuse to download the client you are banning to test. It's like me telling eMule developers to debug aMule because I am banning them. Plan senseless and stupid, sorry to be so rude.
If you want to debug you client's communication with aMule, download aMule, run it, run xMule, and test the communication. When I need to check network behaviour, I do so with eMule, mldonkey, lphant, edonkey, or any other significant part of the network.
I am sorry, but improving your clients beyond the kindness of telling you where the bug is (which, oh, surprise! catalogs aMule as a leecher/thief/etc on the new xMule version) it's not on our roadmap.
Instead, we should ask you to apologize because your client spreads lies to the users against aMule. Knowing your past and present, it's hard to me that xMule logging aMule (and showing to user) as " leecher, invalid eMule or irregular Donkey" or "suspicious name change" it's not intentional, and I don't really care anymore. It's an insult to the project, developers, and users, so please I ask for a public apologize on your frontpage.
That said, going to reply your flaming post.
P.S:
for survival xMule was forced to camouflage itself as eMule for the greater part of 2004
xMule never had to take such action. xMule was being disconnected from sources because xMule was sending bad file info. Same for servers, where xMule was claiming to have network protocol capabilities that didn't have. So servers were disconnecting you.
I'm waiting for the "xMule can't browse eMule >= 0.40 shared files anymore!" claiming you once more are victim of a conspiracy instead of checking your network code to complain with protocol.
PLEASE stop blaming the rest of the world on your mistakes.
