I feel like I may be repeating myself but yes I realize that mIRC was designed to be a client and not a bot platform but other than this window amount limitation I am very pleased at what it can do in this arena. The feature suggestion about a single channel window was only made because I believe that some of the operators rely on the channel window object to evaluate statements and return values for some identifiers - I could care less if there is a channel window open as I rarely ever need to see it at all.
and for Danthemandoo: mIRC runs VERY well as a bot and I would like to continue using it as a bot since we host more than 600 channels. Currently we have 40 bots and there has been countless hours of work done on scripts we have used and on our home grown scripts. There is little time to start developing on a completely new platform for us when there are many feature requests that we must fill as well. I appreciate you taking the time to post and give me some insight into your thoughts but if you can't spend the time to carefully read my *really long* post then please refrain from spending the time to make posts that imho seem a little half assed. This is my mIRC feature request and I purposely created the post long enough to describe my feelings on it and why I think it should be a feature because aside from being able to support more than 200 channels per computer there isn't much that I have seen and eggdrop can do over a mIRC bot. Unfortunately every eggdrop advocate is either to enraged to show me something an eggdrop can do over a mIRC bot or lacks the desire to do so. I don't blame anyone for not showing me the error of my ways but if you are going to make a statement about an eggdrop vs a mIRC bot for the love of god back it up with some actual information and specifics instead of just saying they are better for the job because they are specifically made for the job. Also, please don't post links to eggdrop sites as I have undoubtably browsed them before, state your own specifics and information if you choose to do so.
Our boxes don't need to be rebooted (except for windows update.. big deal) and in our case mIRC doesn't crash. Our mIRC install/scripts are stable and secure despite everyone's idea about mIRC. In some cases it will get stuck in a loop from a script change not thought out well, which is promptly cured by fixing the script... but just like everything that is in development (yes omg eggdrops/tcl scripts!) I am positive there are problems like that.
Ultimately, if it were desired I could see having a different type of mIRC license for those who use mIRC as a bot platform for a service. Since after all, in our situation, many people are using our mIRC indirectly. That would just be another perk to supporting mIRC bot services with a feature here and there (again only if it is programatically sane). I'm not asking anyone to go out of their way for this group of mIRC users, I'm only asking if a feature like this could be added in the future
.
