Will look into the slow reaction time. Did not notice it yet, but will keep testing. If you can give a spin to the update i'll be uploading soon, it may already be fixed. Regarding the Config, well, i don't discard the option to add it later, but as i said i'll have to do it manually since i don't have Visual Studio and hate it And since i never coded C# before this CC, manual UI writing may be a little tricky yet Thank you for testing it (oh and btw, your profiles are amazing).
You already can, but only by manually editing the settings file which is located on a folder named Config inside the CC's folder. At this moment i cannot provide a config window, but will probably add it in a future release. If you have trouble editing the file PM me and I'll do it for you
Thank you very much for your comments, but now if you allow, let me clarify. First, yeah, i know you should keep up always a stack of Lifebloom on the tank, what i tried to say was that in order for me to cut on the overhealing and to make the bot stop healing when there's actually nothing to heal i have to tell him when and how to stop. If you think about it, a good way you know when to stop healing is if everyone is at 100% HP. The CC does the same, but in practice sometimes will happen that we have a full stack of LB on the tank and the healing it provides is more than enough to counteract the damage he is taking, and this will make the CC not even try to refresh the stack, why? Well, because the tank is at 100%. I hope you can see what i'm trying to explain here. I understand what you're saying, and it is true, we gain more mana from LB than we expend casting it. But if you think about it (and please try the new version) if everyone is at full health you are not casting, and so you'll either be regaining mana or you are already at full mana. Regarding the other comment, the CC will check if the tank has LB on him, and if it does, he simply casts LB on him until it reaches the stack size defined on the settings file (which is 3 by default). When i said it does not care, i meant it does not check where the LB that is on the tank came from, it just knows that it is there and needs to be refreshed. And one more think, at this moment the CC only supports one Tank. It is constantly rechecked to make sure if the tank leaves the party and we get a new one, the CC knows exactly who the tank is. If none is found, then we will be the temporary tank (which means the LB stack goes to us). And the Tank (or Main Tank if you will) to the CC will be the Tank with the most Maximum Health, which also means it may not be the Main Tank set on the Raid. In order to make the CC support multiple tanks it would need to suffer a lot of adjustments... And that is not the main goal for now When you have the chance please try out the updated version, and see if you feel it still needs improving on that aspect. Thank you very much once more for your contribution.
Have it define 1 tank thru lazy rider then have it pull another tank from your focus if you require it to have two tanks
Thanks for the suggestion, but the problem is not knowing who are the tanks, the problem would then be how to coordinate both healings. But for now, let's stick with one Tank, there are more healers on the Raid, we don't want to be doing all the hard work now, will we? Maybe on the future if people like the way the CC is handling itself i may upgrade it to support multiple tanks. We'll see
The best idea I can think of is, have an .IF InCombat , one thing i noticed is that it was consistantley doing lifebloom but, would only do 2 application, and it was dropping. That being said i thought it was a pretty good CC, with a few updates in the future i think you have a pretty good chance of being loved on these forums.
Thank you for your suggestion, i'll look into it, but first i would like some people to test the new version and have some feedback about it, to see if it already addresses most of the concerns here expressed.
Really?! Damn, on mine it does, well, not the entire instance, but the entire fight. Have to have a closer look and do a few more tests. Thank you very much for your comment.
you sir are amazing, good work!!!!!! best resto cc ive used, and i think ive tried them all. i cant figure out how to edit this thing myself tho.. i need one better for feral and moonkin
I think there's a bug in v1.01's TCRestoDruid.cs file. I had to change line 337 to: if (CanCast(NOURISH) && isAuraActive(LIFEBLOOM, target) && target.Auras[LIFEBLOOM].TimeLeft.TotalSeconds <= 5 && target.Auras[LIFEBLOOM].StackCount >= TCRestoDruidSettings.Instance.LifebloomCount && !Me.IsMoving) and 343 to: if (CanCast(LIFEBLOOM) && isAuraActive(LIFEBLOOM, target) && target.Auras[LIFEBLOOM].StackCount < TCRestoDruidSettings.Instance.LifebloomCount) Before the change, it was trying to compare LifebloomCount to TimeLeft.TotalSeconds and therefore not keeping the stack up. I'm trying it out now (after deserter wears off ) Update: Just tested, and he's keeping 3 stacks up like a PRO. Dipped below 90% mana once. It does let tank get a little low for my taste, but just cleared 3 Hour of Twilight heroics so I'm just knit-picking a bit ;-) Great CC!!!
Ok, i just reviewed the original code and well, it was correct The thing is you were making the assumption that i was comparing seconds with stack size, but i was not, let me try to explain. On the line Code: if (CanCast(NOURISH) && isAuraActive(LIFEBLOOM, target) && target.Auras[LIFEBLOOM].TimeLeft.TotalSeconds <= 5 && target.Auras[LIFEBLOOM].TimeLeft.TotalSeconds >= 3 && !Me.IsMoving) what i'm saying is basically that if the time remaining is between 5 and 3 seconds we'll refresh the Lifebloom stack with Nourish (cheaper and amazing), why this interval? Well to make sure we have enough time to cast Nourish before the stack fades. On the line Code: if (CanCast(LIFEBLOOM) && isAuraActive(LIFEBLOOM, target) && target.Auras[LIFEBLOOM].TimeLeft.TotalSeconds < 3) i just make sure to cast another Lifebloom to refresh the stack in case we did not did it with Nourish. And since there is one other line to explain, why not, at least all of them are explained here Code: if ((isAuraActive(TREE_OF_LIFE) || target.Guid == tank.Guid) && CanCast(LIFEBLOOM) && (!isAuraActive(LIFEBLOOM, target) || isAuraActive(LIFEBLOOM, target) && target.Auras[LIFEBLOOM].StackCount < TCRestoDruidSettings.Instance.LifebloomCount)) Well this is the first check the program passes through which will evaluate if the stack size on the target is less than the stack size configured on the settings then it'll keep casting on the same target (tank unless we're on Tree of Life form). So in short the line 331 ensures that the target will have 3 stacks of Lifebloom (if 3 is the number on the settings), when the target already has 3 stacks it'll check if it needs to be refreshed an we are in time to do it with Nourish, that is made on line 337 and finally if we are a bit late on the refresh (there are only less than 3 seconds left) we have to cast an instance (more expensive) Lifebloom so we keep the stack up. Hope i was able to explain what i did. The changes you made work (sometimes) but it may come a time where you'll notice it casting Lifebloom where is simply no need for it. I'll upload a new version now with a few minor tweaks and hopefully will do the trick for you guys. It works pretty much flawlessly on mine.
Thank you very much. As for the feral one, I've been using (very successfully) the one from Handnavi, ILoveAnimals it works great for Bear and Cat. As regarding moonkin, well, i found none good, maybe i'll do one sometime.
Thanks for the explanation! I'll switch back and check my log in a cheesy instance so I don't risk wiping my group But, I think you are right. I'm just curious why my performance seems better right now. It could be I'm just imagining it or the better gear I've collected!! Thanks again for taking a look. This CC is great
Managed to find what was making it sometimes not keep the stack. It is now fixed. Now it'll keep the stack all the time. Not sure if i should make it keep it only on combat or all the time as it is now. What do you guys think? In a Raid/Instance setting, it may be good to keep it up all the time, but if we are soloing i think it'll be kinda annoying have it casting all the time. I'll wait for your feedback.
Tbh only combat is prob best, if people are in a raid and using lazy rider I'm sure they can get it to 3 stacks themselves before pull
How can we priortize a spell? Like I want to use Wild Growth and Swiftmend, how should I change the setting?? I tried to change the numbers around but it doesnt seem to do what I want Like I am just comparing my heal done with other druids, they are heavy on wild growth, effroecnese from swiftmend and rejuv, while mine is wild growth, healing touch and lifeboom....
