attackBeyondMaxDistance waitForAgressive: Difference between revisions
Jump to navigation
Jump to search
(Created page with "; attackBeyondMaxDistance_waitForAgressive [<boolean>] : This config setting determines how openkore behaves when a ranged character has already damaged to their target,...") |
No edit summary |
||
| Line 1: | Line 1: | ||
; attackBeyondMaxDistance_waitForAgressive [<[[boolean]]>] | ; attackBeyondMaxDistance_waitForAgressive [<[[boolean]]>] | ||
; homunculus_attackBeyondMaxDistance_waitForAgressive [<[[boolean]]>] | |||
; mercenary_attackBeyondMaxDistance_waitForAgressive [<[[boolean]]>] | |||
: This config setting determines how openkore behaves when a ranged character has already damaged to their target, but the target is currently out of range. | : This config setting determines how openkore behaves when a ranged character has already damaged to their target, but the target is currently out of range. | ||
Latest revision as of 21:04, 18 September 2022
- attackBeyondMaxDistance_waitForAgressive [<boolean>]
- homunculus_attackBeyondMaxDistance_waitForAgressive [<boolean>]
- mercenary_attackBeyondMaxDistance_waitForAgressive [<boolean>]
- This config setting determines how openkore behaves when a ranged character has already damaged to their target, but the target is currently out of range.
- If this parameter is 0 (old behavior), then openkore will move towards the monster.
- If this parameter is set to 1 (new behavior), then openkore will wait in place until the wounded monster comes closer.
- Appeared in PR#3628