Egis should be auto attacking anything that aggros you by default, unless you change their stance. Unless mines glitched this whole time? XD and For some reason Chocobo companions won't do this until u actually do an action on the monster.
Printable View
Got what you mean now.
Well, I guess mine is glitched sometimes. Because I've noticed it on other encounters too. That was just the most recent specific example I could think of. Sometimes it just won't attack while on 'obey' unless I command it to again. Not entirely sure why. Sometimes it appears to be after phase changes? Maybe?
I recall this happening once or twice during t9 golems too... Maybe sometimes it's after I command it to attack a specific target, and I switch targets while leaving my pet on the previous target. After that previous target dies perhaps it fails to switch targets on its own sometimes. And then just sits there like it is on steady even though it is 100% on obey. If that makes sense.
I can confirm that Enkindle is a little buggy. It takes quite a while for the Egi to finally use it and sometimes it'll just use up the timer and and not even go off. It's pretty craycray.
Contagion is working for me, but Enkindle is till using up the ability and not doing anything from time to time, even if no other command has been given for more than 5 seconds. Has anyone tried if straight out using Aerial Blast, for example, instead of going through Enkindle helps? At least when Contagion doesn't register you get to smash it until it finally does. If the egi skips Enkindle there goes your 5 minute cooldown.
Actually I am still having problems with contagion. It is still not as consistent as it was before the patch. I used to be able to fire and forget. Now, sometimes this works, but most times I have to spam the contagion button. Enkindle is still iffy also. It may be better but can not be considered fixed.
I'm pretty sure that Enkindle has always been this way. I've had this happen to me if I use Enkindle at the wrong time since 2.0 hit.
I have only ever seen it happen with Garuda so I'm pretty sure it is related to the cast time of Wind Blade (much like all of the issues just after 2.3).