Zugg Software :: View topic

Wizard Joined: 17 Jun 2006 Posts: 1201

Would it be possible to create another overloaded version of your WALK method that included a time delay argument? The reason is I don't see why I should have to recreate the code in script and add a time delay between movement commands just to walk somewhere when the internal code already does the path and moving very well. The problem is with muds like IRE it walks too fast and you get the don't be so hasty message which aborts the slow walk. I made an easy map find and walk to script but can't get it to work due to the walk always being aborted.

Also, I would think that simply using Stop and Step would solve this problem upon receiving the "Don't be so hasty!" message. However, it does not or I am not understanding Stop and Step commands according to the help file. The map goes ahead and moves to the next room even upon receiving the "Don't be so hasty!" message and the trigger firing sometimes, but you don't actually move. Then when I enter Step it does nothing or only moves one room and stops. According to the help files that should be all I need?

While I understand I could do this in script, and thanks to the person who sent me a script that could accomplish it, I again don't understand why there is a need to recreate the path again in script and make a huge script just to accomplish the same exact thing that #WALK vNum does but add a delay between movements. It seems ridiculous to me.

Posted: Thu Jun 03, 2010 1:27 am

Have you tried setting the "Delay between sending lines" under the scripting options?

Wizard Joined: 17 Jun 2006 Posts: 1201

No I don't really want that do I? I don't want any delays other than when I am slow walking.

It's just a pain in the backside really.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

edit: Nevermind, the suggestion I had was a bad one.

Am still looking at the other thing.