Depend on the reply you get: if it contains the nick and an information that the ip is spoofed, you can relaunch a /whois. The danger is that you may flood the server with /whois commands if you don't get the real IP. You should probably add a counter (who($nick)) and stop if you did more than 2 /wh...
Peharps can you try to understand what the code does, read the doc and try to adapt. OR, to say that quicker: learn. bind nick - * checkvoice # name of the called procedure is checkvoice proc checkvoice {nick uhost handle chan newnick} { set onchash [md5 [string tolower "${nick}:${chan}"]]...
You can do that for the @ (but just op, not aop), I'm not sure you can add the sop.
Eggdrop doesn't know these modes, so it can't check if an op is aop nor sop.
What do you mean ? The user doesn't get his voice when he regains his previous nick ? I made a little test (and some little modifications): bind nick - * checkvoice proc checkvoice {nick uhost handle chan newnick} { set onchash [md5 [string tolower "${nick}:${chan}"]] set nnchash [md5 [str...
If your eggdrop is not on the target channel, it's normal. You can choose between 2 options: 1. have your eggdrop on #djsohbet and it'll work without error 2. remove the && [lsearch [chanlist $::ctarget] $nick]==-1 part in the condition and your eggdrop will do the sajoin command even if the...
First, your eggdrop must be ircop to use these feature. Invite seems better, user join if he want. And which criteria do you want to use to make user coming into target channel ? Everybody ? BTW, here is the simplest script: set ctarget "#djsohbet" set cfrom "#dj" proc forcejoin ...
a specific .tcl will only work on that version of eggdrop ¯\_(ツ)_/¯ I'm quite surprized, usually scripts working with 1.6.21 works with 1.8.x and 1.9.x, sometime they require a few adaptation but there is no real incompatibility. Peharps we can help you with the script rather helping you keepin an ...