Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ Bug reports
➜ OnPluginMXPerror - parameters
|
OnPluginMXPerror - parameters
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Beale
(35 posts) Bio
|
| Date
| Sun 16 Jan 2005 10:59 AM (UTC) Amended on Sun 16 Jan 2005 11:00 AM (UTC) by Beale
|
| Message
| It would seem that when OnPluginMXPerror is called, rather than having the parameters level, line, number, message, it puts all the values into the level parameter separated by commas.
Example:
function OnPluginMXPerror (level, number, line, message)
world.Note(level)
world.Note(number)
world.Note(message)
world.Note(line)
end
Produced this:
A,20000,884,MXP element: </event>
nil
nil
nil
| | Top |
|
| Posted by
| Nick Gammon
Australia (23,158 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Thu 20 Jan 2005 10:17 PM (UTC) |
| Message
| | According to the help file and online documentation those 4 arguments apply to the main script file "mxp error" processing, but not the plugin processing. Just split them up at the commas. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
10,033 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top