homunculus noinfo dead: Difference between revisions
Jump to navigation
Jump to search
No edit summary Tag: visualeditor-switched |
No edit summary |
||
Line 2: | Line 2: | ||
; homunculus_noinfo_resting [<[[boolean]]>] | ; homunculus_noinfo_resting [<[[boolean]]>] | ||
: | : On new servers, when you log in and your Homunculus is dead or vaporized, the server sometimes doesn't send any information about the Homunculus, not even that it's dead or vaporized. This can lead to crashes and incorrect checks in OpenKore. See the issue [https://github.com/OpenKore/openkore/issues/3919 3919]. | ||
: To address this issue, the two specified block parameters were added. The config block will be triggered if the bot has no information about the homunculus's death or rest. | |||
: Example: | : Example: |
Latest revision as of 23:44, 4 October 2025
- On new servers, when you log in and your Homunculus is dead or vaporized, the server sometimes doesn't send any information about the Homunculus, not even that it's dead or vaporized. This can lead to crashes and incorrect checks in OpenKore. See the issue 3919.
- To address this issue, the two specified block parameters were added. The config block will be triggered if the bot has no information about the homunculus's death or rest.
- Example:
useSelf_skill Resurrect Homunculus { homunculus 0 homunculus_noinfo_dead 1 }
useSelf_skill Call Homunculus { homunculus 0 homunculus_noinfo_resting 1 }
- Appeared in PR#3920