Waiting out Rezsick is a CC thing?

[chinajade]

In this post, Apoc wrote...

We intentionally did not add this into the core. CCs should be responsible for handling this [Editor: "this" means "waiting for the RezSick to time out"] (certain classes can still grind with res sickness, others can't). If the default CCs aren't handling this, then it's a valid issue.

(By the way, we thank Apoc for providing such information to the community!)

First, this is not a flame. My primary interest is in keeping the development team focused on productive tasks, and away from whiney users.

The Problem
I've already bumped into the "my CCs don't wait for rezsick debuff" problem and had to turn off HB's "Spirit Rez" feature. My guess is that my reaction will be typical of the user community. The result is that the development team will have wasted a lot of effort on something that nobody will be using.

I think is going to cause the HB developers no end of questions and whining in the forums when people try to use it. It basically means we can't use the new feature unless the CC supports it.


A Better Solution?
Using the principle of symmetry, whatever software area is responsible for accepting the spirit res should be the one responsible for dealing with its consequences. If the CC accepted the spirit res, then fine, it can deal with it. If the HBcore did, then IMHO, its the HBcore responsible for dealing with it.

Could the HBcore not provide a default method in whatever class that CC's derive from, and arrange for the HBcore to ask the CC if its capable of proceeding with RezSick? The default answer would be 'no'. Given this answer, the HB core would wait for the debuff to expire before transferring control to whatever should happen normally. If the CC overrides the method then says 'sure, I can fight with rezsick', then the HB core could transfer control immediately.

What this does for the community and the developers--both HBcore and CC:

• No CCs need to be altered and the right thing will be done
• CCs that can handle it will take advantage of every second of botting time
• And most importantly...
  It prevents a ton of questions in the forums, and faulty bug reports, and general moaning

I honestly believe that a little more time thinking about this problem will head off a lot of trouble down the road with the user base. As it is, its a feature I won't be using because my CC's don't support it.

Just my $0.02, and thanks for listening,
CJ

 

[Apoc]

Here's our reasoning behind why we didn't make the core wait out the res sickness:

• Certain classes can still kill stuff perfectly fine even with res-sickness. (Wars, rogues, Pallys, certain Priest/Mage specs, etc) - If we forced it to wait, then those CCs would be out 10mins of botting time. A waste if you ask me.
• Having the CC wait for res sickness is (literally) 4 lines of code added to the CC. Any CC author (or non-author) is more than welcome to PM me for the code required. Hell; I'll even make the required changes for you!
• By us not handling res-sickness, this allows more freedom for plugin/CC developers to do things while waiting on res-sickness to go away. (E.g.; forcing a repair run, or casting some stuff you normally wouldn't due to mana constraints, etc)
• We simply could not find a valid reason as to why the core itself should force the bot to wait while in res-sickness. This is especially true for the possibility of gaining combat while sitting on our ass at the spirit healer. (If we've got it in a forced-wait, the CC will never pick up on the combat, assuming we don't force it to combat)

The list goes on, but those are the 'big' reasons.

Also, we won't be providing an extra function in CCs, mainly due to the fact that some people would force the bot to wait in Rest, others may want it to wait in CombatBuffs. It's entirely up to the CC author as to where they make it wait (if at all). We're trying not to impose any more limitations than there already are.

One thing for me (note: ME. Not the rest of the HB devs), is that making the CC authors responsible, makes sure that the authors actually pay attention to what they're doing, and not just tossing out a bunch of copy/pasted code in hopes that it will work. Crappy combat makes the entire bot look bad. Little by little we make it just a bit harder for people with *very* little knowledge to create good CCs. Granted; if you spend more than 6hrs working with C#, it's still incredibly easy.