Stacking Buffs

[Nebbeny]

Just curious if anyone knows which, if any, warden and fury buffs (conc) dont stack.  Or alternativly which ones are sensible to let one cast and the other free up conc for aspect etc.  Thank you in advance for any helpful comments! <div></div>

[Especial]

<DIV>All of our group buffs stack up. But our dmg shield won't stack with theirs. Our Spikeshield or whatever it's called now (t7) won't stack with theirs, but ours usually hits for a higher amount than theirs, if they're the same tier (i.e. adept I, Master I, etc). Also, our regens won't stack which is still just a stupid stupid stupid idea that SOE seems to think is ok. Our group regen and their single target regen (or vise-versa) WILL stack however. So thats kinda a-not-so-power friendly way to get around it. Plus group heals don't help the MT if you're not in their group for raids so...   Whoever thought making our regens non-stackable must've been hungover--or some angry Templar that was mad cause they couldn't solo heal encounters like the uber Wardens could =) hehe  Stupid clerics...</DIV> <DIV> </DIV> <DIV> </DIV> <DIV>Samui</DIV> <DIV>70 Warden/70 Sage</DIV> <DIV>Oasis</DIV>

[Rappy]

If the group buff of similar line shares a component with another healer buff (such as HP or mitigation) then that buff will not stack.Example - The physical mitigation buff does not stack and only one will be effective on the whole group.  The irony is this does not seem to follow the 'best' stat.  A simple example is to group with a lower level shamen than yourself and see your physical mitigation go down.   At level 70 i have had my 732 group physical mitigation master 1 buff get overwritten by a level 50 shamen adept 1 physical mitigation buff.Many effects do not stack and there does not seem to be a logic to this.  For this reason when you are grouped with another healer it is important to test clicking off and on buffs to find out which ones are overwriting.<div></div>

[Sokolov]

The shammy mitigation buff appears to have been coded in such a way that it always overwrites another mitigation buff - no matter the cast order.Us shammies suspect it is related to the way Wards work on a First In First Out basis and the fact that our mit buff has a regenerating ward - so they must've coded it so it's "always on top" only they made the mistake of making the whole spell work that way instead of just the ward component=/<div></div>