Im not really sure what your on about about the use of the & symbol on the ON INPUT, any on input that preceeded a ON &*:INPUT that /halt or /haltdef 's well cause the & event to not trigger. In some n inputs this is what you would want, in others its not, for example
If u had a script that checked u were on a channel or pm and u didnt enter a command and had said "BLAH" that it would change that to "BLAB" and /MSG that to the channel/pm, then should a script before this have halted the input then you should use the & to stop yours sending the message again (assumption is the other script is processing the text)
If how ever you had say a auto AFK script, that sets a named timer for 10 mins everytime you say something, then you would not include a & becuase this is ment to run regardless of if any other on input halted the input or not, as its only concern is that you actually typed something.

Invision has assumed becuase thats all it can do, that if someone has halted the input before it, it should not attempt to process it.
Some of there code should not be in this event as it appears to deal with away timers so should be tripped regardless of halt(def) in inputs before it.
Code:
if ($r.set(Away,Auto.Away) == On) && ($isnum($r.set(Away,Auto.Away.Delay)) == $true) && ($server != $null) { .timerAuto.Away $+ $iNetwork 1 $calc($r.set(Away,Auto.Away.Delay) * 60) auto-away } | w.mirc Wizard Advise 0


The only real way i think you well be able to make both scripts function correctly is to adjust what you send to the play command file, so you push the actual command to an editbox (rather than execute it) thus letting the ON INPUT deal with it again /EDITBOX -n, this might produce problems of its own, im not sure, maybe you could create a hidden window in which you can push the commands to.

ex, your play file would have looked something like...
/msg #chan a verylong line i have typed ..... has been cut
/msg #chan here and so its come as two lines of text.

so now you want it to look like

/editbox -n @hiddenwindowname /msg #chan a verylong line i have typed ..... has been cut
/editbox -n @hiddenwindowname /msg #chan here and so its come as two lines of text.

(it would be clever to have your ON INPUT specificly ignore any ON INPUT comming through that window as well to ensure no recursive loop that might appear due to un forseen length adjustments of maybe the channel name etc)

The idea is that you caught the input, and your sending it back through a second time, since all of yours well be commands, they can be executed from any window.