The good thing about an eggdrop, aside from the features they have is that they can handle being in dozens of rooms whereas in my experience, a mIRC bot can handle about 20 quite well. As for my experiment, there was 0% lag (or close enough to it) as I did it on my LAN. The trouble with many distributed mIRC bots is that they come complete with dialogue based settings arrangements and are usually chock-full of .INI files or global variables to store the settings such as the number of lines in BLAH seconds before a flood kick is triggered, etc. And that has to slow mIRC down a bit. I don't believe in that method though and my mIRC bot has all the settings coded into the scripts themselves.
In addition to what I said above, my network uses all of what Starbucks said above, mIRC, Eggdrop and Perl (SecureServ). Each has their own roles and each do that particular role better than the other two.
Lastly, yes, you are right about the partyline script being BIG in mIRC though for the life of me I do not understand the concept of that feature and have never used it.
BTW: In reply to the original post here, I would think that it is perfectly okay to either sell mIRC bots, rent them out or rent out hosting for them though personally I am against the former if only because I am accustomed to the understanding that open source (which a mIRC script is) should be free of charge. At any rate there's little, if any, hope of enforcing any licence on a mIRC script of any kind.
