Register forum user name Search FAQ

Gammon Forum

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 ➜ MXP and Pueblo ➜ Zmud, MXP, and Smaug

Zmud, MXP, and Smaug

It is now over 60 days since the last post. This thread is closed.     Refresh page


Posted by Eos   USA  (52 posts)  Bio
Date Thu 09 Aug 2001 04:10 AM (UTC)
Message
Unlike Mushclient, Zmud at the moment has a problem understanding MXP. It is currently misinterpreting user defined elements, which is something only Zuggsoft can fix, but it is also not accepting any MXP flags not sent to it in secure mode.
Top

Posted by Nick Gammon   Australia  (23,140 posts)  Bio   Forum Administrator
Date Reply #1 on Thu 09 Aug 2001 05:50 AM (UTC)

Amended on Thu 09 Aug 2001 05:52 AM (UTC) by Nick Gammon

Message
For my SMAUG port with MXP I have a small patch that will fix the problem with the current version of zMUD (6.16).

The patch is only a few lines, and basically sends "turn into secure mode" before every MXP command.

Save the patch below to disk in the "src" directory, then type:


patch -p5 < zmudfix.patch


This will patch the file comm.c.

Then do a "make".

After applying this zMUD users will see hyperlinks, however the only ones that work properly are the exits, because zMUD 6.16 has a bug in processing attributes for MXP tags (these are discussed at some length on the zMUD developers pages).

Patch appears below - copy it and paste into Notepad, then save as zmudfix.patch.





*** ../../../smaugmxp/dist/src/comm.c	Wed Jul 18 16:48:38 2001
--- comm.c	Wed Jul 18 16:53:58 2001
***************
*** 1466,1471 ****
--- 1466,1473 ----
          bInTag = TRUE;
          if (!bMXP)
            count--;     /* not output if not MXP */   
+         else
+           count += 4;  /* allow for ESC [1z */
          break;
  
        case MXP_ENDc:   /* shouldn't get this case */
***************
*** 1542,1548 ****
--- 1544,1554 ----
        case MXP_BEGc:
          bInTag = TRUE;
          if (bMXP)
+           {
+           memcpy (pd, MXPMODE (1), 4);
+           pd += 4;
            *pd++ = '<';
+           }
          break;
  
        case MXP_ENDc:    /* shouldn't get this case */




- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Yourdrunkendad   (35 posts)  Bio
Date Reply #2 on Wed 27 Aug 2003 01:08 AM (UTC)
Message
I installed this patch and it works almost flawlessly,
the only thing I've noticed is that occasionaly it will show this.

&lt;26055hp 29788m 1014mv&gt; &lt;#10533&gt;

whereas my normal prompt is:

<26055hp 29788m 1014mv> <#10533>

Shampoo is for sissies real men use poo*
[werd]thewerd.com "Smacking Your Mom Then Running Away"
Top

Posted by Nick Gammon   Australia  (23,140 posts)  Bio   Forum Administrator
Date Reply #3 on Wed 27 Aug 2003 03:58 AM (UTC)
Message
This is with zMUD? Sounds like it didn't go into secure mode for some reason.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Yourdrunkendad   (35 posts)  Bio
Date Reply #4 on Wed 27 Aug 2003 10:08 PM (UTC)

Amended on Wed 27 Aug 2003 10:13 PM (UTC) by Yourdrunkendad

Message
yeah it's with zmud 6.16.
It also does it when you type equipment or look at another player.

I also received this message when installing the patch with cygwin, in WindowsXP


$ patch -p5 < zmudfix.patch
missing header for context diff at line 3 of patch
(Stripping trailing CRs from patch.)
patching file comm.c
Hunk #1 succeeded at 1468 (offset 2 lines).
Hunk #2 succeeded at 1546 (offset 2 lines).

Shampoo is for sissies real men use poo*
[werd]thewerd.com "Smacking Your Mom Then Running Away"
Top

Posted by Nick Gammon   Australia  (23,140 posts)  Bio   Forum Administrator
Date Reply #5 on Thu 28 Aug 2003 06:42 AM (UTC)
Message
First try using MUSHclient in a similar session. If the bug does not appear you have a zMUD bug, pure and simple. Thus, fiddling with the server code won't help any.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

Posted by Samson   USA  (683 posts)  Bio
Date Reply #6 on Sat 29 Nov 2003 07:01 PM (UTC)
Message
Heh. Would it be inappropriate to mention that Zmud *IS* the bug? :P
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.


23,439 views.

It is now over 60 days since the last post. This thread is closed.     Refresh page

Go to topic:           Search the forum


[Go to top] top

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.