You have a point. I must have daydreamed.

and jethro you wouldnt want the @ command here anyways. the first one is to mod yourself so the @ command would make it not work because your not mod on the channel even though what your trying to do is mod yourself haha

Sorry, didn't know about the '@' I see what you're saying now. Either way though it'd still be pointless >> You should know when you're +o, to -o

You don't have to be. op'd. When you type +op It identify s to chatspace, making you moderator. and if you're already moderator -o removes it. fyi

ShaferBatman, > on @*:INPUT:#:{ make sure you're opped.

on *:INPUT:#:{ if ($1 == +op) { services identify #Roomname Password } | if ($1 == -o) { mode $chan -o $me }

+op = identify
-o = -o

See I change my passwords from time to time so that people don't have all that much time to figure it out. Mostly random alpha-characters though.

Why did you put a $1 in replacement for the actual Password though? The $1 is the identifier for the pass. If your pass stays the same, you can have it hard-coded as intended. The $1 should have been $$1 (with double dollar signs) so that it must be filled before the script will trigger. If you choose to have it with single dollar sign, you must make an if condition as in: if ($1) { or else the script will trigger if $1's value is not filled.

I keep most of my code clean in that area so when I add them I don't seem to have a problem. saves time for me having to keep track of the remote scripts I have loaded in case a specific alias isn't there. For big aliases though, then i'll keep them added as a separate remote script though.

I create my own little seperators by starting a line off with a comment semicolon.

something like
;--------------------------------------------------
works for me to separate my aliases into categories if needed, but I only have one of those separators now.. seems a bit unorthodox but it does help me visualize a separation between my needed aliases and my custom ones lol

yea that works too i put all my aliases in my remotes tab though. my aliases tab seems to dislike me most of the time and doesnt wanna work

that would work I guess, but it doesn't show the "!ident" value in the channel. I kind of like it showing, then when someone else tries it to thinking that it's an actual command nothing happens for them haha.

Also, i would just put it in the aliases as

/ident {
    if ($me isop #) {
      mode # -o $me
      return
    }
    services identify # Pass
  }
}

If i was to do it that way... Why did you put a $1 in replacement for the actual Password though?

alias ident {
    if ($me isop #) {
      mode # -o $me
      return
    }
    services identify # $1 
  }
}

ah, I didn't think of it that way. I also should have noted that in my original code you don't need the else if with the (($1 == !ident)). You could also just use else instead to eliminate that little extra bit.

Thanks Jethro_

I believe you only need one command for !ident:

on *:input:#:{
  if ($1 == !ident) {
    if ($me isop #) {
      mode # -o $me
      return
    }
    services identify # PASSWORD 
  }
}

No need to supply the cmd char.

nice to see that chatspace servers are still in use.. lol