Text only | Text with Images

PtokaX forum

Lua 5.3/5.2/5.1 Scripts (for PtokaX 0.4.0.0 and newer) => DiXBoT => AllInOne Scripts => DiXBoT - Bug Reports => Topic started by: ?ippe?? on 20 May, 2009, 07:49:23

Title: Kick Denied
Post by: ?ippe?? on 20 May, 2009, 07:49:23

Hi Snooze,
              I have restricted operators from kicking, banning users.

              The Command (!kick) is not shown in commands (!help) for operators once disabled from CMD MANAGER.

              But this is allowed from dc++

              In Dc++ -> Rightclick -> kick user

              There is such an option which allows operators to kick users.

              Please do something so that when i disable kick command for operators and higher, the option automatically get disabled.

              OR better remove the options from User Commands, as if i allow operators to "kick" the command will be available in
              DiXBoT Rightclicks -> OP CMD

              Please look into it.
Title: Re: Kick Denied
Post by: CrazyGuy on 20 May, 2009, 13:05:46
There is a difference between a !kick command, and the protocol command $Kick.
The latter hides behind the clients Usercommand "Kick user"
Although operator privilidges are required to use $Kick, there is no further checking on profile permissions by default.
Blocking this is possible by monitoring KickArrival in PtokaX but maybe you should consider which kind of users to give operator status instead.

In many hubs a large number of users get operator status just to get a "key" but this is a wrong way of doing things. Operator status is meant to be for those taking care of the hub and NOT to please keysluts.

Side note: It is not possible to remove or block the visibility of the inbuild "Kick user" Usercommand in clients. This is simply controlled by the user being in $OpList. (i.e. has "key")
Title: Re: Kick Denied
Post by: ?ippe?? on 21 May, 2009, 06:27:25

  Thanks CrazyGuy.
Title: Re: Kick Denied
Post by: PPK on 21 May, 2009, 10:05:15
Quote from: CrazyGuy on 20 May, 2009, 13:05:46
Side note: It is not possible to remove or block the visibility of the inbuild "Kick user" Usercommand in clients. This is simply controlled by the user being in $OpList. (i.e. has "key")
It is possible ;) It is working correctly in original nmdc client, OP menu is controlled by $LogedIn command (yes that means that most clients have bug) ::)
Title: Re: Kick Denied
Post by: ?ippe?? on 21 May, 2009, 11:21:58

  Thanks PPK
Title: Re: Kick Denied
Post by: CrazyGuy on 21 May, 2009, 14:03:45
Quote from: PPK on 21 May, 2009, 10:05:15
It is possible ;) It is working correctly in original nmdc client, OP menu is controlled by $LogedIn command (yes that means that most clients have bug) ::)

Ah, then I learned something as well  8)
I implemented the command in my client the way as I thought it worked, i.e. it shows when user is in $OpList ;)
Text only | Text with Images