Sorry, but when a user asks how to solve a problem, I usually take it to mean they want suggestions as to how to solve their problem. Therefore, suggesting how to solve your problem ("code your project") seems completely reasonable to me. When offering a solution to a problem, I leave every option on the table. You should too. This includes scaling back your expectations. I apologize if I didn't initially realize you were too hard headed to allow for this option. I see now that your goal isn't to actually add extra functionality to mIRC, but instead to perform a purely technical exercise in extending mIRC's internal implementation and builtin commands without any change to the existing API.
FWIW I've already offered countless suggestions that meet your goals.. why don't you put *your* "money" where your mouth is and start getting to work on implementing them rather than waiting indefinitely for a "viable" suggestion? You've already been told by Khaled himself that you basically have no alternatives. Why are you still "waiting" for an answer?
Just as a sidenote, I wouldn't hold my breath for Khaled's suggestion. First off, it's not yet implemented, so that makes it rather useless to you. Secondly, even he acknowledged many critical flaws with the suggestion, so it doesn't seem very likely that it will ever be implemented. Of course, you're free to continue waiting on mIRC updates.
