Tuanha Paladin Holy PvP

It's included in 3.4.

Download at page #1.

 

so now it wont judgment anymore going to test it

 

with this

public bool DoNotJudgement = false; //Set to true if you want to use with Judgement

it wont judgment right?

 

it stil uses judgment

 

its working i needed to put it on true P now is the cc awsome u dont need to change anything anymore with dispelling on true i save quite few mana and it only dispels whats needed

 

now i can select a tartget to heal its awsome m8 dont change anything

 

Isn't it better to set it slightly above ur normal latency?​

 

I also tested the CC(3.3) today. It was awesome. Very fast and no thinking-pauses in between(even with 40 people around in AV). Just chaincasting the best spell for each situation(LazyRaider was at 60 tps). Great work.

Out of curiosity I reflected my way through all properties of the objects that

Code:

ObjectManager.GetObjectsOfType<WoWUnit>(true, true)

returns. I wanted information about what property takes how long to access. I used reflection, so the values are probably not 100% accurate, but they give a rough impression about whats going on.

Taken in the starting zone of AV with 39 other players around. These are average values, measured in Milliseconds and sorted from fastest to slowest.

View attachment PropertyAccessTimes.txt

Just thought you might be interessted.

 

a question about this

- WILL NOT work on PvE or use PvE talent (Light of Dawn, Hand of Salvation...)

wil it also use holy radiance on aoe heals if i respec pve ?

 

No, I've removed the Holy Radiance code from the CC already.

This CC is intended to build for SPEED PvP heal only, it will not work on PvE.

 

ok hey the rebuke casting went alot slower a shaman fake casted me a few times on 3.4 thats only thing so ultimate healer is good for pve?

 

It's not slower, in 3.4 you can set delay until rebuke. If you want to interrupt immediately, just change this:

 

what is the best way to set it so you never get fake casted? ok that one is better

 

This is really what i hope for.

Look at the PropertyAccessTimes.txt, InLineOfSpellSight is very slow (that why i only check InLineOfSight) but Name also take a lot of processing time. I'm thinking about delete name output in logging.write for FASTER CC

Thank again cazma12

 

To be honest... i think its enough.
There is alot more room for improvements - but you would not notice one of them....

You could reduce the usage of .Cooldown - because its "slow".
Instead of checking for a Cooldown each tick you could check it once and add a intern Timer for it...

But: Who cares if this CC needs 20 or 22ms to tick?

I guess you wont notice it. If it runs smooth and fast - the next step would be too fast

 

You're welcome.

You could just output the Guid, or retrieve the name only once and store it in a Dictionary<Guid,string>. But be sure to clear that Dictionary sometimes(i.e. zoning), or it will contain every unit you have ever seen since the start of the CC, which, at some point, will definitely be slow.

Interrupting:

For casts:
InterruptTime = TimeWhenSpellCastEnds - YourLag - x
But don't kick too soon on very short casts, as it's inhuman.

For channels:
InterruptTime = TimeWhenSpellChannelingStarted + SomeHumanReactionTime

I've used this on my shaman with a selfwritten CombatHelper(not HB), and I can really only recall one time I got fakecasted. If you kick later they will waste more time waiting for a spell to come through that won't. I've also noticed that quite a few of them are confused about if their cast went through or not, which will also give you time. From my experience most people fakecast 45%-70% into the cast on standard 1.5-2 second casts. Better players test you out and adapt to your interrupting-style.


Performance:

I think it's always good to strive for better performance, as long as it doesn't make your code unreadable or unmaintainable, which it shouldn't if you structure it well. Let's say you maintain and extend this CC for quite a long time, wouldn't it be great if you could build up on a high-performance base, because probably most of the coming changes(logic-wise) will slow the CC down. Maybe 2ms won't matter right now, but who knows if they won't matter sometimes. Maybe I'm a little extreme in that way, but experience has shown me that you will have a bad time reading/changing/extending code that was coded with quick results in mind.

Apart from that I think it's also a great learning experience for anyone interessted in that topic. Think about what awesome CCs could be built by tuanha (or anybody else using parts of the code) in the future.

No offense, just my 2 cents.

 

[23:33:18:063] Could not compile CC from C:\Users\vibe\Desktop\HB\CustomClasses\TuanHA BT Paladin Helpers.3.4.cs!

Log:

View attachment 28-07-2012_23_33 5436 Log.txt

 

You need to make a sub folder inside your CustomClasss folder and unzip 2 files there.

2. Make new folder HonorBuddy\CustomClasses\TuanHA BT Paladin
3. Download attached file, unzip to that folder (delete old file to avoid conflict).

 

This is ridiculous (in a good way). My pally has consistently been #1 in every BG I've healed in. Just came out of a WSG with 7 mil heals in heals -- my non-botting record is only 5 and a half mil. I feel a little outdone...

 

i know m8 my own heals are so bad this cc rocks i couldnt heal without it atleast we only have to do the crowd control self this cc rocks with healing.