Zugg Software :: View topic

Beginner Joined: 04 Jul 2011 Posts: 25

Hi All!

I've been working with the CMUD mapper for a few days now and it's been working great! But I have found one issue that has me stuck.
The MUD I play on has an elevator system that some zones use. The particular one in question has 3 floors, mf, b1, l2. The CMUD mapper (with a quick script, is able to get to b1 and l2 no problem. However, you get to one of those 2 floors, and try to get back to mf, the mapper gets confused and mistakenly marks you in a different location.

I think the problem is the exits. To exit the elevator to MF, you must go west, go exit the elevator to go to B1, you go south, and finally to go to L2, you must go west. I think this is where the issue lies. Since 2 different areas both use WEST to exit the elevator, the mapper automatically uses the first WEST everytime, so you're never able to get to the MF, it will always go to L2 because it's higher up on the list.

I tried to make this as clear as I could, please ask questions for clarification.

TL;DR, elevator has 2 different areas that use west as an exit, mapper incorrectly concludes the first area is the only west.

Thank you so much!

-Bitties

Posted: Tue Jul 05, 2011 3:34 pm

redefine it to NW or SW if those exits arent already taken, the jst but the actuaally west command in the name field

Beginner Joined: 04 Jul 2011 Posts: 25

Posted: Tue Jul 05, 2011 5:50 pm

I've run into an elevator system before myself. The way I handled it if I remember correctly was I set up a command input trigger that would fire when I selected the floor. A #waitfor in the trigger waited for the door opening message then moved me out of the elevator and set my position on the map with a #teleport command. I'll look through my backed up packages and see if I can find some examples if they are needed but it worked well I think.

Beginner Joined: 04 Jul 2011 Posts: 25

Posted: Tue Jul 05, 2011 7:00 pm

Below is a class full of room scripts I had set up for one such elevator. Room 657, 3202, 3208, 3215, 3223, and 3228 were the"lobbies", when I entered those room a pickbox would come up asking if I wanted to board the elevator. Select yes and the script would send the push button command which fired the command input trigger for that room. The #waitfor waited for the doors opening message sent the correct direction to the mud to enter the elevator then teleported me to room 3229 on the map which I had set up as the elevator's room.

Once I entered room 3229 the enable script for that room threw up another pickbox where I could select which floor I wanted. Selecting a floor from that pickbox sent the command to the mud and fired a command input trigger for that particular floor's button command. That command input trigger had a specific #waitfor message that when triggered sent me in the correct direction the #teleported me to the proper room on the map.

The syntax is #TE vNum zone where vNum is the number the mapper uses for that room and the zone is the zone name the room is in. The script below won't be of any use since your rooms will have different numbers of course, but maybe it will give you a better idea of how things worked if you imported it into a blank session and took a look.

Beginner Joined: 04 Jul 2011 Posts: 25

Wow, that is really awesome. Thank you for posting that. Instead of using #waitfor like you do, I just through in an random number, yours makes way more sense. When you create this, you don't use the GUI? I haven't seen my map written out like this before, so I think I understand what I'm looking at for the most part, but still a bit confused.

Thanks!

-Bitties

Posted: Tue Jul 05, 2011 8:32 pm

To make the room triggers I right click on the room I want to make triggers for, then click on properties. When the Room Properties box pops up click on the tab with the pistol icon, then click on the edit scripts for this room button. That will open the package editor up and create a new class under the map object. The class will be named Room## and the number will be the vNum the mapper uses to identify that room. That class will be enabled when you enter the room and disabled when you leave it. Anything you want to happen when you enter or leave a room can be added into the box of the Enable Script (when you enter), or Disable Script (when you leave) tabs. Any other triggers, aliases, ect. that you only want enabled in that room can be created in that rooms class just like you would any other time. Hope that helps a little more.

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

FYI, #teleport and other location-dependant commands can use the room shortname (in the Room Properties window, it's a small textbox to the right of the Room Name textbox; use %roomid() to retrieve it via script) instead of the room number. This will prevent your scripts from breaking if something ever happens to the order of the roomkeys.

Beginner Joined: 04 Jul 2011 Posts: 25

Thanks guys! I'm going to make those changes tonight and let you know the results.

Thanks again!

-Bitties

Beginner Joined: 04 Jul 2011 Posts: 25

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

go to the room you want to be recall and make sure it's selected. Choose Set Recall Location from the Actions menu in the mapper window. Make an alias or oninput trigger for the recall command and use the #RECALL command there.

Alternatively, just trigger on the recall command and use #TELEPORT.

If your game implemented GMCP, don't worry about any of the above since GMCP support in CMud will keep track of your location for you at all times (except when the vnum is purposefully not sent).

Beginner Joined: 04 Jul 2011 Posts: 25

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

You have to build a script for that one, and unless you want to specifically limit yourself to the current zone you will most definitely want to take advantage of threading. Threading is a quick and easy way to lock up CMud tightly enough to require the use of the Task Manager to kill it, so if you aren't comfortable with threading issues you should avoid threading--it's never a matter of if something will go wrong, but when.

Posted: Wed Jul 06, 2011 9:16 pm

for simple threading, just put it into an alias that starts with:
#WAIT 0
That forces it to make a thread to run it without as much chance of messing things up

Beginner Joined: 04 Jul 2011 Posts: 25

Posted: Thu Jul 07, 2011 4:08 am

Beginner Joined: 04 Jul 2011 Posts: 25

Sorcerer Joined: 15 Apr 2011 Posts: 809

If you remove the #te, the mapper's position might not update...

Beginner Joined: 04 Jul 2011 Posts: 25

Beginner Joined: 04 Jul 2011 Posts: 25

I have a separate question and hopefully this is an easy question.

I have a portal room in the mud, each portal goes to a different zone. I use #TE <zone name> to enter the zone. The only problem is the name of all the zones overlap, is there a way to fix this? I can take a screenshot if my description wasn't good enough.

Thanks!

-Bitties

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

First off, in the room properties window on the Exits tab is a textbox with the caption of Label. This is the text shown for zone links and zone links only (if it's to a room in the same zone then the text is never displayed). If left empty, the text shown is to zonename which you've already discovered can be rather inconveniently lengthy. If you fill in this field, it shows exactly what you typed.

Secondly, which room that you first fill in the label for matters. This is the room that controls the "sameness" of the zone link (in other words, editing the label from this room will automatically assign the same label text to the other side of the link). Once created, you can flip over to the other side of the zone link and change the label text so that it no longer matches what you originally typed. Make no mistake that this is in fact a bug, but the jury is still out as to whether or not it will or should become a supported feature (this will be decided when Zugg one day gets back to focusing on the mapper code).

Thirdly, if all the link labels go to the same zone but connect to different parts you can just use a space or an otherwise shorter description (ie, "ditto") for the link label. Alternatively, you could simply uncheck the Draw Link checkbox. This will make the link look like a stub exit, so you might find it useful to also turn on the Show Untested Links as Grey option in the Appearances section of Map Configuration.

Fourthly, use a legend built with text fields and set the link labels to something that doesn't overlap other labels. Keep in mind that the zone boundery calculations do NOT respect the locations or dimensions of any sort of text item set upon the map (zone link labels, room labels, or text fields.) Text fields are entirely separate from room objects, they do not scale with the zoom level, and even though you can select rooms and text together you can only move text objects or room objects.