mIRC Home    About    Download    Register    News    Help

Print Thread
#43020 19/08/03 08:13 PM
Joined: Aug 2003
Posts: 148
K
KoRn18 Offline OP
Vogon poet
OP Offline
Vogon poet
K
Joined: Aug 2003
Posts: 148
how can i ghost(kill) a user if they switch to my nick?


_________
may death strike you.
#43021 19/08/03 08:37 PM
Joined: Dec 2002
Posts: 339
F
Fjord artisan
Offline
Fjord artisan
F
Joined: Dec 2002
Posts: 339
You might wanna tell us witch network you're on since most networks has diferent services witch means diferent commands too, some others also don't have any services at all..

#43022 19/08/03 09:55 PM
Joined: Dec 2002
Posts: 1,541
L
Hoopy frood
Offline
Hoopy frood
L
Joined: Dec 2002
Posts: 1,541
something like this should do (fill in your servers command):

on !*:nick: {
if ($notify(nickname-service).ison == $true) && ($newnick == nickname1) || ($newnick == nickname2) { /server-specific-kill/ghost-command }

OR

if ($notify(nickname-service).ison == $true) && ($newnick isin %nicknames-I-own) { /server-specific-kill/ghost-command }

}

OR

on *:notify: {
if ($notify(nickname-service).ison == $true) && ($nick != $me) && ($nick == nickname1) || ($nick == nickname2) { /server-specific-kill/ghost-command }

OR

if ($notify(nickname-service).ison == $true) && ($nick != $me) && ($nick isin %nicknames-I-own) { /server-specific-kill/ghost-command }

}


That's a start. I used to have an ON NICK event do just this, but changed it in favor of on notify to keep things simple since if I can see the nickname change, Im gonna see it on notify lsit AND if I see it on notify lsit, it wont matter if I see the actual nbick change. The above examples are simply that, examples but they shoudl give you some ideas smile


Those who fail history are doomed to repeat it
#43023 20/08/03 01:44 AM
Joined: Aug 2003
Posts: 148
K
KoRn18 Offline OP
Vogon poet
OP Offline
Vogon poet
K
Joined: Aug 2003
Posts: 148
im on irc.freenode.net


_________
may death strike you.
#43024 20/08/03 06:34 AM
Joined: Aug 2003
Posts: 136
Vogon poet
Offline
Vogon poet
Joined: Aug 2003
Posts: 136
I know on my network to ghost a nick means that you have been ping timeout and the host just thinks your still on thats easy /msg nickserv ghost nick password
now on the network I am on If some one is on your nick You
/msg nickserv recover nick password
then
/msg nickserv release nick password
that will give yea the nick back but then you can always set protections
/msg nickserv set kill quick
that would give yea 20 seconds to identify if yea dont it changes nick, again this might not work for yea


In Virginia, chickens cannot lay eggs before 8:00 a.m., and must be done before 4:00 p.m.
#43025 20/08/03 08:59 AM
Joined: Mar 2003
Posts: 1,271
L
Hoopy frood
Offline
Hoopy frood
L
Joined: Mar 2003
Posts: 1,271
I suggest going to the helpchannel on your network and asking there.


DALnet #Helpdesk
I hear and I forget. I see and I remember. I do and I understand. -Confucius
#43026 20/08/03 05:11 PM
Joined: Aug 2003
Posts: 148
K
KoRn18 Offline OP
Vogon poet
OP Offline
Vogon poet
K
Joined: Aug 2003
Posts: 148
i know the command, ind i know recover but using ghost is one command, so im using that and i asked and that 20 seconds thing is globally disabled


_________
may death strike you.
#43027 20/08/03 10:38 PM
Joined: May 2003
Posts: 215
Fjord artisan
Offline
Fjord artisan
Joined: May 2003
Posts: 215
I use Freenode as well and this works for me:

Code:
;This is the raw triggered if a nickname is in use.
raw 433:*: {
  ;If the nickname in question matches YourNick, ghost it.
  if ($2 == [color:blue]YourNick[/color]) { nickserv GHOST [color:blue]YourNick YourPassword[/color] }
}
;Add YourNick to the notify list for this part to work.
on *:UNOTIFY: {
  if ($nick == [color:blue]YourNick[/color]) { nick [color:blue]YourNick[/color] }
}
on *:NOTIFY: {
  if ($nick == [color:blue]YourNick[/color]) && ($nick != $me) { nickserv GHOST [color:blue]YourNick YourPassword[/color] }
}


Change the text in blue.

If you do not want mIRC to automatically change to YourNick when the unotify event is triggered, simply remove the event.


- Jason

Link Copied to Clipboard