Hello,
Check this screenshot and you will understand what i mean.
- Thanks!
This behaviour is clearly documented in the help file.
The on START event uses the same format, and triggers the first time a script is loaded and every time after that when mIRC is run.
ok i did not saw that, but why mirc do this?
the ON LOAD and the ON START are different events !
It's always been like that and tbh its just a matter of definition.
Please note that this doesn't lead to reduced functionality, e.g. you could easily script the load event to temporarily disable the start one.
The ON START event will trigger every time the script is started. This is triggered when you load a script, since the script has to start when it is loaded.
When you start mIRC, the scripts are already loaded, thus the ON START event triggers, but the ON LOAD event does not.
When you load a new script (usually using File -> Load, or /load -rs <script>) then the ON LOAD event triggers as well as the ON START event.
A simple workaround to prevent mIRC from triggering the startup event after loading a file for the first time would be:
on *:load:{
set %nostartup $true
stuff
}
on *:start:{
if (%nostartup) { unset %nostartup }
else { more stuff }
}
edited: Sephiroth_'s is a smart way than mine
