Zugg Software :: View topic

Apprentice Joined: 12 Apr 2004 Posts: 134 Location: USA

I have been combating movement errors for a long time now, and I am starting to get a bit frustrated; I need some help.

1. When I double click a room on the map some time the path generated by cmud works perfectly, sometimes it spits the whole path out as a string.
2. When I #walk to a room that is more then one zone link away I get the same error as above.
3. When I try to #slow a recorded path from a room trigger it will only spit out one step, then the path is gone from the queue.
4. When I use an alias to call a #walk to a room more the one map zone away, I get the same error as in 1 and 2.

I have tried to uninstall cmud, and reinstall, uninstall the English directions lib, and reinstall, and delete my map and make a new one, but the results are always the same. I don't know what else to do. With the exception of errors 1 and 4 I can get the error to happen almost with out fail. As an example here is an output of the alias calling a #walk command failing, then working back to back. When I issued the command the first time I was more then one zone away, by that I mean according to the map I was in a zone that was in a zone, in other words I have outer zone that holds entrances to many other zones, then inside of one of those zones is an entrance to another zone, I was in that zone.
Big Map->Parent zone->Child zone

Wizard Joined: 22 Mar 2007 Posts: 2320

What version of Cmud are you using? That is always important, and especially important because of the huge differences in the mapper between v2.37 and v3.31.

You apparently have some room triggers, and other triggers trying to play with the directon queue. Can you post the XML code for those triggers?

Apprentice Joined: 12 Apr 2004 Posts: 134 Location: USA

I am using v 3.31

So there is only one room trigger, there is a lock surrounding the ability for the trigger to fire normally (used to prevent never ending loops), but I have removed it for this example.

<class name="Room308" keyword="Room308" id="205">
<onenable>#slow circle
#pause</onenable>
</class>

Wizard Joined: 22 Mar 2007 Posts: 2320

You have another room trigger in room 339. It looks to me like that trigger is firing just when you say things start going bad. What is that trigger? Also, what are the two triggers that are firing at the beginning of your second quotation?

Apprentice Joined: 12 Apr 2004 Posts: 134 Location: USA

Sorry for the delayed response, I was out of town this weekend for my birthday.The room trigger in 339 looks at the value of a quest timer, if that value is ! the command to complete the quest is issued. As far as I can tell this trigger has never affected the stability of the pathing system. Things go bad before that in the first code block things go wrong in that instance when I issue the command rekle from a room that is in a zone, that is inside another zone. rekle is an alias that is only the command #walk 339. The rekle command causes the goofy results every single time use it in a zone within another zone, I can post a longer debug session if you like, but before the command is issued nothing happened, I was in a random room. Notice that on the second line I issue the command, and it parses "travel home" my portal command, then 2en. I then move to my recall room 305.

Then the command 2en is issued to the mud which is some sort of command for dating people. Then I issue the same rekle command again, and it correctly walks e e n

Later in that same session the #walk command fails again. Had it not failed from the first command its likely it would not have failed in the second case.

It has occurred to me that the alias is bad, but I have tested it with typing out the command #walk 339 under the same circumstances, and the results are the same.

Apprentice Joined: 12 Apr 2004 Posts: 134 Location: USA

Script Debug >< This is the main instance where everything fails. This zone is entered through another zone. I issued the command l to look, then move one south, then attempt to move to the questors room, this time without the assistance of the macro.

Wizard Joined: 22 Mar 2007 Posts: 2320

It looks to me like the problem is consistently happening when you execute the 'travel' command. Is that correct? Can you post the code for travel?

Apprentice Joined: 12 Apr 2004 Posts: 134 Location: USA

So the key word "travel" is a portal command, so "travel klevnone" will travel to room 394. In the mud these portals are set up all over the place. So other then there being a portal in 394 with the value of "travel klevnon" in the map, there is no code.

Its a lot like a recall, in fact recall is another command that will trigger the problem; for a while I made the travel cost of my recall room 10000, so that I would never recall when the path distances were calculated.