Addon: temporary fix for "GES" - a must have for (!) tanks

[Azarael]

Guard's fixed in the next, apart from the source of the Guard damage: that still appears to be the ability and player who fired it instead of "Your Guard", and the player attacking therefore sees who is guarding.

Oh, and same-class tanks can't crossguard because the tank buff of Guard is considered identical to the guardee buff of Guard.

[Nishka]

The addon doesn't work. No shield over the guarded target, no sounds. Maybe has to do something with the current bug of no status icon for guard.

[Luth]

But you can use the chatwindow spam function " Guarding *** " until guard is fixed completely. So people know when you guard them.

[Azarael]

Yeah. At the moment Guard offers absolutely no indication of when it's active or not, so I use GES messaging for everyone's convenience.

Not that I'm going to guard anyone this patch

[zabis]

How do you edit the .lua file?

[Luth]

How do you edit the .lua file?

* open the file with a text editor like notepad++ or something

[zabis]

Thanks, Python IDLE worked

[Foxington]

Where can i download GES?

[Luth]

It's included in Tesqs addon pack: Addon Source

[Luth]

I'll wait until the next patch fix it

The next patch is fixing "it" (what?)
This addon is generally good for tanks, even with a working group ui (i guess you meant this) + working guard buffs (or this).

btw chosen aura dont work

I don't know what auras have to do with this thread and btw:

When discussing stat changes made by abilities, the client's stat window is unreliable. Not all abilites send their buff info, but the buffs may well be applied on the server. Check the combat log before reporting any buff abilities as nonfunctional.

Re: twisting and skill sticking: It's because auras are incorrectly triggering the GCD on the server's side, causing AP regen ticks to be skipped and abilities not to go through. The reason you still see the client swing is because the client plays ability start animations (as well as setting most cooldowns) immediately without even bothering to consult with the server regarding whether or not the ability use attempt was valid. This has implications for the current serverside ability range / facing handling, which may have to be made much more lenient to accomodate this strange, assumptive design. As you can tell I'm not much of a fan of it, not least because it confused me into thinking I had a solution to the melee unreliability problem -_-

I think this is the thread you are looking for.