I have an on connect block in one of my files, it's all that's in there besides the on start block.. and every time I join a new network, it explodes violently (ceases to work normally) because of one if statement I have in there at the top.

Code:
if (!$istok($eval(% [ $+ [ $network ] ],2),$me,32)) nick $eval($gettok($eval(% [ $+ [ $network ] ],2),$r(1,$numtok($eval(% [ $+ [ $network ] ],2),32)),32),2)


The idea is that, for networks I frequent I have added that bit of code so that I log into a nick that is actually mine, and it wil pick from the random list of the ones I have for any particular network.. anyhow.... to the bug:

When say, I've added a different if statement a ways down beneath that one, such as if (($network == blah) || ($server == blah)) { code } that is supposed to execute for a network that I don't have such a variable for because I only have one nick and change the nick within the if statement itself. HOWEVER, because of this bug, and I do insist it's a major bug that shouldn't be happening, mIRC will stop executing the entire rest of the code block just because there is no %blah to match that particular network, and so that other if statement is never evaluated. (best I can figure as to why it explodes)

Of course I've made the minor adjust ment of having that code line as the last if statement, but that doesn't quite work when I'm trying to change nicks [i]before[\i] I identify, like in the case where /server -m doesn't remember the nick for that server but uses the one from the server where /server -m was issued, which on start is the first network of the networks you're in when you quit (perhaps this should be fixed to, let it remember the nick used for all the networks you're on, as some of us can't use the same nick on all servers.)

I don't feel that making a seperate on connect block in a seperate file should be needed, this is a bug that has driven me insane for the last time.. ;_; I had the error before and could never figure out a solution till I ended up adding a var for that network and the error stopped happening, so I ignored it and went on, but since it happened again, I'm convinced this is a major bug that needs to be addressed in the next version of mIRC.

Thanks,
Sugiura Midori