egghelp/eggheads community

halfop unbinding, part 2

2002-11-15T22:12:30-04:00

bind dcc ol|ol "say" dcc:hosay

so just that then, kewl

Statistics: Posted by Weirdo — Fri Nov 15, 2002 10:12 pm

halfop unbinding, part 2

2002-11-15T16:54:31-04:00

Yes this will work.

However, try not to use * in your own procedure names.

The * is used in eggdrop, to signify a builtin command, however, I do not know how this came about.

If you use * in your scripts, it could come to confuse you later on

Statistics: Posted by ppslim — Fri Nov 15, 2002 4:54 pm

halfop unbinding, part 2

2002-11-15T13:48:38-04:00

perfect

before i just go ahead with this. The proc is called dcc:hosay, so doing this will look like the code below?

unbind dcc o|o "say" *dcc:say
bind dcc ol|ol "say" *dcc:hosay

Statistics: Posted by Weirdo — Fri Nov 15, 2002 1:48 pm

halfop unbinding, part 2

2002-11-15T12:53:58-04:00

Yes, this is possible.

Simply unbind the command, like you can do with all commands.

THen create a script, as if the command was never there in the first place.

Statistics: Posted by ppslim — Fri Nov 15, 2002 12:53 pm

halfop unbinding, part 2

2002-11-15T12:18:56-04:00

Hmmm, and since it is a windrop that i do my scripting on, this becomes impossible without a C compiler. Modules are all Dlls

Damn.

Is it possible i could unbind the .say command from the module, and then bind the .say command to a script using the eggdrop.conf unbinding thingy. As its possible to rename commands, "ident" to "logon", isnt it therefor possible to reallocate the commands unbinded to different procedures.

I think it should be ok to script a replacement .say and .act thing. As long as i can find the variable that gives the channel the console is set to.

Statistics: Posted by Weirdo — Fri Nov 15, 2002 12:18 pm

halfop unbinding, part 2

2002-11-15T10:02:21-04:00

Internal commands, are built using Tcl, and called in a Tcl wrapping function (confuzzled yet).

So when a bind is triggered, eggdrop will search it's bind lists, call any internal functions, then call any Tcl scripts, depending on the type of bind.

Just like a Tcl procedure, that is called by an event triggered bind, the same applies to the C functions.

To use Tcl as an example (it's quicker, and you will understand it more).

Code:

bind pub - "!test" testproc test {nick uh hand chan arg} {  if {![matchattr $hand o|o $chan]} {    puthelp "PRIVMSG $nick :You don't have operator access"    return  }  Triiger code}

Instead of doing the flga checking in the bind, the script is doing it. It allow a certain flexibility, and is job dependant. In simple scripts, keep to using flags in binds.

Like in my example, the C functions will check the users flags, before allowing him access to the commands.

So even though the user has half-op flags, and the bind allows him to trigger it (simalar to the fact, the bind in the example, allows any1 to trigger it), a check inside the function is stopping him.

The simplest way to locate the files with the functions, is to look in the modules related with the task being done (EG: server, irc, channels and possibly core (IE, eggdrop, not a module)), the files are usualy named so that you can see what there contents are (usualy have Tcl in for code that provides command that can be used in script, cmds for functions that provide bind based commands).

Statistics: Posted by ppslim — Fri Nov 15, 2002 10:02 am

halfop unbinding, part 2

2002-11-15T09:08:00-04:00

IE replace the .say command with a different one which links to it in a tcl script. Its possible

where is the internal checking held?

Statistics: Posted by Weirdo — Fri Nov 15, 2002 9:08 am

halfop unbinding, part 2

2002-11-15T06:46:32-04:00

I havn't looked, so don't hold me too it.

A lot of functions in eggdrop, do internal checking, as well as on the binds.

If you havn't got the flags for a bind, you get "you need help", but if there is internal checking, then the function will usualy warn and complain.

You could simply work around this, with small Tcl scripts.

Statistics: Posted by ppslim — Fri Nov 15, 2002 6:46 am

halfop unbinding, part 2

2002-11-14T19:26:30-04:00

Hi

this topic isnt so old, you helped me recently to restrict the ban functions to ops only, so halfops coulnt use them. After doing some more of that, only i came up with some problems

Code:

unbind dcc o|o "say" *dcc:saybind dcc ol|ol "say" *dcc:sayunbind dcc o|o "act" *dcc:actbind dcc ol|ol "act" *dcc:act

I want to let them use the bot chatting facilities. Well, its a female bot... and you get the idea, the channel could use some livening up. Problem is, although i have rebinded them, it still gives the

"You are not a channel op on #cometanime"
"what, you need .help?"

Which means the access dont work, am i doing something wrong?

Also, how i can i remove the .help references for halfops. As they still see the +ban, -ban +invite... ones still. Want to clean this up a little, and completely hide the unnecessary ones from the help file. Maybe add a little .say reference so they can see it

Can you offer any help?

Weirdo

Statistics: Posted by Weirdo — Thu Nov 14, 2002 7:26 pm