ah ok
i didnt read all posts

It used to be WorldDMT.. read above

:P I was actually using on me:*:join:#:{ but changed it to the regular join event, because the $ial().mark becomes empty when a user hops. Perhaps I have thought wrong in the process of making the script.

Nice snippet :)
And worldGMT, perhaps.

hey

i think on :join:#: who # should be on me::join:#: who #

Thank you, FordLawnmower. I'll incorporate your example into the snippet when I get around to it, along with the credit due to you.

Doesn't the use of "ialmark" here conflict with your realname script ?
I use ialmark a lot in my personal scripts and I've found it much easier to manage storing items in their own field using a delimiter. ie. realname=fred | access=friend | nicknames=fred joe ted bill | etc.
Here is a basic alias that checks for an item= and edits or creates it using =value. This uses ascii 01 as a delimiter, but this is just an example.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;Usage /ialmark_ nickname item value(s) go here.
;Or $ialmark_(nickname, item) <--Will return the value of item if it exists.
alias ialmark_ {
  var %item $2
  if ($isid) {
    if ($regex($ial($1).mark,/ $+ %item $+ =([^\x01]*)/i)) return $regml(1)
  }
  else {
    var %value $3-
    if (!$regex($ial($1).mark,/ $+ %item $+ =[^\x01]*/i)) {
      .ialmark $1 $addtok($ial($1).mark,$+(%item,=,%value),1)
    }
    else {
      .ialmark $1 $regsubex($ial($1).mark,/( $+ %item $+ =[^\x01]*)/i,$+(%item,=,%value))
    }
  }
}

I find it much easier to manage this way. I'm sure there are many other ways to manage ialmark so it can be used by multiple scripts.

If I'm going to add a basic flood protection as I always do, it'll shut Dean's pie hole.

I'm gonna update the script later. What you have mentioned has already been said by wims, and I don't really need your harsh tone to bark at me.

I was mystified myself when I debugged my code without halt and received this error in the status:> * /msg: insufficient parametersWIth halt, the error disappears.

"Without the halt command, it will generate an error if someone checks a fictional nickname. The halt actually helps it."
I don't see how, there's an if statement, if a non existing nick is given, the if shouldn't be true :/

-you don't need to halt in the previous alias, why are you halting there?Without the halt command, it will generate an error if someone checks a fictional nickname. The halt actually helps it.> -on :join:#: who # < if a netsplit occurs, everyone using your code will be disconnected if used on some big channels, you should /who when $nick == $me only, and otherwise store the information:P I was actually using on me::join:#:{ but changed it to the regular join event, because the $ial().mark becomes empty when a user hops. Perhaps I have thought wrong in the process of making the script.

Thanks for your suggestion. I'll surely take it under consideration and make the snippet better later.

Some way to improve this:
-you should use $wildsite inside events instead of $address($nick,2)
-you shouldn't halt the raws everytime, i don't want your script to disable any message.
-$hfind is slow, here $hfind(pnick,$+(!@,$4),1,n) is simply $hget(pnick,$+(!@,$4)) but i would remove that condition and add to the table every information from the /who, because actually it's not really storing every possible information (you are not using on text either to store information about the nick talking), i think you should
-the on start event has a problem, it /hload everytime, whatever if the table exists and whatever if the file exists
-you don't need to halt in the previous alias, why are you halting there?
-on *:join:#: who # < if a netsplit occurs, everyone using your code will be disconnected if used on some big channels, you should /who when $nick == $me only, and otherwise store the information

loLLL

I updated the script and eliminated the error Dean has reported. But unfortunately I felt disrespected by his comment so I had to delete his post.

Thank you, xdesoto.

Nice Jethro.

Could be useful for me, there's a server I frequent where people do a lot of /nicking x.x

extremity, you can modify the snippet to hsave the data right after hadd. That way, you know it's saved every time a data is added to the hash table.

Thanks for the rating and likes.

oh and nice snippet for a nicklogger..

only downside with hash saving on exit or part is if your computer or mirc crashes.. you lose all your data..

it is more resource hogging, but i save important hashes on a timer or on every update..

Nicely nicely... I like \o/