RoboCop and Kick
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

RoboCop and Kick

Started by Vmon, 09 July, 2006, 19:28:19

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Vmon

When right-clicking on a user with the intent to kick, I choose "kick user(s)" but am getting the following message:

[14:21] <RoboCop> *** Inbuild client kick is disabled, use !kick instead!

How do I enable this option?  I would rather use this one than going through the Robo defined options (easier to get to).

Thanks for your help!

I am running PtokaX 0.3.5.0 with Lua 5.02 and Robocop 10.021 script.  No other scripts are installed.

Rincewind

Use Profile Manger in PX to enable the inbuilt kick for the profiles you need it for

Vmon

These were already set up that way.  I am stumped!! ???

Tw?sT?d-d?v

in robo 10.21 opti disabled the inbuilt kick command
Unsure y he did this .. but must have had good reason for doing so

UwV

#4
client inbuild $kick has two "bad" things about it ..

1. there is no reason send witht the $kick to be added to the banlist.
2. there is no escaping the inbuild profile protection in ptokax.. (unless that changed now)
    so e.g.  a Moderator(id 4) would not be able to kick a OP(id 1)    but,..   a OP would be able to kick a Moderator. 1

that might just have something to do with it ..
\NL   The knowledge and skills you have achieved are meant to be forgotten so you can float comfortably in emptiness, without obstruction.
" Holly loves me,...  . "      ;o)

& don't forget, the motto is :
  -- SUPPORT YOUR LOCAL DJ'S --

Vmon

Thanks for the information.  Maybe this is being worked on.

UwV

#6
Quote from: Mutor on 10 July, 2006, 23:58:50


1 - What does a kick have to do with a ban?
2 - Such 'protections' may be scripted

a kicked user is timebanned with the default tepmbantime from ptokax GUI if i am not mistaking..
     and will not have a reason specified in the ptokax (temp)banlist.
2. i guess he will when he has time for it.

my personal conclusion
me i have disabled $kick  in my hub  ..  since i think  a reason to be non optional.
the message send to the kicked user by the clients is very good but does not register a reason in hubsoft.
and a "homebrew" usercommand using  $kick can send with no "reason message" no problem. (most clients have a kcik and reason as popupbox, just leave it empty)
so because "  becuase : " is not a reason ..
i hope you allow me to have it disabled now ..  ;0)

------------------------------------------
as far as opitmus and  robocop i don;t know why.

i was just trying help think why ..
\NL   The knowledge and skills you have achieved are meant to be forgotten so you can float comfortably in emptiness, without obstruction.
" Holly loves me,...  . "      ;o)

& don't forget, the motto is :
  -- SUPPORT YOUR LOCAL DJ'S --

UwV

#7
Quote from: UwV on 11 July, 2006, 01:39:07
2. i guess he will when he has time for it
was refering to optimus and scripting the $kick to be protected according to robocop profiles..

if that is why he has forced disabled it..  again i was just guessing for a reason ..

and the last but not least i fully agree we should all be free to choose.
\NL   The knowledge and skills you have achieved are meant to be forgotten so you can float comfortably in emptiness, without obstruction.
" Holly loves me,...  . "      ;o)

& don't forget, the motto is :
  -- SUPPORT YOUR LOCAL DJ'S --

PPK

Quote from: UwV on 11 July, 2006, 00:15:46
and will not have a reason specified in the ptokax (temp)banlist.
Only with versions before 0.3.4.0  ::)
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

UwV

#9
Quote from: PPK on 11 July, 2006, 09:00:52
Only with versions before 0.3.4.0 ::)

nice one,
but what would the reason would be ? "  kicked by "kickernick". "

if i am specific about it..
yes, there is reason why he is temp/time banned.
but not "why" this user was kicked.
(i understand it would be hard to capture the optional pm message to the kicked user and sub the reason so i don't expect ptokax to do so)

scripting the $kick to protect profiles (like mutor mentioned, and needed if a profile ID is higher in number and  higher in "status" then another)
seems a very good solution if you are not so specific about reasons.
\NL   The knowledge and skills you have achieved are meant to be forgotten so you can float comfortably in emptiness, without obstruction.
" Holly loves me,...  . "      ;o)

& don't forget, the motto is :
  -- SUPPORT YOUR LOCAL DJ'S --

PPK

#10
Get reason from kick message is easy, is same as PtokaX is able to filter kick messages from chat then in same way is able to get reason from this message and after when receive $Kick to use it for ban item ;D

Quote[12:36:40] <PPK> is kicking PePeK because: test...
[12:36:40] <_@o'> *** PePeK with IP 127.0.0.1 was kicked by PPK
[12:36:43] <_@o'> Sorry you have temp ban with remaining time: 59 min 57 sec
IP: 127.0.0.1
Nick: PePeK
Reason: test...
Banned by: PPK
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

UwV

#11
 :D

that really looks great :0)
i didn't know ptokax did that ..

i should test things more regulary on new releases of hubsoft before to open my BIG mouth.

remains only one 'reason' for me to block it ..
the message to user or "is kicking" message to the hub is optional
the $kick arrival will kick a user if the messages are send or not.
not filling in any reason ( no "test" )  would not give us any 'reason' for the action taken.

and then again ...
as reason one could alway's say  : " !kick Nick no reason"
and our Nick  is still kicked without any  "reason" ..

i think i will re-enable it in my hub now i that i see  PX does take reason from message after kick.




\NL   The knowledge and skills you have achieved are meant to be forgotten so you can float comfortably in emptiness, without obstruction.
" Holly loves me,...  . "      ;o)

& don't forget, the motto is :
  -- SUPPORT YOUR LOCAL DJ'S --

SMF spam blocked by CleanTalk