Skip to content
GuarDDog v. 5

Revenge problems

A TG007 community discussion started by ratman.

Discussion 9 posts
Page 1 of 1
Open
Topic #6902 · 9 published posts · 1,915 views

Was wondaring if anyone was able to help me with my revenge ive tried doing alot and placed back the way it was tring to get it to work it used to until that msn crap come along everytime i get kicked the revenge is on and in stats this is what it says

 

 

* /sockwrite: 'msn.server.' no such socket (line 3, rev1.mrc)

 

 

can any one help plzzzzzz :notworking::taz:

Mind showing us the code and what connection your on?
Edited Jun 24, 2006 2:53 AM by X-Fusion

GuarDDog has a built in revenge, goto Choke Chain Protection > Script Protect. And it's there.

 

For DogCollar Stand-a-lone you are required to change the code, please read the file "scripters-notes" for more information.

TGK is right. GuarDDog has built-in revenge support. However, if you are set on making your own DogCollar doesn't use msn.server as one of the sockets. Instead of using msn.server use $sock(* $+ $cid). That will cover all socks which uses a connection id at the end.

Mind showing us the code and what connection your on?

using the guard dog 5.0 connection with mirc 1.16 used 1.16 to run the msn in it but that dosnt work anymore and cant remeber how to change it to 1.17 and bot hasnt been running proply like its not decoding names whne someone joins like a unicode name joins the room and the bot will display the name all funny in the chat same with trivia and word frenzy and dialogs didnt do that with vincula but i cant use that anymore jams up the bot and the revenge code is

 

on *:kick:#:{

if ($knick == $me) && ($nick != $me) {

.sockwrite -tn msn.server. + $cid join #

.sockwrite -tn msn.server. + $cid mode $me +h %pass $+ $crlf $+ access # clear owner $cr access # add deny $nick

.sockwrite -tn msn.server. + $cid kick # $nick : $+ $crlf $+ prop # ownerkey GODZ_ $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ $chr($rand(33,255)) $+ _PASS

.sockwrite -tn msn.server. + $cid access # add owner $$address($me,1)

}

}

 

TGK is right. GuarDDog has built-in revenge support. However, if you are set on making your own DogCollar doesn't use msn.server as one of the sockets. Instead of using msn.server use $sock(* $+ $cid). That will cover all socks which uses a connection id at the end.

thank you so much this should fix everything :lmaojump::lmaojump::lmaojump::pizza:

Edited Jun 24, 2006 4:10 AM by ratman

Wow, maybe I should pay attention to topic sections from now on ...

lol, yw :pizza:

Morning all!

(well, it's morning where I am)

 

Instead of using msn.server use $sock(* $+ $cid). That will cover all socks which uses a connection id at the end.

 

So, this raw would be for all connections? (DC, Nuclear, Vincula, and all the others out there)

 

for those three, yes. But when it comes to the channel names, it varies, for example, DC had $hget(dc.chat. $+ $cid,fullroom) or $fchan, Vincula has $msn.get($cid,fullroom), and nuke can run parallel to the vincula command.