-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
smartscript waypoint_reached (40)/waypoint_ended(58) Not working properly #18938
Comments
If you add a random approach point before the last waypoint, it will work
|
This happens when there is less than 4 points. Yes, it's bizarre, and I don't know what causes this, but it happens consistently with waypoints with less than 4 points. I added a new set of actions and events that make use of the waypoint_data table, if you prefer, it shouldn't have this issue, I think. |
SMART_ACTION_MOVEMENT_PAUSE。 I see that the description timer is not implemented. I need to make the creature pause and move again. I tested it myself and creatures can only walk. Can't run. I tried set_run(59 )set_movement_speed(136) |
The movement type (run, walk) is set in the waypoint_data itself, under the field move_type. It'll run if it has move_type equal to 1. Try this:
|
Current Behaviour
"waypoint_reached (40)/waypoint_ended(58)" in Smat Script uses "wp_pause(54)" in the last waypoint-1 to always trigger an event when the last waypoint has not yet arrived
Expected Blizzlike Behaviour
In any case, the event should always be triggered when the location is reached or when the waypoint is completed
Source
No response
Steps to reproduce the problem
Extra Notes
No response
AC rev. hash/commit
f8e584a
Operating system
windows 10
Custom changes or Modules
No response
The text was updated successfully, but these errors were encountered: