Hi all!

I know how to add and trap "/" commands, but my question is how to grab the param data...for example If I type:
/Joel somedata
How do I get only somedata?
Thanks!

I don't know what method you use to trap "/" commands, but you normally use ChatWndSendMessage(Message).

Then the variable Message, is the whole message that was sent, including to bit after the parameter, so you can get all the data you want from there.

e.g.

code:

---

function OnEvent_ChatWndSendMessage(ChatWnd, Message) {
var checkExpCommand = /^\/command/i
if ( checkExpCommand.test(Message) ) {
  Param = Message.replace(checkExpCommand, "");           
}
}

---

You can do:

code:

---

var Command = "/Joel";
if(Message.substr(0, Command.length) == Command)
{
  // The /Joel command was used.
}

---

code:

---

var Param = Message.substr(Command.length, Message.length);

---

This method is my favourite and it VERY well written.  If there is anyway that people should get commands in general it is using this method posted by CookieRevised

CookieRevised's reply to [Release] Exit WLM

ahh thank you i wqas looking for this

also if i do

code:

---

function OnEvent_ChatWndSendMessage(ChatWnd, Message) {
if (Message == "/woot") {
Debug.Trace("WOOT");
}
}

---

quote:

---

Originally posted by DarkGhost
also if i do

code:

---

function OnEvent_ChatWndSendMessage(ChatWnd, Message) {
    if (Message == "/woot") {
        Debug.Trace("WOOT");
    }
}

---

how can i make it so it doesnt say "The command you entered was not recognized"

---

code:

---

function OnEvent_ChatWndSendMessage(oChatWnd, sMessage) {
    if (/^\/([^ \n\r\v\xA0\/][^ \n\r\v\xA0]*)[\s\xA0]?([\s\S]*)/.exec(sMessage)) {
        var command = RegExp.$1.toLowerCase();
        var parameter = RegExp.$2;
        switch (command) {
            case 'myname':
                // <- Lets tell the function we handled the command. Pass something back to the conversation.
                MsgPlus.DisplayToast("Handled Command", "'" + command + "'\n'" + parameter + "'");
                Debug.Trace("command handled/recognized: '" + command + "', parameter: '" + parameter + "'");
                return "Hi, I'm a cookie!";
            case 'donothing':
                // <- We recognize the command, but we return the same message/command as-is.
                //    This is usually BAD code since it will cause the "command not recognized" error from
                //    Messenger Plus! to pop up if other scripts didn't recognized it. However, it could be
                //    used to intercept commands from other scripts and act upon them without disturbing the output.
                MsgPlus.DisplayToast("Handled Command", "'" + command + "'\n'" + parameter + "'");
                Debug.Trace("command handled/recognized: '" + command + "', parameter: '" + parameter + "'");
                return sMessage;
            case 'showcommand':
                // <- We recognize the command, and we return the same message/command as a text by adding a
                //    second slash. Since it is interpreted as text from that point on by Messenger Plus!,
                //    you wont get the "command not recognized" error.
                MsgPlus.DisplayToast("Handled Command", "'" + command + "'\n'" + parameter + "'");
                Debug.Trace("command handled/recognized: '" + command + "', parameter: '" + parameter + "'");
                return "/" + sMessage;
            case 'clearme':
                // <- Lets tell the function we handled the command. But nothing needs to be passed back to
                //    the conversation and nothing needs to be send to the server; so let's simply clear the
                //    text from the typing area.
                MsgPlus.DisplayToast("Handled Command", "'" + command + "'\n'" + parameter + "'");
                Debug.Trace("command handled/recognized: '" + command + "', parameter: '" + parameter + "'");
                return "";
            case 'wrongcode':
                // <- We recognize the command and act upon it, but we return nothing or 0, so Messenger Plus!
                //    does not know we did handle the command. This is BAD code because it will also cause the
                //    "command not recognized" error from Messenger Plus! to pop up.
                MsgPlus.DisplayToast("Handled Command", "'" + command + "'\n'" + parameter + "'");
                Debug.Trace("command handled/recognized: '" + command + "', parameter: '" + parameter + "'");
                return 0;
            default:
                // <- We don't recognize any other commands, so we return nothing or 0.
                //    Let the other installed and running scripts handle what is written in the conversation.
                MsgPlus.DisplayToast("Unhandled Command", "'" + command + "'\n'" + parameter + "'");
                Debug.Trace("command recieved but not handled/recognized: '" + command + "', parameter: '" + parameter + "'");
                // no return statement here.... or return 0
                return 0;
        }
    }
}

---

k ty
    if (/^\/([^\s\/]+)\s*([\s\S]*)$/.exec(sMessage) !== null) { whats this mean? - also is there a way i can just like make it so the person who typed /command can only see the message

quote:

---

Originally posted by DarkGhost
if (/^\/([^\s\/]+)\s*([\s\S]*)$/.exec(sMessage) !== null) { whats this mean?

---

quote:

---

Originally posted by DarkGhost
also is there a way i can just like make it so the person who typed /command can only see the message

---

Ah...thanks all for your tips!!!

I just wanted to update Cookie's regex to something that is a little better IMHO

code:

---

if (/^\/([^\s\/]\S*)\s*(.*)/.exec(sMessage) !== null) {

---

code:

---

if (/^\/([^\s\/]\S*)\s*(\S*)/.exec(sMessage) !== null) {

---

code:

---

if (/^\/([^\s\/]\S*)\s*((?:\S+\s)*)/.exec(sMessage) !== null) {

---

code:

---

if (/^\/([^\s\/]\S*)\s*(?:\[.*?\]\s*(?:\[.*?\]\s*(?:\[.*?\])?)?)?/.exec(sMessage) !== null) {

---

I know this is an old thread, but here are some important things I never bothered to reply with before because it is rather much. But still, since this topic comes up now and then:

quote:

---

Originally posted by markee
And finally [\s\S] is simply the equivalent of "."

---

code:

---

if (/^\/([^ \n\r\v\xA0\/][^ \n\r\v\xA0]*)[ \n\r\v\xA0]?([\s\S]*)/.exec(sMessage)) {
    var command = RegExp.$1.toLowerCase();
    var parameter = RegExp.$2;

---

code:

---

if (/^\/([^ \n\r\v\xA0\/][^ \n\r\v\xA0]*)[\s\xA0]?([\s\S]*)/.exec(sMessage)) {
    var command = RegExp.$1.toLowerCase();
    var parameter = RegExp.$2;

---

code:

---

if (/^\/mycommand(?:[ \n\r\v\xA0]([\s\S]*))?$/.exec(sMessage)) {
    var parameter = RegExp.$1;

---

code:

---

if (/^\/([^ \n\r\v\xA0\/][^ \n\r\v\xA0]*)(?:[ \n\r\v\xA0]([\s\S]*))?$/.exec(sMessage)) {
if (/^\/([^ \n\r\v\xA0\/][^ \n\r\v\xA0]*)[ \n\r\v\xA0]?([\s\S]*)/.exec(sMessage)) {
if (/^\/([^ \n\r\v\xA0\/][^ \n\r\v\xA0]*)[\s\xA0]?([\s\S]*)/.exec(sMessage)) {
    var command = RegExp.$1.toLowerCase();
    var parameter = RegExp.$2;

---

code:

---

if (/^\/mycommand(?:[ \n\r\v\xA0]([\s\S]*))?$/.exec(sMessage)) {
    var parameter = RegExp.$1;

---