egghelp/eggheads community

De Kus

check your config file for my-ip and my-hostname. probably you have any invalid entry.

De Kus

you will have to give your ops access to the bot, to be able to remove his bans

.
but no, you can still give them +o and -p flag

, since the trigger isn't a DCC bind, but justs captures the regular channel mode +b and -b you see in the channel.

De Kus

I posted a script doing such things long time ago.
http://forum.egghelp.org/viewtopic.php? ... banmanager

bans from bot are threaten as master, but you may adjust it easily, knowing a bit tcl ^^.

De Kus

then make a /whois on irc to the user and an .whois on the bot. hope you know how you will give him an hostmark that matchs him always, but most secure ^^. everthing else is just reading the manual :D. seeing the host above means the bot probably set a 1.2.3.* hostmark, but the host of the person ch...

De Kus

don't you like my avatar, or why did you just mantion this on that day I realiezed that I had completly forgotten to enter a signature and an avatar? :D Just kidding. But I think all avatars are ok, since they can't exceed 6kb and 80*80 pixels... it's not like on some other forums, where you can use...

De Kus

]Kami[ wrote:Plus puting static host on auop sux.Many people can fake host

AFAIK +o isn't autoop and a password isn't faked that easily...

I suggest you use '.channel #tbog_yang' and look if he is recognized with a handle.

De Kus

Code: Select all

  foreach user [chanlist $chan] {
    if {[isop $user $chan]} {
      incr op
    } elseif {[isvoice $user $chan]} {
      incr voice
    } else { incr normal }
  }

so it should work ^^

De Kus

The @#dn occurs in case of an op notice (onotice). Just filter the destination of the notice and will work smoothly. I wouldn't like that, since this way they could spam the ops with notices... but... since both scripts don't handle really critical spamming it might be an idea. btw. the [expr ...] ...

De Kus

*grabs backup from temp dir*

Code: Select all

bind notc -|- * handle_lamer_notice

proc handle_lamer_notice {nick uhost hand text chan} {
  if { [validchan $chan] } { handle_lamer $nick $uhost $hand $chan "$text" }
  return 0
}

De Kus

egghead wrote:
Code: Select all
validchan $chan

was a nice idead from me... but did relault to this:

Code: Select all

[19:10] Tcl error [handle_lamer_notice]: illegal channel: @#dn

and I don't know how to strip this @ easier...

PS: other function, same code ^^. played a bit with quakenets lamer.tcl

.

De Kus

*headbang* args, FU, *grmpf* damn elseif... hmm, strange seem he doens't like set overkill [expr [lindex $shortflood 0]+3] because of Tcl error [shortflood]: syntax error in expression "5:2+3": extra tokens at end of expression as egghead mentioned... looks strange, but works in repeat1.1....

De Kus

are you talking about that line?

Code: Select all

if { $shortflooders($uhost:$chan) == [lindex $shortflood 0] } {

thats first I thought, too. I also made a .restart to be sure it has been refreshed. same as without $ ^^.

De Kus

I am having a strange error in a new written script :/ Tcl error [shortflood]: syntax error in expression " shortflooders($uhost:$chan) == $overkill ": missing close parenthesis at end of function call I counted the braces, but couldn't find the misstake. The if-construct as it is is copie...

De Kus

take time, open port 80 or 22 or sth. like this, if port is opend, take time again. diffrence is something like a ping ^^.

De Kus

as said, there must be a script using bind JOIN and forwarding $nick in a putserv/putquick syntax with MODE to server ^^. I can't help you finding it.

egghelp/eggheads community

Search found 1347 matches

hehe

Re: syntax error in expression ... missing close parenthesis

syntax error in expression ... missing close p... [solved]