| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8
Comments:
<0> put the nicks in a variable
<1> then if ($istok($opnick,%nickslist,32))
<2> can u set a variable to = more than 1 thing ?
<3> yes, the $istok seperates the names by spaces (I believe)
<3> ?
<3> you got it working ChanBot?
<2> on +1:OP:#:{ mode $chan -oo $opnick $nick | ruser $address( $+ $nick $+ ,6) | notice $nick [Channel protection] You are not permitted to use the op command. } }
<2> why does this not work
<3> Well
<3> I was thinking on *:OP:#:{ if ($istok($opnick,%nickslist,32)) { mode -o $opnick | notice $opnick [Chan prot] Not auth } }
<3> or +1 access
<2> thats good, but i want it by host not nick cuz ppl can change their nick
<3> Well I must go. I wish you luck
<4> yo salut
<3> hello
<5> tomalak well GF stands for good food
<6> GF stands for Girlfriend
<5> those are synonyms.
<3> I thought it stood for german Fantasies
<5> not unless your girlfriend is german
<3> well... ;)
<7> hey is anyone here
<4> salut
<7> hey, i have a question
<4> shoot
<7> i just registered my version of mirc, but i dont know where to put the serial #
<8> the email tells you
<4> regsted bever done that
<4> never
<4> waiy 30 day reload
<4> wait
<4> lolo
<4> ljk
<6> heh.
<6> lmao
<6> i just put up with the nag screen *shrug*
<5> just like we put up with you
<6> yep.
<6> well, you could ban me like that other channel did *shrug*
<2> QUESTION !
<2> what is the difference between HALT and RETURN ?
<6> *shrug* /help return doesn't have any matches.
<0> /help /return
<1> ChanBot: /return is useful for immediately coming out of an alias by returning a blank value. This may or may not work for events too... try it.
<1> /halt is useful for literally breaking out of the execution of a code block. A big difference is that, if used in an event, it'll stop other code blocks for the same event firing as well.
<1> But note that /return would usually be used in the definition of an identifier alias to return a value. e.g. alias double { /return $calc($1*2) } ---> $double(4) = 8
<5> too bad that code is broken
<1> it was a loose example
<1> what's wrong with it anyway
<5> youre a loose ex..wait
<5> //tokenize 32 4 | echo -a $calc($1*2)
<1> bet you weren't expecting $1*2 to parse
<1> I just ran that myself and it was fine
<5> i bet you WERE
<2> so tomalak is it useful to place | halt } } at the end of each On something event?
<5> well it doesnt, tom
<1> Oh yea, I was expecting 8 wasn't I
<1> well like I said loose example and stfu :(
<1> :'(
<5> har.
<1> ChanBot: not really..
<1> use it if you need it
<5> wait
<5> ChanBot a) dont edit code if you dont know what it does
<5> b) on ^ events arent the same
<9> TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL TROLL
<5> tell me about i
<5> t
<1> ^ is related to /haltdef, not /halt, IIRC
<2> LOL!
<5> theyre both the same
<5> actually
<1> not quite
<5> halt will haltdef and then end the script
<1> but yea ok
<2> on 13:TEXT:addautovoice*:?:{ guser 10 $2 3 | msg $nick User $+ $2 $+ added to autovoice list. | halt } }
<1> I would have used them both for different purposes
<2> so halt is not needed?
<5> nope
<1> if attempting to halt default text then ^ + /haltdef
<5> again, dont edit code if you dont know what it does
<1> if attempting to stop other blocks executing, /halt
<2> i do know what it does ...
<8> know_me now knows glime
<2> thats why i scripted it...
<5> that code also has a bracket mismatch
<1> ChanBot: you are asking /us/ if you need /halt in your script. which is ridiculous.
<10> i cant resolve google
<1> only you can know
<1> slicknick! try www.google.com
<5> ..
<2> bracket mismatch ?
<5> yes
<2> what is that
<1> you have one { and two }
<0> heh
<1> for some reason
<5> it means theres a mismatch of brackets.. a bracket mismatch
<2> ok
<2> on @*:KICK:#:{ if (%sop $+ $nick == yes) || ($knick isreg $chan) || ($knick isvoice $chan) { halt } }
<2> else { mode $chan -o $nick | ruser $address( $+ $nick $+ ,6) | notice $nick [Channel protection] You are not permitted to kick a channel operator. } }
<2> well like on this, only works with two } }
<1> that's because in that example, two { are open by the time the script gets to /halt
<1> you don't really know what you're doing, do you?
<2> ahhhh
<2> i get it now
<1> ^^
<1> that's .. amusing.
<2> no, that's why i joined here and asked....
<1> actually you need one } there
<1> because you only want to close the IF statement
<1> not the whole event. it'll only work right with one } after /halt in either example
<2> k
<2> or no /halt at all :)
<1> try counting brackets
<2> ok
<1> in that example I'd use /return ..
<2> Why?
<1> because you only want it to act as a 'do nothing in this event in this case'
<1> /halt has further connotations
<2> how so
<1> well it'll attempt to stop any further on KICK events firing
<1> like I said
<2> ok
<2> ;)
<1> it's just not semantically the command appropriate for the situation
<2> AKA always use /return
<1> you'd be better off rewriting your if statement to get the code in the first clause rather than an else
<1> no, not always... it depends what you're doing!
<1> duh
<2> if i just want it to do nothing
<2> then use return
<2> :)
<1> that's how I do it yes
<2> halt also works for that tho
<1> BUT if you find yourself in that situation then you're probably not writing very good code
<1> (Tue-2:52:38) (tomalak) well it'll attempt to stop any further on KICK events firing
<1> don't use /halt.
<2> k.
<2> thats my only on kick thing tho
<1> on @*:KICK:#:{ if ((%sop [ $+ [ $nick ] ] != yes) && ($knick isop $chan)) { mode $chan -o $nick | ruser $address($nick,6) | notice $nick [Channel protection] You are not permitted to kick a channel operator. } }
<1> this is how to do what you're doing
<1> there are a few changes, a few are neatness things, a few are semantic things and i fixed a bug with your %sop$nick thing
<1> you didn't want "value of %sop"+"value of $nick", you wanted "value of %sop$nick" i'm guessing... you do that as indicated above
<1> .. doesn't matter if it's your only on KICK event or not. point is you don't want your script to stop other events firing. that's not the point of it. so /halt is the wrong thing to use.
<1> whether or not it makes any practical difference in this specific case as things are atm is irrelevant
<1> think like a programmer not an engineer:)
Return to
#mirc
or
Go to some related
logs:
#gamedev
#politics
microdick porn
cannot be cast to type pg_catalog.timestamp
#winxp
#politics
nick beckham- texas
xp assosication
#beginner
#nhl
|
|