Zugg Software :: View topic

Apprentice Joined: 20 Jul 2001 Posts: 127 Location: USA

I'm on a mud that doesn't use MXP, but I've successfully used it in a couple #SUB commands to give myself some of the experience.

I recently stumbled across an opportunity. A command used to change the ansi colors for mud objects (room desc, weapon, armour, monsters, players) has a bugging flaw in it.

basically, the command is supposed to be used like this

aset say green

and this will make all says that i see (whether i say them or not) green on my screen. it does this by setting 2 variables. the first "say_pref" stores the color code, and the second "say_suff" is usually set to "reset" so that color doesn't spew out where it shouldn't be.

The flaw in the command will actually let me put ANY text before and after each item. Example:

aset say blahblah
resulted in the output text being:
blahblahYou say: test

Am I explaining how that works, well enough? I used this to put a couple MXP commands in, and it worked!! So on to my question.

I know there are MXP tags that can be set to tell the auto mapper what is a room desc, room name, and room exits.

If i use this aset command to put the RoomName tag in the prefix, and the /RoomName tag is the suffix of a room name, will it work? will the automapper know that that is indeed the room name? What I'm concerned with is the MXP security. I don't know if I can just "make" the mud throw that command at me like that.

Also, room exits are shown like this:

The Obvious room exits are: West, South, North, and Down

now there are prefix, and suffix vars for this too. but can i have all of that text in the RoomExit MXP tag? will the automapper still know what's an exit(West, South, North, Down)? or will it think each word is an exit(The, Obvious, room)?

Any help you guys can give me on this, would be great :) It's kind of a large project for me, to go through and enter MXP commands into all the prefix and suffix variables. I don't want to have to do it twice, so I have to make sure it's right the first time :)

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

About the exits, you tag the whole line as RoomExits and then the mapper parses this lines and figures out that the exits come after "The Obvious room exits are:", so there should be no problem with that.

Now, about actually tagging these lines, you should have no problem if you define some elements of your own and set them as open. Example:
<!EL RName FLAG="RoomName" OPEN>
<!EL RDesc FLAG="RoomDesc" OPEN>
<!EL RExits FLAG="RoomExits" OPEN>

Now, theoretically, you should be able to use your aset command to put <RName> before the room name and </RName> just after it and have the mapper recognize it correctly. The same should work with room description and exits.

Kjata

Apprentice Joined: 20 Jul 2001 Posts: 127 Location: USA

I ran into a problem BEFORE I even got to the auto-mapper stuff

the two vars (say_pref & say_suff) do thier job, but when they fall on two seperate lines, zmud doesn't do the mxp thing right.

if the say is only one line, it works perfectly. but when it wraps to a new line. it's like it doesn't see the closing mxp tag. any idea how i can fix this?

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

I believe this is a bug that should have already been fixed in later versions. 6.16 is not the best version for MXP.

Kjata