 |
jonhutch01
Beginner
Joined: 21 Dec 2009
Posts: 12
Location: Chattanooga, TN
|
 Posted: Thu Dec 31, 2009 4:42 pm
IRE Speedwalk Slow down
|
I'm playing on an IRE game and I've just got the mapping down but I can't seem to speedwalk it. They only allow a certain amount of movement in a given time frame. I know it zMUD you could set the time between movement commands but I don't see an option like this in cMUD. Can someone point me to it if it exists or if it does not, help me figure out how to slow it down so I can use the speed walk feature? Thanks!
|
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Thu Dec 31, 2009 6:17 pm
|
Technically, in Zmud you only get to set the time between ALL commands, not just movement commands. This hasn't changed in CMud, and is found under General Scripting Preferences.
|
|
_________________
EDIT: I didn't like my old signature |
 |
|
|
jonhutch01
Beginner
Joined: 21 Dec 2009
Posts: 12
Location: Chattanooga, TN
|
Posted: Thu Dec 31, 2009 6:18 pm
|
| MattLofton wrote: |
| Technically, in Zmud you only get to set the time between ALL commands, not just movement commands. This hasn't changed in CMud, and is found under General Scripting Preferences. |
Good to know. Anyway to do this just on a speedwalking basis? |
|
|
|
|
gamma_ray
Magician
Joined: 17 Apr 2005
Posts: 496
|
Posted: Thu Dec 31, 2009 6:35 pm
|
| Code: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger priority="750" case="true" verbatim="true" copy="yes">
<pattern>You cannot move that fast, slow down!</pattern>
<value>#nodir
#stop
#step</value>
</trigger>
</cmud> |
And the scripting preferences doesn't apply to all commands, just those sent with #send or speedwalking. If you're not using #send (or not using it heavily) I wouldn't worry. |
|
Last edited by gamma_ray on Thu Dec 31, 2009 8:36 pm; edited 1 time in total |
|
|
|
jonhutch01
Beginner
Joined: 21 Dec 2009
Posts: 12
Location: Chattanooga, TN
|
Posted: Thu Dec 31, 2009 6:46 pm
|
| gamma_ray wrote: |
<?xml version="1.0" encoding="ISO-8859-1" ?>
<cmud>
<trigger priority="750" case="true" verbatim="true" copy="yes">
<pattern>You cannot move that fast, slow down!</pattern>
<value>#nodir
#stop
#step</value>
</trigger>
</cmud>
And the scripting preferences doesn't apply to all commands, just those sent with #send or speedwalking. If you're not using #send (or not using it heavily) I wouldn't worry. |
Should there be a #wait or #alarm somewhere up in there? Other wise it makes the speedwalking abort. |
|
|
|
|
gamma_ray
Magician
Joined: 17 Apr 2005
Posts: 496
|
Posted: Thu Dec 31, 2009 8:41 pm
|
Whoops, forgot code tags, fixed my post so you can actually read it now.
And no, it doesn't need wait or alarm or anything. It works perfectly just like that, I should know, I use it. |
|
|
|
|
jonhutch01
Beginner
Joined: 21 Dec 2009
Posts: 12
Location: Chattanooga, TN
|
Posted: Thu Dec 31, 2009 8:45 pm
|
| gamma_ray wrote: |
Whoops, forgot code tags, fixed my post so you can actually read it now.
And no, it doesn't need wait or alarm or anything. It works perfectly just like that, I should know, I use it. |
Are there any settings I should have set?
Edit: Sorry, I say this because it doesn't seem to be working. Granted the trigger pattern is different ("Now now, don't be so hasty!") but replacing it should be all that's needed for it to work right? Am I missing something?
Edit2: I went ahead and turned up my time between commands. That seems to have fixed it for now. Thanks |
|
|
|
|
gamma_ray
Magician
Joined: 17 Apr 2005
Posts: 496
|
Posted: Thu Dec 31, 2009 11:12 pm
|
How wasn't it working? Getting a speedwalk aborted message is normal, #stop...stops speedwalking (giving you the message), but then #step starts again so nothing shocking there.
I do have a delay between commands, but it's fairly low so I still hit the delay message on long walks when my connection is good. |
|
|
|
|
Chris_3413
Novice
Joined: 22 Mar 2004
Posts: 46
Location: Australia
|
Posted: Mon Jan 11, 2010 1:49 pm
|
Perhaps what he's after is the step delay found in the mapper configuration, just set it to something reasonable thats not too fast that you get the hasty messages
|
|
_________________
What do you mean, Fatal Error! |
|
|
|
|
|
|
