Jump to content

tidy trax

Members
  • Posts

    49
  • Joined

  • Last visited

Posts posted by tidy trax

  1. //set %varname string

    if you're using an editbox like in the status window you'd need two forward slashes (//)

     

    You only need one / unless you want the things you're adding to the variable to evaluate an extra time, for example:

     

    * Set %x to $time

     

    * Set %x to 04:24:40

     

    See the difference?

  2. I'd actually go for the /filter method:

     

    alias loadsongs {
     if ($isfile(mp3s.txt)) filter -fk mp3s.txt addtodialog
    }
    alias addtodialog did -a mp3 1 $replace($duration($calc($mp3($1-).length /1000)),mins,m,secs,s,min,m,sec,s) $chr(9) $gettok($nopath(%i),-1,46)
    

  3. Currently, a state-of-the-art laptop would be around £2000 for 3Ghz with 1GB RAM and a 100GB harddrive.

    I don't know how much 500MB ram and 20GB disk space would affect the cost, but the one I'm getting for £800 has a 3Ghz processor, decent (not the best, but decent) graphics card, 500MB ram and 80GB disk space.

  4. Simple way to test would be to add someone to your notify list then run /debug @raw in your mIRC then check to see what raws are working when ppl on your list join the server.

     

    My above example is directly from my crappy theme and works great on cusa.

     

    Dunno, try and try again lol

    You're both right. mIRC waits for the raw 005 numeric (usually this numeric tells you what the server supports) before determining how to make the notify list work, if mIRC is told the server supports the WATCH command it will use that, then the server will automatically tell you when someone gets online.

    Otherwise, mIRC will send the ISON command on a timer.

  5. Both of your points are totally flawed.

     

    1) mIRC and your bot (or any other client, for that matter) will flood out the same if you send too much data in such a little time. It makes no difference what you use to connect.

     

    2) mIRC has to parse a script every time data comes through the socket rather than just doing whatever it wants to do. There's no question that your socket bot is going to be slower.

  6. I found out that code doesn't work.

    It worked for me.

    Your method isn't a very good one because they can just open up the script in notepad and see the password.

    I know you could just remove that part of the script altogether but many people don't know how to edit scripts.

  7. Updated again:

     

    /*
    
    What does /monitorfile do?
    
    /monitorfile will watch a file and tell you when the file is modified or deleted, it will send a 'monitorfile' signal with either 
    'FILE_DELETE' or 'FILE_CHANGE' as the first parameter followed by the file that was being watched.
    If you don't use a . with the /monitorfile command (/.monitorfile) then you will also see some information in the active window when files
    are changed or deleted.
    All error/information messages should replicate mIRCs own messages.
    /monitorfile uses a 5 second interval to check for changes in files.
    
    How do I use /monitorfile?
    
    The syntax is: /monitorfile [-l|-s] <file>
    If you specify -l then the files matching the wildcard string in <file> will be listed.
    If you specify -s then the files matching the wildcard string in <file> will stop being monitored.
    Otherwise, the specified file will start being monitored.
    
    How do I use $monitorfile?
    
    The syntax is: $monitorfile(<file>,<N>)
    This identifier will return the Nth monitored file matching the wildcard string in <file>, if you specify 0 as <N> then the amount of
    matching files will be returned.
    
    How does /monitorfile work? (For scripters)
    
    /monitorfile will store the crc value of a file when you start monitoring a file and check the current crc value against the stored one 
    every 5 seconds.
    If the value doesn't match then the FILE_CHANGE signal will be sent and the new crc value will be stored.
    If the file no longer exists when /monitorfile goes to check the current crc value then the FIlE_DELETE signal will be sent and the timer
    will be stopped. 
    
    Can you give me an example of using this?
    
    on *:start:{ .monitorfile $mircini }
    on *:signal:monitorfile:{
     if ($1 == FILE_CHANGE) && ($2- == $mircini) { echo $color(info) -afilr Hi $+($me,!) mIRC will just revert all changes to mirc.ini so $&
       there's no point in changing it unless you used the options dialog. :) }
    }
    
    How can I contact you?
    
    You can email me at [email protected] or [email protected]
    You can also find me in #mIRC or #mirc.net on IRC at irc.undernet.org but I am not always there.
    
    Have you made any changes to this snippet since it was first made?
    
    v2:
    Added -s and -l switches.
    
    v3:
    Fixed -s not stopping all matching files from being monitored.
    Fixed hfree bug when table didn't exist.
    Now uses '<' to replace spaces instead of '\s'
    
    */
    
    alias checkfile {
     if (!$isfile($1-)) {
       .signal -n monitorfile FILE_DELETE $1-
       if ($hget(monitorfile)) {
         hdel monitorfile $replace($1-,$chr(32),<)
         if (!$hget(monitorfile,0).item) { hfree monitorfile }
       }
       $+(.timermonitorfile,$replace($1-,$chr(32),<)) off
       if (!$line($active,0)) { linesep -a }
       echo $color(info) -afilqr * /monitorfile: No longer monitoring $+(',$1-') for changes (File was deleted).
       linesep -a
       return
     }
     if ($crc($1-) != $hget(monitorfile,$replace($1-,$chr(32),<))) {
       hadd -m monitorfile $replace($1-,$chr(32),<) $v1
       .signal -n monitorfile FILE_CHANGE $1-
       if (!$line($active,0)) { linesep -a }
       echo $color(info) -afilqr * /monitorfile: File $+(',$1-') has changed. 
       linesep -a
     }
    }
    alias monitorfile {
     if (!$isid) {
       if ($istok(-l -s,$1,32)) {
         if ($hget(monitorfile)) {
           var %i = 1
           tokenize 32 $1 $replace($2,$chr(32),<)
           if ($1 == -s) {
             while ($hfind(monitorfile,$2,1,w)) {
               echo $color(info) -afilqr * /monitorfile: No longer monitoring $+(',$replace($hfind(monitorfile,$2,1,w),<,$chr(32)),') $&
                 for changes (Stopped by user).
               linesep -a
               $+(.timermonitorfile,$hfind(monitorfile,$2,1,w)) off
               hdel monitorfile $hfind(monitorfile,$2,1,w)
             }
           }
           else {
             if ($2 == $null) { tokenize 32 -l * }
             if (!$line($active,0)) { linesep -a }
             echo $color(info) -afilr * Monitoring files:
             var %i = 1 
             while ($hfind(monitorfile,$2,%i,w)) {
               echo $color(info2) -afilr $hfind(monitorfile,$2,%i,w)
               inc %i
             }
           }
           if (!$hget(monitorfile,0).item) { hfree monitorfile }
           linesep -a
         }
         return
       }
       if (!$isfile($1-)) {
         if (!$line($active,0)) { linesep -a }
         echo $color(info) -abfilr * /monitorfile: No such file $+(',$1-')
         linesep -a
         return
       }
       hadd -m monitorfile $replace($1-,$chr(32),<) $crc($1-)
       $+(.timermonitorfile,$replace($1-,$chr(32),<)) 0 5 $+($iif(!$show,.),checkfile) $1-
       if (!$line($active,0)) { linesep -a }
       echo $color(info) -afilqr * /monitorfile: Now monitoring $+(',$1-') for changes. 
       linesep -a
     }
     else { return $hfind(monitorfile,$1,$iif($2 != $null,$v1,1),w) }
    }

  8. on *:start:{
    if ($md5($input(Enter password:, dip, Password request)) == <password in md5 format>) { server blah blah }
    else { exit }
    } 
    
    
    
    Type //echo -a $md5(<password you want to use>) to get the md5 hash of the password, then you can change <password in md5 format> to that hash. 
    

     

    each time mirc quit notworking.gif

    You're only supposed to put the part inside the code tags in remote and you have to change the "<password in md5 format>" part like I said in the last post.

  9. hello ,

     

    i am making a mirc script called CyberResearch ,, but i wanne make a password dialog that ask a password when you start mirc,, en if you enter a wrong password then quit mirc. en when you enter the correct password then mirc connect to a server

     

    i have no idea to make this can somebody help me  ...?

     

     

    Buy Odysseus w0ot.gif

    on *:start:{
     if ($md5($input(Enter password:, dip, Password request)) == <password in md5 format>) { server blah blah }
     else { exit }
    }

     

    Type //echo -a $md5(<password you want to use>) to get the md5 hash of the password, then you can change <password in md5 format> to that hash.

  10. Updated:

     

    /*
    
    What does /monitorfile do?
    
    /monitorfile will watch a file and tell you when the file is modified or deleted, it will send a 'monitorfile' signal with either 
    'FILE_DELETE' or 'FILE_CHANGE' as the first parameter followed by the file that was being watched.
    If you don't use a . with the /monitorfile command (/.monitorfile) then you will also see some information in the active window when files
    are changed or deleted.
    All error/information messages should replicate mIRCs own messages.
    /monitorfile uses a 5 second interval to check for changes in files.
    
    How do I use /monitorfile?
    
    The syntax is: /monitorfile [-l|-s] <file>
    If you specify -l then the files matching the wildcard string in <file> will be listed.
    If you specify -s then the files matching the wildcard string in <file> will stop being monitored.
    Otherwise, the specified file will start being monitored.
    
    How do I use $monitorfile?
    
    The syntax is: $monitorfile(<file>,<N>)
    This identifier will return the Nth monitored file matching the wildcard string in <file>, if you specify 0 as <N> then the amount of
    matching files will be returned.
    
    How does /monitorfile work? (For scripters)
    
    /monitorfile will store the crc value of a file when you start monitoring a file and check the current crc value against the stored one 
    every 5 seconds.
    If the value doesn't match then the FILE_CHANGE signal will be sent and the new crc value will be stored.
    If the file no longer exists when /monitorfile goes to check the current crc value then the FIlE_DELETE signal will be sent and the timer
    will be stopped. 
    
    Can you give me an example of using this?
    
    on *:start:{ .monitorfile $mircini }
    on *:signal:monitorfile:{
     if ($1 == FILE_CHANGE) && ($2- == $mircini) { echo $color(info) -afilr Hi $+($me,!) mIRC will just revert all changes to mirc.ini so $&
       there's no point in changing it unless you used the options dialog. :) }
    }
    
    How can I contact you?
    
    You can email me at [email protected] or [email protected]
    You can also find me in #mIRC or #mirc.net on IRC at irc.undernet.org but I am not always there.
    
    */
    
    alias checkfile {
     if (!$isfile($1-)) {
       .signal -n monitorfile FILE_DELETE $1-
       hdel monitorfile $replace($1-,$chr(32),\s)
       if (!$hget(monitorfile,0).item) { hfree monitorfile }
       $+(.timermonitorfile,$replace($1-,$chr(32),\s)) off
       if (!$line($active,0)) { linesep -a }
       echo $color(info) -afilqr * /monitorfile: No longer monitoring $+(',$1-') for changes (File was deleted).
       linesep -a
       return
     }
     if ($crc($1-) != $hget(monitorfile,$replace($1-,$chr(32),\s))) {
       hadd -m monitorfile $replace($1-,$chr(32),\s) $v1
       .signal -n monitorfile FILE_CHANGE $1-
       if (!$line($active,0)) { linesep -a }
       echo $color(info) -afilqr * /monitorfile: File $+(',$1-') has changed. 
       linesep -a
     }
    }
    alias monitorfile {
     if (!$isid) {
       if ($istok(-l -s,$1,32)) {
         var %i = 1
         if ($1 == -l) {  
           if ($2 == $null) { tokenize 32 -l * }
           if (!$line($active,0)) { linesep -a }
           echo $color(info) -afilr * Monitoring files:
         }
         tokenize 32 $1 $replace($2,$chr(32),\s)
         while ($hfind(monitorfile,$2,%i,w)) {
           if ($1 == -s) { 
             if (!$line($active,0)) { linesep -a }
             echo $color(info) -afilqr * /monitorfile: No longer monitoring $+(',$replace($hfind(monitorfile,$2,%i,w),\s,$chr(32)),') $&
               for changes (Stopped by user).
             linesep -a
             $+(.timermonitorfile,$hfind(monitorfile,$2,%i,w)) off
             hdel monitorfile $hfind(monitorfile,$2,%i,w)
           }
           else { echo $color(info) -afilr * $hfind(monitorfile,$2,%i,w) }
           inc %i
         }
         if (!$hget(monitorfile,0).item) { hfree monitorfile }
         linesep -a
         return
       }
       if (!$isfile($1-)) {
         if (!$line($active,0)) { linesep -a }
         echo $color(info) -abfilr * /monitorfile: No such file $+(',$1-')
         linesep -a
         return
       }
       hadd -m monitorfile $replace($1-,$chr(32),\s) $crc($1-)
       $+(.timermonitorfile,$replace($1-,$chr(32),\s)) 0 5 $+($iif(!$show,.),checkfile) $1-
       if (!$line($active,0)) { linesep -a }
       echo $color(info) -afilqr * /monitorfile: Now monitoring $+(',$1-') for changes. 
       linesep -a
     }
     else { return $hfind(monitorfile,$1,$iif($2 != $null,$v1,1),w) }
    }

  11. There isn't a section for just mIRC snippets/addons so i'll post this here.

     

    This snippet will monitor files for changes and tell you when they're changed or deleted.

     

    Note: this snippet will only work on mIRC 6.16, if you want to use it in older versions of mIRC then you can simply change '$v1' to '$ifmatch' on line 52.

     

    /*
    
    What does /monitorfile do?
    
    /monitorfile will watch a file and tell you when the file is modified or deleted, it will send a 'monitorfile' signal with either 
    'FILE_DELETE' or 'FILE_CHANGE' as the first parameter followed by the file that was being watched.
    If you don't use a . with the /monitorfile command (/.monitorfile) then you will also see some information in the active window when files
    are changed or deleted.
    All error/information messages should replicate mIRCs own messages.
    /monitorfile uses a 5 second interval to check for changes in files.
    
    How do I use /monitorfile?
    
    The syntax is: /monitorfile [off] <file>
    If you specify [off] then the specified file will no longer be monitored.
    Otherwise, the specified file will start being monitored.
    
    How does /monitorfile work? (For scripters)
    
    /monitorfile will store the crc value of a file when you start monitoring a file and check the current crc value against the stored one 
    every 5 seconds.
    If the value doesn't match then the FILE_CHANGE signal will be sent and the new crc value will be stored.
    If the file no longer exists when /monitorfile goes to check the current crc value then the FIlE_DELETE signal will be sent and the timer
    will be stopped. 
    
    Can you give me an example of using this?
    
    on *:start:{ .monitorfile $mircini }
    on *:signal:monitorfile:{
     if ($1 == FILE_CHANGE) && ($2- == $mircini) { echo $color(info) -afilr Hi $+($me,!) mIRC will just revert all changes to mirc.ini so $&
       there's no point in changing it unless you used the options dialog. :) }
    }
    
    How can I contact you?
    
    You can email me at [email protected] or [email protected]
    You can also find me in #mIRC or #mirc.net on IRC at irc.undernet.org but I am not always there.
    
    */
    
    alias checkfile {
     if (!$isfile($1-)) {
       .signal -n monitorfile FILE_DELETE $1-
       hdel monitorfile $replace($1-,$chr(32),\s)
       if (!$hget(monitorfile,0).item) { hfree monitorfile }
       $+(.timermonitorfile,$replace($1-,$chr(32),\s)) off
       echo $color(info) -afilqr * /monitorfile: No longer monitoring $+(',$1-') for changes (File was deleted).
       linesep -a
       return
     }
     if ($crc($1-) != $hget(monitorfile,$replace($1-,$chr(32),\s))) {
       hadd -m monitorfile $replace($1-,$chr(32),\s) $v1
       .signal -n monitorfile FILE_CHANGE $1-
       echo $color(info) -afilqr * /monitorfile: File $+(',$1-') has changed. 
       linesep -a
     }
    }
    alias monitorfile {
     if ($1 == off) && ($hget(monitorfile,$replace($2-,$chr(32),\s))) {
       hdel monitorfile $replace($2-,$chr(32),\s)
       if (!$hget(monitorfile,0).item) { hfree monitorfile }
       $+(.timermonitorfile,$replace($2-,$chr(32),\s)) off
       echo $color(info) -afilqr * /monitorfile: No longer monitoring $+(',$1-') for changes (Stopped by user).
       linesep -a
       return
     }
     if (!$isfile($1-)) {
       if (!$line($active,0)) { linesep -a }
       echo $color(info) -abfilr * /monitorfile: No such file $+(',$1-')
       linesep -a
       return
     }
     hadd -m monitorfile $replace($1-,$chr(32),\s) $crc($1-)
     $+(.timermonitorfile,$replace($1-,$chr(32),\s)) 0 5 $+($iif(!$show,.),checkfile) $1-
     echo $color(info) -afilqr * /monitorfile: Now monitoring $+(',$1-') for changes. 
    }

  12. If you're going to use timers then use the 'n' flag in $read():

     

    .timershowsongs 0 $iif($3,$3,300) msg $!chr(37) $!+ $right(#,-1) Look at this song: $!read(songs.txt,n)

  13. I like it, my only suggestion is that you add a keyboard accelerator to your "geekIRC" menu in the menubar.

    You can do this by putting an & before the letter you want to act as the accelerator, so if you used "&geekIRC" Alt+g would access that menu.

  14. on *:nick: { 
     kick $comchan($newnick,1) $newnick No name changes :|
    }
    

    Or something like this:

     

    on *:nick:{
     var %i = 1, %n = $($+(%,flood.,$site),2)
     if (!%n) { inc -u3 $+(%,flood.,$site) }
     else { inc $+(%,flood.,$site) }
     if ($calc(%n + 1) > 2) {
       while ($comchan($newnick,%i)) {
         if ($me isop $v1) { kick $v2 $newnick Flooding. }
         inc %i
       }
       unset $+(%,flood.,$site)
     }
    }

  15. still wrong tidy,

     

    it couldnt do anything cause the link to nhtml dll was wrong

    (which is contained in one of the files i told him to delete)

     

    thats why it couldnt write cause it couldnt load the dll in first place , thus there was nothing for it to try and write

     

    so reloading vinc remade the files with the correct paths and thus the dll loaded and he didnt get the write error , because there is now something for it to write

    When you only pass the filename to /write it will create a new file if the file doesn't exist and absolutely nothing if it does exist, try it yourself:

     

    /write x
    //write x $dll(c:\x)
    //write x $null

     

    c:\x is not a dll so your nhtmln theory cannot possibly be right.

     

    Edit: even if mIRC did give an error, it would most likely give an 'insufficient parameters' error rather than an 'unable to open file' one.

  16. unload vinc

    delete the following files

    vfchache.dat

    vpassport.dat

    vincula.ini

     

    and make sure nHTMLn_2.92.dll is in the vincula folder

     

    then go to mirc and reload vincula.mrc

    Although that could fix the problem it isn't likely to.

    Normally the "Unable to open <file>" error is given for one of three reasons:

     

    1) You're trying to write to a read-only file or a file protected by the operating system.

     

    2) The file has invalid characters in its name, eg: <>?

     

    3)

     

    The filename is the name of a system device, to demonstrate this try any/all of the following:

     

    /write con.txt x
    /write ip.txt x
    /write nul.txt x
    /write prn.txt x
    /write shadow.txt x

  17. (Tye's)

    Ftr, if someone leaves the room (kick, quit, etc) wouldn't the room limit need to go down instead of up?

    It does go down.

    It sets the channel limit to <number of users> + 1, that is still going down as a user has just left.

  18. on @*:join:#:{ mode $chan +l $calc($nick($chan,0) + 1) }
    on @!*:part:#:{ mode $chan +l $calc($nick($chan,0) + 1) }
    on !*:quit:{
     var %i = 1
     while ($comchan($nick,%i)) {
       if ($comchan($nick,%i).op) { mode $comchan($nick,%i) +l $calc($nick($comchan($nick,%i),0) + 1) }
       inc %i
     }
    }
    on @*:kick:#:{
     if ($knick != $me) { mode $chan +l $calc($nick($chan,0) + 1) }
    }

×
×
  • Create New...