General description:
Monitors your health and if it falls below a stipulated threshold, perform "/keypress instant_camp" or its equivalent. Setting the stipulated threshold to 0 (zero) turns off checking. Should be a very short frequency for the monitoring check.
Purpose:
To save your butt from unexpected problems when AFK.
Commands:
/saveme ###, where ### is a number between 0 and 99. A value outside that range is ignored. /saveme off might be a reasonable option as well.....more intuitive and consistent than /saveme 0.
Reason:
Macro processing is pretty dumb/straight-line, and adding this type of constant checking would be difficult at best. I can't see how this could be trapped via an event, since you really only can tell from screen messages that you are being hit, not how much aggregate damage you've taken. I don't want to camp just because I was hit once (eg. I may run out of range, or zone, or one of many other butt-saving activities). Having the checking outside a macro makes it immediately available for all macros with no re-coding or re-design.
If this kind of checking is already available in another plugin or even in basic MQ behavior, I'll take my flames in stride and go read up. If not, opinions/comments/assistance will be greatly appreciated.
Even though this seems like it would be straight-forward code, I've never written in C++, let alone my own plugin, and need to lean on y'all for guidance or assistance.
Thanks in advance.
Monitors your health and if it falls below a stipulated threshold, perform "/keypress instant_camp" or its equivalent. Setting the stipulated threshold to 0 (zero) turns off checking. Should be a very short frequency for the monitoring check.
Purpose:
To save your butt from unexpected problems when AFK.
Commands:
/saveme ###, where ### is a number between 0 and 99. A value outside that range is ignored. /saveme off might be a reasonable option as well.....more intuitive and consistent than /saveme 0.
Reason:
Macro processing is pretty dumb/straight-line, and adding this type of constant checking would be difficult at best. I can't see how this could be trapped via an event, since you really only can tell from screen messages that you are being hit, not how much aggregate damage you've taken. I don't want to camp just because I was hit once (eg. I may run out of range, or zone, or one of many other butt-saving activities). Having the checking outside a macro makes it immediately available for all macros with no re-coding or re-design.
If this kind of checking is already available in another plugin or even in basic MQ behavior, I'll take my flames in stride and go read up. If not, opinions/comments/assistance will be greatly appreciated.
Even though this seems like it would be straight-forward code, I've never written in C++, let alone my own plugin, and need to lean on y'all for guidance or assistance.
Thanks in advance.