fix(DB/SAI): update waypoint start events for new forcedMovement parameter (#23255)
This commit is contained in:
parent
0822bc34d7
commit
bc27115efb
1 changed files with 11 additions and 0 deletions
|
|
@ -0,0 +1,11 @@
|
|||
-- 53 WP_START
|
||||
-- update previous parameter run = 1 to forcedMovement = 2 (run)
|
||||
update `smart_scripts` set `action_param1` = 2 where `action_type` = 53 and `action_param1` = 1;
|
||||
-- update previous parameter run = 0 to forcedMovement = 1 (walk)
|
||||
update `smart_scripts` set `action_param1` = 1 where `action_type` = 53 and `action_param1` = 0;
|
||||
|
||||
-- 113 START_CLOSEST_WAYPOINT
|
||||
-- update previous parameter run = 1 to forcedMovement = 2 (run)
|
||||
update `smart_scripts` set `action_param4` = 2 where `action_type` = 113 and `action_param4` = 1;
|
||||
-- update previous parameter run = 0 to forcedMovement = 1 (walk)
|
||||
update `smart_scripts` set `action_param4` = 1 where `action_type` = 113 and `action_param4` = 0;
|
||||
Loading…
Add table
Add a link
Reference in a new issue