Would someone tell me why, when i join several channels at one time the 'Topic was set..' text is shown twice?
example:
08:29 • Topic was set by Same on Wed Feb 26 23:24:30 2003
08:30 • Topic was set by Same on Wed Feb 26 23:24:30 2003

those are my raws

raw 332:*:{
echo -l $2 $_t • 3Topic ' $+ $3- $+ '
halt
}
raw 333:*:{
set %topic. $+ $2 $3
halt
}
raw 329:*:{
echo $2 $_t • Topic was set by %topic. [ $+ [ $2 ] ] on $asctime($3)
halt
}

I beleive this is a mIRC bug, rather than your script, but I'm not very sure if it was fixed..

/debug might tell you why: type /debug @debug , then connect and join channels. See what's happening in the debug window.

yes i used debug earlier, the raw appears once for every channel so ...maybe you could test it? it'll be enough that you put those raws to remotes and type /join #a,#b,#c,#d,#e,#z ;-)
This problem appears on DALnet, those raws almost don't work at all on IRCnet.

ALSO...i don't know why this happens, but sometimes it does happen, and sometimes not

If you're only getting it once in /debug -p @Debug, then your problem is with your scripts. /remote off. Then try joining channels again. You'll only see one copy. /remote on. Next, you need to find a raw 332:*: in every file in your script. That is the event that's making it show up twice.

i have only one script file (i installed fresh copy of mirc) and i'm making my own theme. And it's not raw 332 but 329 and...when i change anything in the raw 329 line i shown before, those two lines both contain changes...sooooo.... i don't like such situations when i really don't know what's going on :-|

You're right - it's 329. You're halting the event, so I don't really know why it's repeating.

ive noticed that on a couple networks ...... it calls the same info twice on channels ..... its probably more of a ircd bug than a mirc bug ...... its only on a few networks ive seen that it does this ...... if u turn ur debug window on and join a room u will see the raw is sent to u twice ,,,,,, again i dont have a clue why ..... unless its an ircd error