i was making a script for mIRC that cut text into several messages to send, so that it does not appear cut off for other users. There was another topic dealing with this at one point (and only one, as far as i know), but i do not believe this bug has ever been addressed directly.
i noticed that when you have a string that is approximately 920 characters long, mIRC cuts it off at the token nearest to this point (i'm not actually sure of how it decides to cut it) and sends the string. somewhat annoying, but fine up to here. when it automatically sends the string, however, it does not trigger an ON INPUT event, it simply sends the text.
also, if you have one non-broken (spaceless) string of characters after the 920th characters, it does not cut it, which is what led me to believe that it only cut at token points. once again, all well and good, but when you get to 998 characters (assuming i counted correctly. i could be a few off), the string is completely deleted; it does not send, and it does not trigger an ON INPUT event.
other clients do not have these types of input length restrictions, but as mIRC does, and it far exceeds that allocated for messages in the RFC, i think we will be able to live with them, however, it is my belief that the bugs associated with these limits should be addressed.
thanks, hope this helps.
