From what I could understand from your explanation attempt, mIRC 'stops' the execution somewhere in the code without being told to do so.
There are 3 ways to make mIRC stop the execution:
- HALT
- RETURN
- an error
You said you did not get an error message, and since you are surprised by the execution abortion, I assume there is no RETURN or HALT in the event code.
That still leaves one cause other than a bug left: somewhere in the execution path mIRC encounters a HALT command.
And the execution path is ALL code mIRC goes through, including any called aliases, no matter how deep.
So if you called alias A from this on connect event, and alias A has in its code a call to alias B - which performs a HALT command, then mIRC just stops the execution.
In your last post here:
on *:connect:{
echo -a $server $network
you said you got neither of the echo's.
There are 3, but above one is unconditional and has no alias calls with possible HALT command before it.
If you don't get the first (you said 'neither' so...), then the most likely reason is the event not being executed at all, due to another on connect before this one in the same file, or a missing } in earlier code, or a switched off code #group, there are quite some possible reasons.
So are you sure there is no 'serverhere networkhere' text in active window?
The remaining non-bug reason could then be an /echo replacement alias that has a HALT.