Zugg Software :: View topic

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

I've finally begun using the mapper.. and it definitely a handy thing. Will definitely improve my quality of life once I get a lot of maps made.
My only issues so far are:
Background color... I take this to be the color that is the background on the mapper window.. No matter what color I pick it does not change.
(Cmud v2.37, Windows 7) In case either of those are an issue with it. My eyes just do not like the color that is the background. They slide over it and miss stuff. I have tried even with themes turned off on Win7, and a Basic Colorscheme.

My second issue has to do with the auto-detection of the mapper. I play on "Realms of Despair" and we have a compass feature that shows the exits in a room, as well as if they are locked, etc. Below is a visual representation of a room with the compass being in the top right corner.

Wizard Joined: 22 Mar 2007 Posts: 2320

You will have to extract the room name, exit list, and room description yourself (using triggers) from the mud text, then use #TAG to tell the mapper what the values should be. After creating the #TAG trigger(s), you need to re-configure the mapper so that it knows about the #TAG commands.

Wizard Joined: 22 Mar 2007 Posts: 2320

As for the map background, you need to edit the map configuration file, find the color section, and edit the colors there.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

I tried using triggers with TAG, and nothing got altered at all. Though perhaps I may have misconfigured something wrong. Each time I changed or made the triggers, I did reconfiguration like the helpfile said.

As for the background. Blargh.. why can't the config section just work. *trundles away*

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

It works for me. Try sending your map through the repair utility, and then delete your existing .zfg and make a new one.

Wizard Joined: 22 Mar 2007 Posts: 2320

Show us the exact script that you used to do the #TAGs. You probably have a bug in your trigger.

Wizard Joined: 22 Mar 2007 Posts: 2320

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

Sorry for the long delay, my schedule is a daytime one for sleeping.

Rahab: Yes the map color is still wrong in the configuration section.. changing it makes no difference. So I open up the file in notepad++ and just see a bunch of 'NUL" "SOH" "ENQ" etc. So naturally I did not mess with any of that.
Though I do see the expression that it believes is my prompt. I have very little experience with Regex.. other than a semester for writing asp.net scripts.. and we only used it a couple times. The expression it has listed is:

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

Update: OK. So having been a little annoyed, I deleted my characters whole session, and all of their files in the cmud directory. Then remade the triggers, reconfigured, etc etc.
Room name, description and exits now work fine for detection with the above trigger. I don't know why, perhaps one of my other triggers I have was causing an issue or it didn't come in from zmud entirely proper.

The colors still won't change for the background though. But the other colors all change. Room, Links, Above, Below, etc.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

Oh well, I give up, but thank you guys for your assistance :D The mapper is working fine, and I will just deal with the not so nice background color. Hope you all have a good day.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

I take the last post back... Thought the mapper was fine, hadn't had time to actually sit down and map, just did the configuration, and saw that it made the room properly on the map. Nothing else mapped though. It would only add a room and desc, etc when I did reconfigure. I'm not sure if the reconfigure option actually causes the client to do something more than just move. But it selected the right text for name/desc/exits automatically with the trigger above. Just never worked when manually inputting a direction. Any ideas on this?

As for the background color.. it still doesn't change in zmud.. but if I change my desktop them to say, a high contrast black, or white. the background of zmud will change then and only then. Any thoughts here would be appreciated as well.

Thanks again for all of you guys help, you really save some headaches :)

Magician Joined: 28 Jan 2007 Posts: 430

Hasn't the talk so far been about CMud? They're two completely different products, why are people still unable to comprehend that.

Anyways, you should give text examples from Mud with Exits line, Desc, prompt etc.

You probably have something funky going on in your own triggers you previously tried to no avail. Reconfigure isn't reliable, for any trouble, you're
supposed to use #tag triggers.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

Sorry, yes it is cmud. I typed zmud out of habit. I just only recently started using cmud, had a break from muds for over 6.5years, and was used to using zmud. No need to be condescending though for a simple misspelling, especially when you saw me even say the version I use in the first post since you read it. Or maybe you didn't. Since I provided a room output as well as prompts.

As for tag triggers, I do use one to capture the room name, the rest the configuration captures in the example. So I don't know why it wouldn't in the general use. Really, you didn't say anything that was useful. But thanks for being condescending. :)

Wizard Joined: 22 Mar 2007 Posts: 2320

Your trigger pattern has (%1) in it. You should not use %1, %2, etc. inside a trigger pattern. Your trigger pattern should be:

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

You are correct in that sir, I copied this trigger from here on the forums.. and didn't change anything that actually worked in the trigger itself. But yeah, bad practice and all that. Thanks!

Wizard Joined: 22 Mar 2007 Posts: 2320

In this case it was more than just bad practice. You had "(%1)(*)~ ". Cmud might not have been able to figure out what should go into %1. Have you tested it again since that fix?

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

It found what was to go in the %1 properly before it actually. Though %2 would also catch the room name, as well as the space after it. but it did correctly grab the roomname with %1. since the fix you suggested, it will map the new rooms. but now the desc's while saying as detected in the reconfigure window, will not show up. but the exits and roomname will show up properly. I'm afraid I don't know how to get the #TAG command to work for roomdesc entirely. So that was the big thing that the autoconfigure grabbing it was really nice for.

Wizard Joined: 22 Mar 2007 Posts: 2320

To use the #TAG to work on the description, you have to get the entire description into a single variable (call it @roomdesc or something), then

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

Yes sir, it is the problem of me capping the desc into a variable. As for the 2 lines, yes as well. So long as I have the compass on, that format will always be there. I prefer the compass being on, so obviously I want to get it to work with it on. It is exactly how you described it. Name, 2 lines I don't care about, the description, then Exits: . I will give it a try in just a few minutes and holler back at you.

Wizard Joined: 22 Mar 2007 Posts: 2320

I just spotted a small bug in my code and edited it above.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

K. regrabbed it.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

Hrm, that just sets the room name as the desc, the full line of the roomname including the compass directions. As well now it isn't grabbing the room name correctly. It is adding the compass directions to the name, as well as the line after. So the above room would have:

"Darkhaven Square NW N NE------------------------------------------------------- W -U-(+)--- E "
as the roomname, and the same exact thing as the room desc.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

OK.. so.. with some more work at this.. I changed the trigger I made, as well as you made.. to try to narrow it down.. so I have this now:

Sorcerer Joined: 15 Apr 2011 Posts: 809

Two problems that I see. First, the #SET should be a #STATE. Second, the roomdesc variable is never being cleared, so rooms will have the descriptions of the all previous rooms you've been through tacked on at the start. Just add a roomdesc = "" to empty it in the first trigger state, and you should be good to go.

Wanderer Joined: 12 Feb 2003 Posts: 93 Location: USA

PHEW! After fiddling with it all day.. trying many different ways to capture it all. I ended up using this: