lockMap randX: Difference between revisions
Jump to navigation
Jump to search
m (Syntax) |
m (Conversion script moved page LockMap randX to lockMap randX: Converting page titles to lowercase) |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
; lockMap_randX <[[number]]> | ; lockMap_randX <[[number]]> | ||
; lockMap_randY <[[number]]> | ; lockMap_randY <[[number]]> | ||
: If [[lockMap]], [[ | : If [[lockMap]], [[lockMap_x|lockMap_x]], and [[lockMap_y|lockMap_y]] are set, and you set these two options, Kore will stay at a random spot inside the '''lockMap''' within an area '''lockMap_randX''' distance to the left or to the right of '''lockMap_x''', and '''lockMap_randY''' distance above or below '''lockMap_y'''. | ||
== Notes == | == Notes == |
Latest revision as of 22:34, 26 April 2021
- lockMap_randX <number>
- lockMap_randY <number>
- If lockMap, lockMap_x, and lockMap_y are set, and you set these two options, Kore will stay at a random spot inside the lockMap within an area lockMap_randX distance to the left or to the right of lockMap_x, and lockMap_randY distance above or below lockMap_y.
Notes
- This is useful if you want to stay in a particular area inside the lockMap. If you are using random walk to search for monsters, these options restrict your movement within that particular area.
- If you are using tele-search, these options are entirely useless.