mIRC Home    About    Download    Register    News    Help

Print Thread
raw KILL:*:{ #157363 24/08/06 05:50 PM
Joined: Feb 2006
Posts: 164
V
vexed Offline OP
Vogon poet
OP Offline
Vogon poet
V
Joined: Feb 2006
Posts: 164
raw KILL:*:{ or raw KILLED:*:{ doesn't work on IRCX servers
Yet raw PROP:*:{ and raw KNOCK:*:{ work.

Re: raw KILL:*:{ #157364 24/08/06 06:27 PM
Joined: Jul 2004
Posts: 15
H
HumbleSage Offline
Pikka bird
Offline
Pikka bird
H
Joined: Jul 2004
Posts: 15
I have verified this problem on 2 different IRCx networks.

It seems that mIRC is not recognizing the raw non-numeric event for KILL on these servers. You can see mIRC receive it by looking in a debug window but it won't parse in scripts.

I tested the 3 following techniques:

raw *:*:{}
raw KILL:*:{}
raw KILL*:*:{}

The on DISCONNECT event does still trigger but, it does not return suffcient information to identify a KILL.


- HumbleSage
"i don't know what this randomizer is thinking" - LEET
Re: raw KILL:*:{ #157365 26/08/06 01:27 PM
Joined: Jan 2006
Posts: 10
N
nfield38 Offline
Pikka bird
Offline
Pikka bird
N
Joined: Jan 2006
Posts: 10
I can confirm that this is a bug on UnrealIRCd and IthildinIRCd.

Re: raw KILL:*:{ #157366 30/08/06 09:17 AM
Joined: Nov 2003
Posts: 50
X
x64 Offline
Babel fish
Offline
Babel fish
X
Joined: Nov 2003
Posts: 50
No.. you can't confirm that this is a bug with UnrealIRCd, because Unrealircd isn't an IRCXd and doesn't send KILLED messages, and it only sends KILL messages to the person being killed.

Re: raw KILL:*:{ #157367 30/08/06 12:08 PM
Joined: Jan 2006
Posts: 10
N
nfield38 Offline
Pikka bird
Offline
Pikka bird
N
Joined: Jan 2006
Posts: 10
I can confirm that the raw KILL event does not work properly, which is exactly why your IRCd is not working properly with it either.

Quote:
raw *:*:{}
raw KILL:*:{}
raw KILL*:*:{}

Re: raw KILL:*:{ #157368 30/08/06 12:34 PM
Joined: Dec 2004
Posts: 87
I
ik000ike Offline
Babel fish
Offline
Babel fish
I
Joined: Dec 2004
Posts: 87
add this in status window

-
Events on:/event add channel | /event add member | /event add server | /event add socket | /event add connect | /event add user
Events off:/event delete channel | /event delete member | /event delete server | /event delete socket | /event delete connect | /event delete user
-

allthough only ircop's can see those ( server ) messages

Last edited by ik000ike; 30/08/06 12:35 PM.
Re: raw KILL:*:{ #157369 30/08/06 12:56 PM
Joined: Feb 2006
Posts: 164
V
vexed Offline OP
Vogon poet
OP Offline
Vogon poet
V
Joined: Feb 2006
Posts: 164
IRCX shows everyone on the server who has been killed in the status window, even normal users. It's not a matter of changing anything.
If PROP and KNOCK can be parsed, so should KILL.

Re: raw KILL:*:{ #157370 30/08/06 01:04 PM
Joined: Dec 2002
Posts: 4,998
Khaled Offline
Hoopy frood
Offline
Hoopy frood
Joined: Dec 2002
Posts: 4,998
This is in fact by design, mIRC does not trigger a KILL event when you are killed. Also, in some cases mIRC will not attempt a reconnection after a kill, depending on the type of kill.

Re: raw KILL:*:{ #157371 30/08/06 02:27 PM
Joined: Feb 2006
Posts: 164
V
vexed Offline OP
Vogon poet
OP Offline
Vogon poet
V
Joined: Feb 2006
Posts: 164
But why does raw PROP and raw KNOCK show the same status in debug as raw KILL?
On IRCX anyone who is killed will show in the status window of all users, I don't mean just the user who is killed.

Re: raw KILL:*:{ #157372 30/08/06 02:36 PM
Joined: Feb 2006
Posts: 164
V
vexed Offline OP
Vogon poet
OP Offline
Vogon poet
V
Joined: Feb 2006
Posts: 164
<- :user1!x@86.131.XXX.XXX PROP #teen_ops OWNERKEY :arse
Prop looks exactly the same as KILL

<- :sadf!techacct@electrickz KILL user1 :test <- in debug of the user who was killed

<- :sadf!techacct@electrickz KILL user1 :test <- in the debug of all the other people on the server.


* user1 killed by sadf (test) <- in the status window of all users on the server

I don't see why this can't be implemented in, i've scripted everything else, and when someone on the server gets killed it looks out of place, i'm not being selfish, It just seems as though it should be able to be parsed. Alot of others agree. frown

I do see what you mean now, kind of a throttle.
How about a compromise, allow it to be parsed to change colours and what not, but not being able to add code to reconnect or something?

Last edited by vexed; 30/08/06 03:14 PM.