Extra variable for moveto and pathto quest functions
Would it be possible to have the heading added to these as well as another field that would include whether or not the mob stops and holds at those coordinates? ex: quest::moveto(x,y,z,h,stop(1/0)).
Currently, after a mob uses moveto, it returns to its start point. It requires a lot of work to get that little weasel to stop sometimes and can create a lot of extra grids. This would also allow for more scripting control than using $wp which only fires when a mob leaves a waypoint. You would be able to have say statements appear more fluid with less timer setting required. |
In this thread, Justsomeguy shows how to use quest::moveto and save the new WP after each move fairly easily:
http://www.eqemulator.net/forums/sho...329#post175329 As long as you have this in your script, it will save every WP it gets to as long as the NPC isn't already using a grid: Code:
sub EVENT_WAYPOINT { Code:
my $Destination = "None"; I do agree that the stop option should definitely be added to the moveto quest command. It would have saved me a bit of work on a script I am currently working on that has quite a bit of moving around in it. Heading probably wouldn't be a bad thing to have as an option either. I might try to look into adding these features if I get some time soon. For now, the above method works pretty well. |
I went ahead and added the 2 new options to quest::moveto. It wasn't hard to get them added using guard spots. Here is the new explanation of the command I updated in the wiki for it:
Quote:
Here is an example of a quest using all of these options: Code:
sub EVENT_SAY { |
Thanks! I found that post after I'd posted this though =/. Consequently, when I use stop, the NPC generally takes the absolute straightest route home that it could find, so I generally just used long pauses and a timer with a depop.
|
All times are GMT -4. The time now is 05:57 PM. |
Powered by vBulletin®, Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.