Pygar
EQ2Bot Specialist
I've updated this script on the SVN.
I ask that folks give it a whirl on your healer classes.
It is designed to optionally be run with eq2bot.
This script is the eventual replacement to all current eq2bot curing routines. The way eq2bot currently works is every so often (depending on class script) the bot scans the group for needed cures and process the data.
A while back Amadeus added triggers to ISXEQ2 for afflictions. These triggers fire almost immediately each time you, a group member, or a raid member is afflicted.
The benefit to switching to the trigger based cures is the bot can immediately react to these conditions and address them appropriately rather than waiting 1-10s for it to finish its current functions then scan cures and react.
My plan is to eventually integrate this cure thread to eq2bot and allow you to set several priority settings to govern it like:
1 - How often to scan for triggered events (100ms - 5000ms). This allows you to configure the 'reaction time' to triggered cures.
2 - Interupt any cast to address cures?
3 - Interupt only non-heals to address cures
4 - Only run if current KillTarget is epic
I think most of our community will recognize why and how this new method of cure reactions is superior. The main reason for the additional options, is if you have multiple bot healers in your group/raid you may only want one hypersensitive to cures, and the other more 'heal' focused.
Please test this out, as currently it is optional and not integrated into EQ2Bot for a testing / trial period. Once I feel it is solid enough it will be directly integrated. Test now, or suffer later.
I ask that folks give it a whirl on your healer classes.
It is designed to optionally be run with eq2bot.
This script is the eventual replacement to all current eq2bot curing routines. The way eq2bot currently works is every so often (depending on class script) the bot scans the group for needed cures and process the data.
A while back Amadeus added triggers to ISXEQ2 for afflictions. These triggers fire almost immediately each time you, a group member, or a raid member is afflicted.
The benefit to switching to the trigger based cures is the bot can immediately react to these conditions and address them appropriately rather than waiting 1-10s for it to finish its current functions then scan cures and react.
My plan is to eventually integrate this cure thread to eq2bot and allow you to set several priority settings to govern it like:
1 - How often to scan for triggered events (100ms - 5000ms). This allows you to configure the 'reaction time' to triggered cures.
2 - Interupt any cast to address cures?
3 - Interupt only non-heals to address cures
4 - Only run if current KillTarget is epic
I think most of our community will recognize why and how this new method of cure reactions is superior. The main reason for the additional options, is if you have multiple bot healers in your group/raid you may only want one hypersensitive to cures, and the other more 'heal' focused.
Please test this out, as currently it is optional and not integrated into EQ2Bot for a testing / trial period. Once I feel it is solid enough it will be directly integrated. Test now, or suffer later.
