Thanks so much, jaytea. I probably wouldn't have been able to identify the problem myself, even if I had been actively checking...

it is possible there were some changes to the ignore command since this was posted, Im not really sure

well, its not actually !listen, its listen

whats wrong with just

if (!@Highlight) { window -hw2 @Highlight }
        aline -hp @Highlight $fulldate 6Action Highlight: 00 $+ $1- 10by 12 $+ $nick 10in 7 $+ $chan 10on 3 $+ $server $+ 9( $+ $network $+ )
      }

?

if (!@Highlight) {
        window -hw2 @Highlight
        aline -hp @Highlight $fulldate 6Action Highlight: 00 $+ $1- 10by 12 $+ $nick 10in 7 $+ $chan 10on 3 $+ $server $+ 9( $+ $network $+ )
      }
      else {
        aline -hp @Highlight $fulldate 6Action Highlight: 00 $+ $1- 10by 12 $+ $nick 10in 7 $+ $chan 10on 3 $+ $server $+ 9( $+ $network $+ )
    }

aaaand

 if (!@Highlight) {
        window -hw2 @Highlight
        aline -hp @Highlight $fulldate 4Text Highlight: 00 $+ $1- 10by 12 $+ $nick 10in 7 $+ $chan 10on 3 $+ $server $+ 9( $+ $network $+ )
      }
      else {
        aline -hp @Highlight $fulldate 4Text Highlight: 00 $+ $1- 10by 12 $+ $nick 10in 7 $+ $chan 10on 3 $+ $server $+ 9( $+ $network $+ )
    }

You really should get into the habit of using $+(1,2,3) it looks cleaner :| other than that its so simple theres not much to rip on.

I take it back. Why do you have the same line twice? >_>

Updated

hm...whats line 14? I must be looking at the wrong one :S

this whole thing could be 10-15 lines...

on @*:TEXT:!lockdown*:#:{ if ($2 == help) { ... }
  elseif ($2 == orange) { if (!$3) { ... }
    elseif ($3 == off) { ... }
  }
  elseif ($2 == yellow) { if (!$3) { ... }
    elseif ($3 == off) { ... }
  }
  ; And so on
}

or even shorter if you use $iif

UPDATE! This is my first time using regex at this level, so pointers would be appriciated

Nice script :D few minor things though: $$1 isnt really necessary since the menu fills in $1 for you, not really sure about query but Im fairly certain nicklist menus dont have a $2, so that can probably be taken out, since you use query in your menu, $chan will return null but since you use $1 after it in all of them that will serve as a fall back so it will probably still work, just something to keep in mind, also, you should probably consider shorter texts, so the pop-up isnt huge (e.g. [-Oops! I lost my mobile number! Could I have yours? -] could be Number or something), oh and you forgot a few brackets on the end. All in all though not bad

OKI! This bad boy is gonna get a complete overhaul, everything is being redesigned and rewritten, hopefully that will fix all the bugs people have been having, stick around for updates :D

...why...just...why?

UPDATE

lol, that movie was amazing.

The Whistler, the script runs on sockets, meaning it creates its own bot and uses that to link, you dont have to have a bot running, thats the beauty of it :)

Also, if no bot is joining your channel, make sure the nick it is trying to use (LinkBot by default) is available, as of now there is no support for alt nicks though, this will be added to a future update

ew, goto :S also you could probably eliminate 3/4 of the elseifs just by using else >w>

UPDATE!

A quiet little channel link that works entirely on socket connections.

UPDATE

set %color $r(1,3)
    if (%color == 1) { set %color red }
    if (%color == 2) { set %color blue }
    if (%color == 3) { set %color green }

could be

set %color $gettok(red|blue|green,$r(1,3),124)

:)

hm, honestly didnt know you could do it like that. learn something new every day.

it would be harder to share though. not that thats an extremely bad thing >_>

A basic socket bot for mIRC

how is it possible that this thing even works? o_o

alias botsend sockwrite -tn bot

should be

alias botsend sockwrite -tn bot $1-

alias bot.join { sockwrite -tn bot JOIN #$$1 }
alias bot.part { sockwrite -tn bot PART #$$1 }

should be

alias bot.join { sockwrite -tn bot JOIN $+(#,$1) }
alias bot.part { sockwrite -tn bot PART $+(#,$1) }

@kenJi If your eggdrop is running on a shell then you should get that information from your shell provider.

I just used /dns shell.host.here

Just used this script for my eggie, works great, even though my lazy ass had to dns my shell's host to get the right IP :P but, works without a flaw so far and even looks better than normal telnet or dcc chat sessions :D

usually not a good habit to use multiple text (or any) events on the same script, they can clash :)

on *:TEXT:*:#:{ 
if ($1 == !warn) { 
if ($2 == on) { ... }
elseif ($2 == off) { ... }
} 
else { ... }
}

true, its not a common way to do it, but /who is not a commonly used command to begin with, at least not that Ive seen. The information from a /who command is easier to handle than /whois, if someone has issues with the script I will gladly change it to work for everyone, but for now I think I will stick to the wise words of "If it ain't broke, don't fix it" :)

@WorldDMT Thanks Ill add that with the next update

@Jethro_ /who $nick works fine on the networks I use