MXP Help.... Not working

Posted by Creeper386 on Fri 02 Nov 2001 11:02 PM — 8 posts, 30,795 views.

Creeper386 USA Fri 02 Nov 2001 11:02 PM #0

Alright. I downloaded the Smaug with MXP and it has tags and everything but they show up literally. As in your see

Exits: <Ex>North</Ex>

Or similar.

I'm just figuring out what I am doing with the rest of the code so not worrying too much about this just wondering if anyone knows the answer...

Thanks ahead of time.

Creeper

Nick Gammon Australia Forum Administrator Sun 04 Nov 2001 08:59 AM #1

Which client program are you using? Some clients won't detect the MXP tags, and earlier versions of zMUD (if you are using that) need a slightly modified version of the code to make it work properly.

Creeper386 USA Mon 05 Nov 2001 05:23 AM #2

I'm using the newest one I could download 6.16 I think Yeah thats right.

Nick Gammon Australia Forum Administrator Mon 05 Nov 2001 08:15 PM #3

My SMAUG server changes use the new 'mode changes' in the MXP spec. The first version of zMUD that supports that is 6.20. From their site I see this change under 6.20:

Support for new modes: ESC[3z,4z,5z,6z,7z

There are three things you can do...

Wait for the newer version of zMUD.
Use MUSHclient which correctly supports these modes
Patch the SMAUG server slightly to make it work with zMUD 6.16.

The patch is described in this post: Zmud, MXP, and Smaug

Creeper386 USA Thu 08 Nov 2001 11:09 PM #4

Okay I figured I'd just take out MXP from it for now with still giving the choice of putting it back in easily. Would that be hard to get out that code or not? I thought it might be the area files but found out it obviously itn't after getting new area files. Don't really want to get new code although getting it to compile isn't hard it's some busy work I don't have time for.

Creep

Nick Gammon Australia Forum Administrator Fri 09 Nov 2001 02:28 AM #5

The MXP stuff is only in the source code, not the area files.

I suppose you could take it out, but the patch to fix the problem is only half-a-dozen lines, which is simpler than removing a few hundred.

If you want to remove it the simplest thing is to download the version of the server without the MXP patches.

Creeper386 USA Fri 09 Nov 2001 03:10 AM #6

So there isn't an easy way to at least stop the MXP from working? Because in order it to compile on an older cygwin I have to make quite a few changes though not hard it takes awhile. And when I won't always be using a newer zMUD or even on as new as 6.16 I also know alot of the people that are going to play it or at least help me with it aren't going to be using a newer zMUD thats why just patching it won't help too well.

Guess if all else fails I'll have to go back through and and change the code without MXP hopefully I haven't forgot anything I did though. Good thing I haven't done anything major.

Creep

Nick Gammon Australia Forum Administrator Fri 09 Nov 2001 03:59 AM #7

Probably you can take MXP out temporarily by adding one line to comm.c.

Add the extra "return" to turn_on_mxp which should leave it turned off.


void turn_on_mxp (DESCRIPTOR_DATA *d)
  {
  return;   /* no MXP for now */  
  d->mxp = TRUE;  /* turn it on now */

... and the rest ...

  }

Maybe also comment out the line that asks the client if it wants MXP:



  /* telnet negotiation to see if they support MXP */

 /*    write_to_buffer( d, will_mxp_str, 0 );  */