disconnect & Quit

[Undeference]

I just looked at this. This is extremely dumb. Do you want a trigger that can easily be changed by simply changing the text there and not having to save settings, or do you want people to have to click "Save settings" or something along those lines?

It would make a lot more sence to use a global string called trigger or something.
using more expresive code than what the vars are actually called:

Code Select Expand


If Left(LCase(message),Len(trigger))=trigger Then
'...there's your trigger
If Mid(LCase(message),Len(trigger),10))="disconnect" Then
  'disconnect
ElseIf Mid(LCase(message),Len(trigger),4)="quit" Then
  'disconnect&quit
End If
End If

First thing I do is check to see what the person's access is. Then I check for a trigger IF THEY HAVE ENOUGH ACCESS TO USE ANY COMMANDS, I then find the word after the trigger (until the first space) and search for a command that matches that. After that I see if they can use the command and then do whatever it is that that command does.

[Kp]

Is it completely lost on you that the last response to this topic was in May?

[Undeference]

So... as I said, I was just looking at it. But not that I expect anybody to be anywhere efficient.