egghelp/eggheads community

modified partyline access/restrictions

2003-11-15T03:35:17-04:00

Yep! My mistake, I forgot to use .tcl before the command
Anyway it's a relief to know it only works for owners (as I am the only owner).

Statistics: Posted by z_one — Sat Nov 15, 2003 3:35 am

modified partyline access/restrictions

2003-11-14T17:58:32-04:00

you did .info ( see .help info )
the command you stated is a .tcl command
so they need +n to use it, if it is even binded ( its not by default) and depending on your must-be-owner setting they may even need to be perm owner in the conf to use it

Statistics: Posted by gumbydammit — Fri Nov 14, 2003 5:58 pm

modified partyline access/restrictions

2003-11-14T17:03:19-04:00

caesar, I was reviewing all eggdrop commands to see which ones I want to stop (using the code you showed me) and I found out this in the tricks file that ships with Eggdrop:

Tcl has a command 'info body ' that will list the contents of a proc.

Now, if I get this right it means that someone who has access to my bot's partyline can somehow display the code inside a procedure that I wrote and then steal it ?
If yes, how to stop this ?
I tried the command .info body myprocname and to my surprise, it said "your info is now myprocname" ! I must be doing something wrong here or using the wrong command

Statistics: Posted by z_one — Fri Nov 14, 2003 5:03 pm

modified partyline access/restrictions

2003-11-14T16:39:37-04:00

Heh, you'r welcome. Feel free to change anything you want in it.

Statistics: Posted by caesar — Fri Nov 14, 2003 4:39 pm

modified partyline access/restrictions

2003-11-14T16:16:32-04:00

Caesar, done.
Works like charm.

Thanks a million.

Statistics: Posted by z_one — Fri Nov 14, 2003 4:16 pm

modified partyline access/restrictions

2003-11-14T11:50:24-04:00

In the code I've previously posted just add your handle in the allowed variable. Doing this only the handles that are added in the allowd variable can do the dcc commands you've binded.

Statistics: Posted by caesar — Fri Nov 14, 2003 11:50 am

modified partyline access/restrictions

2003-11-14T00:18:30-04:00

unbind dcc lo|lo kick *dcc:kick
bind dcc n|n kick *dcc:kick

Statistics: Posted by gumbydammit — Fri Nov 14, 2003 12:18 am

modified partyline access/restrictions

2003-11-13T16:29:36-04:00

user wrote:

If you want to change the flag(s) required, just create the bind with different flags

So if I bind .kick to the owner flag like that:

Code:

bind filt n|n ".kick *" dcc:allow

It would only allow the owner to use .kick ? Do I have to unbind first then bind it to owners only ?

Thanks for everyone who has helped/is helping in this thread.

Statistics: Posted by z_one — Thu Nov 13, 2003 4:29 pm

modified partyline access/restrictions

2003-11-13T16:08:47-04:00

'unbind' is the way to go if you want to disable a command. If you want to change the flag(s) required, just create the bind with different flags.

Statistics: Posted by user — Thu Nov 13, 2003 4:08 pm

modified partyline access/restrictions

2003-11-13T16:02:03-04:00

caesar, say I want to control the .kick to stop it (just like u can stop the default eggdrop flud actions if you make the proc return 0).

I read the following about FILT

FILT (stackable)
bind filt
procname

Description: party line and file system users have their text sent
through filt before being processed. If the proc returns a blank
string, the text is considered parsed. Otherwise, the bot will use
the text returned from the proc and continue parsing that

So will the following code stop anyone from using .kick. If it doesn't then what would be the code to stop anyone from using a .kick from the partyline?

Code:

bind filt - ".kick *" dcc:allow proc dcc:allow {idx args} {   return ""}

Statistics: Posted by z_one — Thu Nov 13, 2003 4:02 pm

modified partyline access/restrictions

2003-11-11T17:07:42-04:00

Test this:

Code:

# What users (theyr handle) to be allowed to use the commands?set allowed "bla foo bar" bind filt - ".dump *" dcc:allowbind filt - ".kick *" dcc:allowbind filt - ".+ban *" dcc:allowproc dcc:allow {idx args} {   global allowed   set usernick [idx2hand $idx]  if {[lindex $args 1] == ""} {     set icmd [lindex $args 0]    set args "$icmd "  }  if {[lsearch -exact [string tolower $allowed] [string tolower $usernick]] == -1} {    putdcc $idx "What? You need '.help'"    } else {    return $args  }}

Statistics: Posted by caesar — Tue Nov 11, 2003 5:07 pm

modified partyline access/restrictions

2003-11-11T16:56:17-04:00

Unbind the dcc command .op and add a new flag then wrote your own .op script that checks the flag you have added if the user has the flag its op him.

Statistics: Posted by Rusher2K — Tue Nov 11, 2003 4:56 pm

modified partyline access/restrictions

2003-11-11T16:33:59-04:00

Hi,

Is there a way to make someone have access to the partyline but forbid them from using and bot command such as .dump or .kick or .+ban etc...
I just want them to be able to use the .op command only

Thanks

Statistics: Posted by z_one — Tue Nov 11, 2003 4:33 pm