hixxy

You're right, $!(|) works fine Try this mate: //timer 1 1 echo -a a $chr(124) b As you will see it throws a "b unknown command" error. The way to get around this is by using $!chr(124) //timer 1 1 echo -a a $chr(124) b evaluates $chr(124) to plaintext "|" when the /timer command is first executed, then plaintext "|" is evaluated to special meaning "|" at the time that the timer fires. Using my version, //timer 1 1 echo -a a $!chr(124) b evaluates $!chr(124) to "$chr(124)" when the /timer command is first executed, then $chr(124) is evaluated to plaintext "|" at the time that the timer fires.

You must be doing something wrong, because it works fine for me: //topic # test $chr(124) test | timer 1 1 echo -a $!chan( # ).topic Output: * Timer 1 activated (13:23:54) * hixxy changes topic to 'test | test' test | test * Timer 1 halted The example you posted is not the same as what I gave you.. for your example to work of echoing a pipe as plain text you would need to do this: //timer 1 1 echo -a hahha $!chr(124) hahha Or: //timer 1 1 echo -a hahha $!(|,) hahha Same problem as I demonstrated in my earlier post, you would need to use $!chr(124)

FYI you could have just done this: .timer 1 1 hadd cProt TOPIC $+ # $!chan( # ).topic Timers evaluate everything twice (once at the time of the execution of the /timer command, and once again at the time the actual timer fires)... so you need to make sure anything you pass to it is escaped. You can see what I'm talking about by typing these two lines of code in your status window: //echo -a $!me * this echoes the literal text "$me" //.timer 1 1 echo -a $!me * this echoes your nickname.

The problem with your $iif() statement is that you have closed the bracket too early: did $iif($did(96).text) == $null,-b,-e) $dname 97 I have highlighted the brackets in different colours so you can see which ones are matching brackets and which aren't. You need to remove the second blue bracket in order for you to have a bracket match. As for your code, it seems fine. The $left() thing you're doing doesn't make a lot of sense but it shouldn't cause any problems with your code. Maybe the problem lies elsewhere, try posting the entire on dialog code block.

When correcting people you should make sure that you're correct first. Identifiers like $nick, $chan, $dname, $did, etc, are passed on to any custom aliases that are called from within an event definition where that identifier was filled. You can check this by using the following code: dialog t { size -1 -1 300 300 } on *:dialog:t:init:*: update alias update echo -a $dname Then just type "/dialog -m t t" without the quotes and you should see the letter "t" (the dialog name) echoed in the active window.

Perhaps vista is stricter then, but this is also the way things should've been done on XP and earlier OS's as well.

It's not a change to support vista, it's a change to become an application that's compliant with Windows. If you run mIRC from a non administrator account then you may find that it doesn't have permission to write to the Program Files folder, however it IS allowed to write to the Application Data folder or Roaming folder. The only thing that has changed is the location of the directory, you can still use $mircdir as long as everything has been installed correctly. You don't need to use the location of the exe.

No you don't. //if ([*] iswm [x]) { echo -a WEJKDIKSDJH }

Seeing as they both have a common message in the kicks ("Banned for <time>") you could always try this. on !*:kick:#:{ if ($knick == $me) && ($regex($1-,/banned for (\d++)(?= |$)/i)) { .timer 1 $regml(1) join $chan } }

There's no reason why it should be staying open, but your code is a bit yuck. The way you've written it will trigger the script if somebody types !joins or !parts. I'd use something like this instead: on admin:text:!join ?*:#: join % $+ #$2 on admin:text:!part ?*:#: part % $+ #$2

What do you mean? a { b { c } } Becomes: a { b { c } } When you hit the "{ }" button. What else are you talking about?

on *:text:!readsug:#:{ var %handle = handle $+ $ticks, %file = complaints\suggestion.ini if (!$isfile(%file)) { msg $chan There is no suggestions file to read from. } else { .fopen %handle %file if (!$ferr) { while (!$feof) { msg $chan $fread(%handle) } .fclose %handle } } }

No you can't. "me:" is an event prefix (much like !, & and ^), not a user level, so you would have to use this: on me:*:join:#:{ } However, he wanted to do something when he joined, but something else when somebody else joined, so his own code was perfectly fine for that purpose.

Perhaps the line doesn't end in a CRLF, which would cause no bytes to be read into &x. Try using sockread -fn instead. What The Gate Keeper recommended should stop the error, but it might mean that you miss data. TGK: Fyi, you could use $sockbr there instead of $bvar(&x,0)

I see, well I wouldn't know about that. But you can send multiple messages the way I showed, which is just as good.