Using the debug window

Posted by Nick Gammon on Wed 06 Jun 2001 04:51 AM — 1 posts, 6,492 views.

Australia Forum Administrator #0
On the MUSHclient configuration screen -> Output tab, you can set MXP Debug level to:

None - no messages
Errors - only show errors
Warnings - show errors and warnings
Information - show errors, warnings, and information
The Lot - Same as Information, plus every tag as it is encountered

MUD server implementors are encouraged to set the Debug Level to Errors or Warnings, and check the window periodically to see whether MUSHclient is giving warnings or errors.

Also, if you are just playing on a MUD, you might want to check the window, particularly if you think "something is missing". It might be that text between < and > has been discarded.

The debug window uses the inbuilt notepad, and can be saved to disk, copied and pasted, and printed in the usual way.

The debug window displays look like this:


A: ( 28) MXP element: <language type>
E: ( 28) Unknown MXP element: <language type>
A: ( 64) MXP element: <i>
A: ( 64) MXP element: <b>
A: ( 64) MXP element: </i>
W: ( 64) Closing out-of-sequence MXP tag: <b>
A: ( 64) MXP element: </b>
W: ( 64) Closing MXP tag </b> does not have corresponding opening tag
I: ( 83) MXP reset.
I: ( 83) MXP turned off.


The first letter on each line is the debug level (E=Error, I=Information, W=Warning, and A=All).

You could use that to quickly search for errors (ie. search for "E:").

The number in brackets is the line number in the output buffer of the current line when the message was displayed. To go to that line press Ctrl+Alt+L and type in the appropriate line number.