Question - Bard using Fading Memories when not in danger

[Kibeth]

Currently using bard to pull for my team. I do have Use Combat Escape enabled, as there are times when my bard can pull aggro from mage pet when bellow and a few DoT crits hit all at once, but the situations when the bard is currently using Fading Memories seems inconsistent or maybe unintended.

There are times when the bard has to get fairly close due to small hallways or LoS issues and gets hit, then will Fade and return to camp. This is behavior I would expect completely, no concern.

There are other times when just running back to camp or standing in camp waiting for the mob being pulled to arrive that the bard will decide to Fade. Bard is at full hp, bard is not within melee range or near the mob being pulled, then realizes there is now nothing in the xtar window and goes back out to pull again, often times the same mob it had just been pulling. If this happened every time the bard went to pull, I could understand okay just disable combat escape and manually fade in combat if needed, but the bard will pull fine for 10-15 minutes and then suddenly do this for 5-10 pulls, and then go back to normal for another extended period.

I did set the log to Verbose and tried to understand what is triggering the call to fade. I tried searching for Emergency, which simply states "Run Rotation Emergency" without referencing the criteria met to trigger this, i tried searching for Fading Memories which then just outlines the calls to check if its available and to use the AA, but again does not reference the criteria being met to trigger it being used. If there is a more appropriate term to use to search for it may help me have a better understanding if I can do something to prevent this behavior.

 

[Algar]

Bard should not be using Fade if he is assigned as the group puller (meaning, we have code to prevent this).
We are likely changing your roles and that is why it seems random to you.

You should disable that fade to pull with bard, or customize your class config to adjust those conditions yourself.

[CODE lang="Lua" title="Bard Fade Check"]UnwantedAggroCheck = function(self)
if Targeting.GetXTHaterCount() == 0 or Core.IAmMA() or mq.TLO.Group.Puller.ID() == mq.TLO.Me.ID() then return false end
return Targeting.IHaveAggro(100)
end,[/CODE]
Targeting.IHaveAggro is a helper function that checks your target and your xtargets for aggro greater or equal than the supplied percent (in this case, 100).

Coding around this is possible, and may perhaps be supported in the future, but my initial adjustment would be to simply disable it entirely if you have a mercs pull-mode active.

I did set the log to Verbose and tried to understand what is triggering the call to fade.

Good on you for that, but we dont' spell out every condition in our logging, you'll have to examine the code :3

 

[Kibeth]

It never even crossed my mind to assign the puller group role, I simply assumed since i had "start pulls" active that it would take that into consideration. You know what they say about assumptions!

This makes a lot more sense, with the puller group role assigned bard is acting more as expected.

 

[Algar]

It never even crossed my mind to assign the puller group role, I simply assumed since i had "start pulls" active that it would take that into consideration. You know what they say about assumptions!

This makes a lot more sense, with the puller group role assigned bard is acting more as expected.

I honestly thought that we should be assigning that role for you. maybe my memory isn't as good as I thought XD

I realize this setup may not support every situation but it *is* what stops bards from getting hammered due to song aggro when someone else is pulling.

 

[Kibeth]

Its because my group leader is not running RGMercs but one of the CWTN/Sic modules, so whatever signals are being sent to automate this aspect are being missed. I typically avoid assigning the puller group role due to all the issues it causes with the actual in game mercs, but this character doesn't even use one so it wouldnt actually be an issue anyway.

edit: forgot to actually say thank you!