Ah, yes I did misunderstand.
- I'm not sure about that;
I think that we should add a registercommand function to the PS system that works very much like the menu's do:
CODE
Sub Example_Event_Load()
'//If it throws an error.
On Error Resume Next
'// RegisterCommand(Prefix, CommandName, Access, Flags, Type (determins if usable outside of the bot, and other options)
RegisterCommand "Example", "Dance", 20, "", 1
If Err.Number <> 0 Then
'//I.E. "Example: Command "Dance" already exists from plugin: "OtherPlugin" "
Addchat VBwhite, "Example: " & Err.Description
End If
'//Woosh, all gone.
Err.Clear
On Error Goto 0
End Sub
Sub Example_Commands_Callback(Command, Username, Args, DspID)
Select Case Command
Case "Dance"
Dsp DspID, "/me Dances", Username, 0
End Select
End Sub
If I understand what you're saying, - it would
Require a UI form; and you couldn't make commands from in the channel-- well, I guess you could with a lot of :'s -- And would be as powerful (and risky) as /exec
But if it's the user doing it anyway-- he might as well open notepad++ and write it.
However, it's a cool concept- to have all your commands organized like that- click on a command and view the VBs code for it right in the box.
-- Or am I still misunderstanding?
The above concept would be a step in the right direction - as far as easily created VBs commands.