..Sorry, I couldn't find a more fitting title.
What I want to do is capture a MXP entity, and display it's value in the info bar. I want this info constatnly updated each time the client receives said entity.
Now, the only way I have thought yet is to put a function in the script file that processes MXP errors(with arguments given in the help file). Then I add said function to "MXP Script Routines" under "Error". Thus every message that involves MXP gets checked, and my function fires when needed.
My question: Is there any other way?
First of all, I don't think it's too effective, cause it's checking a lot of information(not only errors, but ino, warnings, and something else I forgot), so it's slower than it could be.
Second, I don't know if the Error MXP script routine accepts more than one function. If it doesn't, I wouldn't want to keep my function there. Cause I might need the sace for something else.
I only receive the MXP entities when I send commands to the MUD(any commands), so I thought I'd do a trigger, but I don't know how to make a trigger match anything I send(not anything I receive).
Also, I would eventually want to put this into a plugin. What limitations would apply and what can I do to not be restricted?
I know I could probably have found the answer if I'd peruse Lua's docs and the help files for a few hours or more(I'm a very big MUSHClient newbie), but it's really late, and if anyone can be bothered to drop me a response, please do.
What I want to do is capture a MXP entity, and display it's value in the info bar. I want this info constatnly updated each time the client receives said entity.
Now, the only way I have thought yet is to put a function in the script file that processes MXP errors(with arguments given in the help file). Then I add said function to "MXP Script Routines" under "Error". Thus every message that involves MXP gets checked, and my function fires when needed.
My question: Is there any other way?
First of all, I don't think it's too effective, cause it's checking a lot of information(not only errors, but ino, warnings, and something else I forgot), so it's slower than it could be.
Second, I don't know if the Error MXP script routine accepts more than one function. If it doesn't, I wouldn't want to keep my function there. Cause I might need the sace for something else.
I only receive the MXP entities when I send commands to the MUD(any commands), so I thought I'd do a trigger, but I don't know how to make a trigger match anything I send(not anything I receive).
Also, I would eventually want to put this into a plugin. What limitations would apply and what can I do to not be restricted?
I know I could probably have found the answer if I'd peruse Lua's docs and the help files for a few hours or more(I'm a very big MUSHClient newbie), but it's really late, and if anyone can be bothered to drop me a response, please do.