bind for +o flag

Yoda · Post by **Yoda** » Sun May 25, 2003 5:43 am

I want that some binds could be used only by ops, so I added these users to bot user list with .+user nick and give them +o with .chattr nick +o

setted tcl with

bind <type> o <command> <procedure>

but this dont works with these users, instead they are recognized as global op in the bot.

what i'm doing wrong?

(note: I have .13 eggdrop)

Post by **user** » Sun May 25, 2003 7:56 am

.chattr handle +o <-global o
bind <type> o <mask> <cmd> <-global o

If you don't want them to be global +o you better provide a channel name to the chattr and bind the thing to o|o or -|o

Yoda · Post by **Yoda** » Sun May 25, 2003 8:01 am

this is what I did but dont works, the bind command is not executed

Post by **user** » Sun May 25, 2003 8:03 am

Yoda wrote:this is what I did but dont works, the bind command is not executed

Might be some other bind matching the same mask that halts further processing...is your bind stackable?

Check .binds <your type> all

Yoda · Post by **Yoda** » Sun May 25, 2003 8:23 am

no, because without o flag ( but - ) it works

ppslim · Post by **ppslim** » Sun May 25, 2003 9:57 am

Check your hosts for each user.

Unless the hostmasks match, eggdrop has no way of telling which user record to do the flag matching against.

Yoda · Post by **Yoda** » Sun May 25, 2003 10:07 am

this is a problem because are a lot of ops and they change provider too so the only way will be an hostmask like *!*@* for all, but: will it resolve the problem?

spock · Post by **spock** » Sun May 25, 2003 10:10 am

it would create a bunch of other problems

Yoda · Post by **Yoda** » Sun May 25, 2003 10:16 am

ok, better if I'll create a filter on server, more fast and secure

thanks all for help