04-30-2014, 04:19 PM
question - heal priorities in high damage scenarios such as brayflox hm seem to be lacking. U have to hand heal basically lest you risk death every pull. (Referring to speed runs but I wonder if in raid scenario it would risk the same)
What I mean is instead of focusing on keeping the tank up it will Esuna him or regen him or regen another party member or heal another party member even and by the time the next heal fires - the tank is down.
I know this is partially due to game design as those decisions are what seperate a good player from the opposite. Still I would like to think we can tune the bot to make the proper choice most of the time.
I haven't looked but is it possible to move most of the Esuna to after cures? Or only if hp is > xxx amount? I noticed you have some bundled together and id hate to move essential esunas such as moogle ex when trying to move non essential.
As for priority, I tried setting it so anything under 85 goes tank, me, party, anyone. Unfortunately this doesn't seem to work? Does it have to be set inside skill manager on a per heal basis in order to work in assist mode?
Anyhow, are you noticing any of the aforementioned and is their any chance that you wouldn't mind paying attention to some of these areas for your next update? In most scenarios this is the most complete and ideal profile around. An excellent base to work off of as well. The only time I see issue is with priority in really high damage scenarios.
Oh, before I forget. Also seems to want to cycle between cure2 and cure1. I rarely see cure2 twice in a row. I understand why it does this, as the bot cannot predict incoming damage.. However I'm wondering if their is any way to counter it to an extent? I find my cure 2 landing but then it tosses a cure 1 and by the time it tosses cure 2 again the hp is preeeeetty low and I end up clenching my butt while mashing my cure2 hotkey lol.
Just some thoughts. Mind you this is with an ilvl 99 whm. (Oh and whm so needs a buff! Lol scholars makin me look bad QQ)
What I mean is instead of focusing on keeping the tank up it will Esuna him or regen him or regen another party member or heal another party member even and by the time the next heal fires - the tank is down.
I know this is partially due to game design as those decisions are what seperate a good player from the opposite. Still I would like to think we can tune the bot to make the proper choice most of the time.
I haven't looked but is it possible to move most of the Esuna to after cures? Or only if hp is > xxx amount? I noticed you have some bundled together and id hate to move essential esunas such as moogle ex when trying to move non essential.
As for priority, I tried setting it so anything under 85 goes tank, me, party, anyone. Unfortunately this doesn't seem to work? Does it have to be set inside skill manager on a per heal basis in order to work in assist mode?
Anyhow, are you noticing any of the aforementioned and is their any chance that you wouldn't mind paying attention to some of these areas for your next update? In most scenarios this is the most complete and ideal profile around. An excellent base to work off of as well. The only time I see issue is with priority in really high damage scenarios.
Oh, before I forget. Also seems to want to cycle between cure2 and cure1. I rarely see cure2 twice in a row. I understand why it does this, as the bot cannot predict incoming damage.. However I'm wondering if their is any way to counter it to an extent? I find my cure 2 landing but then it tosses a cure 1 and by the time it tosses cure 2 again the hp is preeeeetty low and I end up clenching my butt while mashing my cure2 hotkey lol.
Just some thoughts. Mind you this is with an ilvl 99 whm. (Oh and whm so needs a buff! Lol scholars makin me look bad QQ)