Zugg Software :: View topic

Magician Joined: 02 Feb 2004 Posts: 364 Location: USA

I'm not sure what you're referring to.

Enchanter Joined: 10 Oct 2000 Posts: 698

Looks like a trigger intended to keep your mapper location marker in sync.

Wizard Joined: 22 Mar 2007 Posts: 2320

If this is from Version 3.xx, then this is probably not anything that you did at all. Version 3.xx uses a completely revamped mapper, and part of it is that when you move, it automatically creates a trigger matching on the expected room name to give an #OK signal, telling the mapper that you successfully moved. The trigger LocIthilion will continue to exist, or even be remade anew if it is deleted, but the pattern is changed whenever you move to match the next room you are trying to enter.

Note, since you are using version 3.xx, this really should have been posted in the Beta forum.

Wanderer Joined: 02 Sep 2005 Posts: 85

Stonewall + mr_kent: Yes, it's a mapper loc trigger, but.. how did I create it? thats what I'm asking..

Rahab: *nods* I wanna get rid of it. Cant? :( and this was a 'general' query imho.. *shrug* I'll be sure to post all beta queries in there, regardless of content.

Sorry for bumping, btw, but I've been sick lately so I didnt get a chance to get on the forums and get this resolved a while ago.

Wizard Joined: 22 Mar 2007 Posts: 2320

Why do you want to get rid of it? It is a critical part of the mapper. And this was definitely a beta query, because it is due to something new in the beta version.

The answer is, you did not create it. The mapper itself automatically creates this trigger. If you delete it, it will create a new one with the same id as soon as you try to move to another room. This is the trigger that tells the mapper that you successfully moved. Whenever you move, the mapper looks up the name of the room in that direction on the map, and changes the pattern of this trigger to match that room name. When the mud sends the room name to you, the trigger fires, and the mapper knows that you successfully moved. The mapper then disables the trigger. When you type a new movement command, the mapper enables the trigger again, and looks up the next room name.

In Zmud and Cmud up through version 2.37, the mapper did the same thing, but it kept the trigger internally and you couldn't see it. With the new revamped mapper in 3.xx, this trigger now gets created right in your package.

Wanderer Joined: 02 Sep 2005 Posts: 85

It's just for that room, I have other #OK triggers.. I dont need a double #ok for that one single room

Posted: Thu Jul 15, 2010 12:28 am

It doesn't matter. The auto-trigger created by CMUD won't interfere and will be replaced with the next room as soon as you move. There isn't any way to remove these automatic triggers. They are needed by the mapper to handle most rooms properly. Just ignore them.

Wanderer Joined: 02 Sep 2005 Posts: 85

Okay. Thanks, Zugg.