Difference between revisions of "lockMap x"
Jump to navigation
Jump to search
(Created page with '; lockMap_x [<x-coordinate>] ; lockMap_y [<y-coordinate>] : If lockMap is set, and these two options are set, Kore will always try to stay in the specified coordinates inside…') |
m (Syntax) |
||
| Line 1: | Line 1: | ||
| − | ; lockMap_x [ | + | ; lockMap_x <[[number]]> |
| − | ; lockMap_y [ | + | ; lockMap_y <[[number]]> |
: If [[lockMap]] is set, and these two options are set, Kore will always try to stay in the specified coordinates inside the lockMap. | : If [[lockMap]] is set, and these two options are set, Kore will always try to stay in the specified coordinates inside the lockMap. | ||
| − | + | == Notes == | |
| + | |||
* If you are using [[route_randomWalk|random walk]] to search for monsters, you have to also set [[lockMap_randX]] and [[lockMap_randY]] or these options are rather useless. | * If you are using [[route_randomWalk|random walk]] to search for monsters, you have to also set [[lockMap_randX]] and [[lockMap_randY]] or these options are rather useless. | ||
* If you are using [[teleportAuto_search|tele-search]], these options are entirely useless. | * If you are using [[teleportAuto_search|tele-search]], these options are entirely useless. | ||
[[Category:config.txt]] | [[Category:config.txt]] | ||
Revision as of 08:48, 16 August 2012
- lockMap_x <number>
- lockMap_y <number>
- If lockMap is set, and these two options are set, Kore will always try to stay in the specified coordinates inside the lockMap.
Notes
- If you are using random walk to search for monsters, you have to also set lockMap_randX and lockMap_randY or these options are rather useless.
- If you are using tele-search, these options are entirely useless.
