No 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

No kick?

Started by elgee, 23 May, 2007, 08:57:38

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

elgee

<PutUpOrShutUp> This hub is running PtokaX DC Hub 0.3.6.0 (UpTime: 0 days, 0 hours, 15 minutes)
<PutUpOrShutUp> The following commands are available to you:

Profile specific commands:
   !passwd <new password> - change your password.
   !ban <nick> <reason> - permanently ban user with given nick, followed by disconnect.
   !banip <IP> <reason> - permanently ban IP address.
   !fullban <nick> <reason> - permanently ban user with given nick, followed by disconnect.
   !fullbanip <IP> <reason> - permanently ban IP address.
   !nickban <nick> <reason> - ban user's nick (if user is connected then is disconnected).
   !tempban <nick> <time> <reason> - temporary ban user with given nick, followed by disconnect.
   !tempbanip <IP> <time> <reason> - temporary ban IP address.
   !fulltempban <nick> <time> <reason> - temporary ban user with given nick, followed by disconnect.
   !fulltempbanip <IP> <time> <reason> - temporary ban IP address.
   !nicktempban <nick> <time> <reason> - temp ban user's nick (if user is connected then is disconnected).
   !unban <IP or nick> - unban IP address or nick.
   !permunban <IP or nick> - unban perm banned IP address or nick.
   !tempunban <IP or nick> - unban temp banned IP address or nick.
   !getbans - display list of bans.
   !getpermbans - display list of permanent bans.
   !gettempbans - display list of temporary bans.
   !clrpermbans - clear perm bans.
   !clrtempbans - clear temp bans.
   !rangeban <fromIP> <toIP> <reason> - permanently ban given IP range.
   !fullrangeban <fromIP> <toIP> <reason> - permanently ban given IP range.
   !rangetempban <fromIP> <toIP> <time> <reason> - temporary ban given IP range.
   !fullrangetempban <fromIP> <toIP> <time> <reason> - temporary ban given IP range.
   !rangeunban <fromIP> <toIP> - unban banned IP range.
   !rangepermunban <fromIP> <toIP> - unban permanently banned IP range.
   !rangetempunban <fromIP> <toIP> - unban temporary banned IP range.
   !getrangebans - display list of range bans.
   !getrangepermbans - display list of permanent range bans.
   !getrangetempbans - display list of temporary range bans.
   !clrrangepermbans - clear permanent range bans.
   !clrrangetempbans - clear temporary range bans.
   !checknickban <nick> - display ban found for given nick.
   !checkipban <IP> - display ban(s) found for given IP address.
   !checkrangeban <fromIP> <toIP> - display range ban found for given IP range.
   !drop <nick> <reason> - disconnect with tempban.
   !getinfo <nick> - displays basic info on user with given nick.
   !op <nick> - give a temporal Op status to the user for one session.
   !gag <nick> - disallow user to post in mainchat.
   !ungag <nick> - user can post to mainchat again.
   !restart - restart hub.
   !startscript <filename> - start script with given filename.
   !stopscript <filename> - stop script with given filename.
   !restartscript <filename> - restart script with given filename.
   !restartscripts - restart scripting part of the hub.
   !getscripts - display list of scripts.
   !reloadtxt - reload all textfiles.
   !addreguser <nick> <password> <profilename> - add registered user with specified profile.
   !delreguser <nick> - remove registered user.
   !topic <new topic> - Set new topic. Or !topic <off> - clear topic.
   !massmsg <message> - send private message to all users.
   !opmassmsg <message> - send private message to all OPs.
*** Reason is always optional.
*** Full bans disallow anyone from banned IP to login.
*** Temp ban time values: m = minutes, h = hours, d = days, w = weeks, M = months, Y = years.

Global commands:
   !me <message> - speak in 3rd person.
   !myip - show your IP.




... say what? No kick? ...
No matter what I been trying, I can't kick ...

And I have not tried to use the clients inbuild kick cmd.
What I have done is to typed it in mainchat as !kick Iluminada test
In the GUI i see this: [09:33] <?Regardless?> !kick Iluminada test|

**edit** crap pic but as you see there is kick and it is ticked

PPK

Direct Connect protocol have for kick command $Kick nick|, i don't see any reason to make thing harder and adding kick chat command when kick command is already available on protocol level  ::)
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

elgee

well for me as a user of the hubsoft and other hubsoft, I think that !kick is a basic command that should be there.
But thats my point of view, also it do separate Ptoka from the rest of the softs beeing used, afaik, there is not another hubsoft not supporting
!kick nick ...

And most are OP in hubs of different kinds of soft, Ptoka, Verli, Aquila, Ynhub ... and the rest ..
I can't really see the idea of not supporting it, it makes it harder to OP when you need to separate the users into what hubsoft there loged into, as many is using a) usercommands written by there own b) adl-search with trigger !kick nick ...


UwV

#3
too bad,, a fine feature , wich we had from build 0.0.0 (kind of)  just gone..
as far as i remeber (correct me if i am wrong) the !kick command has always been there.. and it was working good..
i see no reason for it being taken out unless if it was not working or unwanted by the users of the hubsoft (we did not ask you to put it in)..

so if you ask me ? just put it back in even if you do not see a reason i do,
and then.. you removed it without any warning btw ? like no comments in the change log no poll here for the hubowners/scripters ??..   .. maybe if you stop rolling your eyes you would also see the reason why someone is very surpised it is just "gone" ... 

*edited to correct some spelling and ad a small piece
\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

#4
Quote from: elgee on 23 May, 2007, 10:30:26
also it do separate Ptoka from the rest of the softs beeing used
$Kick is STANDARD command in Direct Connect protocol, all Direct Connect compatible hubsofts support it, all Direct Connect compatible clients support it. Here is no separation, simply use on all hubsofts same command, because is supported on all Direct Connect compatible hubs. PtokaX was here before Verli, Aquila, YnHub... they are stupid idea of putting in command what nobody need because is already here. PtokaX have kick command, and here is no reason to add another only because others have it.

Quote from: UwV on 23 May, 2007, 10:42:34
as far as i remeber (correct me if i am wrong) the !kick command has always been there..
No PtokaX version have !kick command :P


If you really need !kick command simply use script for it ;D
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Naithif

Quote from: PPK on 23 May, 2007, 12:34:51
If you really need !kick command simply use script for it ;D

Or:
!tempban <nick> 0 <reason>


You only have to write one extra 0 (for default) and a space compared to kick ;)

elgee

If you really need !kick command simply use script for it

Silly.

bastya_elvtars

Watch your mouth, please.
Everything could have been anything else and it would have just as much meaning.

UwV

#8
Quote from: PPK on 23 May, 2007, 12:34:51
No PtokaX version have !kick command :P

I stand corrected.
i really did think PX used to have it build in ..
(and have been using a script for that command for ages :p )

ps. i am not deleting that post, even if it makes me look stupid.
\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: elgee on 23 May, 2007, 15:37:02
Silly.
Imho is silly that OPs using hubsoft specific command instead of command available on all hubsofts.
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

bastya_elvtars

Quote from: PPK on 23 May, 2007, 22:06:00
Imho is silly that OPs using hubsoft specific command instead of command available on all hubsofts.

$Kick in its current form SUCKS BIGTIME.
Everything could have been anything else and it would have just as much meaning.

PPK

Sucks or not, it is here and working. OP don't need to care how it's working, he is simply use menu command and PtokaX do rest (catch kick message, add it as reason for tempban, filter kick message from chat and not broadcast it to all, maybe send kick message only to OPs).
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

baba.runner

Quote from: elgee on 23 May, 2007, 10:30:26
well for me as a user of the hubsoft and other hubsoft, I think that !kick is a basic command that should be there.
But thats my point of view, also it do separate Ptoka from the rest of the softs beeing used, afaik, there is not another hubsoft not supporting
!kick nick ...

And most are OP in hubs of different kinds of soft, Ptoka, Verli, Aquila, Ynhub ... and the rest ..
I can't really see the idea of not supporting it, it makes it harder to OP when you need to separate the users into what hubsoft there loged into, as many is using a) usercommands written by there own b) adl-search with trigger !kick nick ...



Do you use an all in one script or what scripts do you use?
How did you make your list in your first post here? By tiping which command?

Psycho_Chihuahua

Quote from: baba.runner on 24 May, 2007, 11:49:31
Do you use an all in one script or what scripts do you use?
How did you make your list in your first post here? By tiping which command?

the first post he made contains the output from the default ptokax !help command as far as i see
PtokaxWiki ?PtokaX Mirror + latest Libs

01100001011011000111001101101111001000000110101101101110011011110111011101101110001000000110000101110011001000000101010001101111011010110110111101101100011011110111001101101000

elgee

Yes it was the !help i was posting.
Guess I has not paid attention before to it, but it explains why we had problem kicking before, but as I was in a rush I never looked at it.

baba.runner

Quote from: Psycho_Chihuahua on 24 May, 2007, 12:14:05
the first post he made contains the output from the default ptokax !help command as far as i see

Not necessary
could also be the output of an all-in-one script
and if he has not he kick right in that script, he will not see it.

elgee

"She" has not any scripts running in that hub, only when testing is done :)

SMF spam blocked by CleanTalk