Another N00b Question From Me

[Guest X-Fusion]

It should work fine. If it still gives you the insufficient parameters error, add else halt to it.

[Daniel_gr]

It should work fine. If it still gives you the insufficient parameters error, add else halt to it.

 

it works fine, when someone else says the trigger,

but when the bot says it it doesnt respond

only difference between the 2 is is that the bot uses a red color.

 

and i changed the * in the if for 'New Shit' (without the ' ) cause there are some other responses on the server that use []

[Guest X-Fusion]

Tools > Options > IRC menu > Messages submenu > Strip codes from bold and color.

 

Just a wild guess.

 

Also, for the server messages that come in, this might work

on *:text:*:*:{
if ($+($chr(91),*,$chr(93),*) iswm $1-) && ($nick == FFBot) { echo @info $1- }
}

[Guest Travis]

You dont see your own text.

[Guest X-Fusion]

Huh?

[Guest Travis]

it works fine, when someone else says the trigger,

but when the bot says it it doesnt respond

 

You dont see your own text.

Edited February 20, 2008 by Travis

[Daniel_gr]

the bot is not me.

if i was the bot. i would have had it echo to the info screen at the same time id send the msg

 

i added your code btw, and tried with the old one: it picks up on texts that look like this : [ blah blah blah]

but somehow it still doesnt pick up on the [New Shit]

 

only difference i see between what it picks up and what it doesnt is the space between [ and the text

Edited February 20, 2008 by Daniel_gr

[hixxy]

you need to use the $chr for [ and ]

 

if ($chr(91) $+ * $+ $chr(93) iswm $1-)

 

 

etc

 

No you don't.

 

//if ([*] iswm [x]) { echo -a WEJKDIKSDJH }

[Ozzy10]

from mirc help file

The [ ] evaluation brackets

 

If you want greater control over the order of evaluation of identifiers, you can use the [ ] brackets. Identifiers within these brackets will be evaluated first, from left to right. You can nest brackets.

 

/say % [ $+ [ $1 ] ]

 

You can also force a previously evaluated identifier to be re-evaluated by using extra [ ] brackets.

 

/set %x %y

 

/set %y Hiya!

 

/echo [ [ %x ] ]

 

this is why you need to use chr codes

 

if ($chr(91) $+ * $+ $chr(93) iswm $1-)

 

or someone could slip in some code into an echo (not in this case)

 

so its good practice to use the $chr when you dont want to use the [ ] evaluation brakets

 

[Guest Travis]

I have found I only need to use the $chr for the opening bracket.

 

menu item $chr(91) * ]:command