With /parseline, -t('as text') or -b('as bvar') is required. This is inconsistant with other mIRC commands that attempt to assume the nature of the input
Yes, this is by design, I chose to force you to make it clear whether the parameter is text or a binary variable.
With /parseline new lines in an input do not delimit messages to be parsed
Again, this is by design. You need to specify each new incoming or outgoing line separately.
With on PARSELINE, theres quite a few inconsistancies I'm not sure how to explain them other than showing through code:
The on PARSELINE documentation does not mention halt/haltdef and they cannot be used for this event. This is by design. Remember, you can use /parseline to change the current event to anything you want, including an emtpy line.