Xassist not Clearing Targets on Mob Reset MqNext Version

[Redbot]

In GitLab by @morisato38 on Nov 2, 2021, 11:44

[Redbot]

In GitLab by @morisato38 on Nov 2, 2021, 11:46

Using mqnext Xassist is not Clearing targets on Mob reset this does not always Happen But after a while it begins to occur and then a unload reload of the plugin seems to clear the issue there is No Specific Error or Event tied to it other than, targets Getting stuck and this Messes Up Enchanters/ Pullers in Rgmercs alot.

[Redbot]

In GitLab by @Knightly1 on Nov 2, 2021, 12:44

What is meant by "Mob Reset"?

[Redbot]

In GitLab by @morisato38 on Nov 2, 2021, 16:16

When Pulling a mob sometimes they get Stuck and then drop aggro and reset to Spawn point But Even though they are No Longer aggressive or tagged Xassist Is leaving them on Xtar.

[Redbot]

In GitLab by @jessebevil on Dec 27, 2021, 14:25

Once you strike a mob AssistName is populated on a Xassist "assisting" toon because the assister struck the spawn and therefore populates "AssistName" which is what is used to determine what XAssist should add to your XTarget window. That "AssistName" will remain there until another spawn is struck/engaged. With that said, it means this is the expected result of pulling a mob that then gets too far away and drops aggro as it's still populated as that pSpawn->AssistName

I don't believe there is a way to fix this that doesn't involve making assumptions to work around the issue. If the assist toon is also the puller, then it wouldn't be on their XTarget's and they should resume pulling, which would update their "AssistName" target. As it stands the plugin will just add the new one, leaving the old one on there.

I did have a version that would remove the previous spawn from XTarget and replace it with the new one. Which, if you release that slot back to EQ and the mob did in fact have aggro on you it would automatically repopulate itself. I tested this in the guild hall where they don't retain aggro after engaged. I could switch between 3 dummies and maintain only one added XTarget from XAssist. Then again using the same version I went hunting and repeated the process. If I had aggro and cleared the manually created one by XAssist, EQ would repopulate it because the spawn did in fact have aggro.

So with the above said, there is a potential work around, but it changes the functionality of the plugin in that it doesn't keep stuff on your XTarget if the Assist spawn engages a new target.

[Redbot]

In GitLab by @morisato38 on Dec 29, 2021, 09:48

If it would be possible to make it auto refresh The slot every like 60 in that slot it would be useful, if the mob was still aggressive and OTW it would repopulate if it was not it would drop aggro and allow u to move on.?

[Redbot]

In GitLab by @jessebevil on Dec 29, 2021, 11:32

Well that doesn't really fit in with the way AssistName/Plugin works. You could certainly have your macro do the above I'd imagine, but I feel that could have a 'breaking' effect on other potential users of the plugin.

[Redbot]

In GitLab by @morisato38 on Dec 29, 2021, 15:48

Possible to put in a reset command for a macro to trigger?

...

On Wed., Dec. 29, 2021, 12:32 p.m. Jesse B (@jessebevil), < gitlab@mg.gitlab.com> wrote:

Jesse B https://gitlab.com/ChatWithThisName commented
https://gitlab.com/redguides/plugins/MQ2XAssist/-/issues/1#note_797699167:

Well that doesn't really fit in with the way AssistName/Plugin works. You
could certainly have your macro do the above I'd imagine, but I feel that
could have a 'breaking' effect on other potential users of the plugin.

—
Reply to this email directly or view it on GitLab
https://gitlab.com/redguides/plugins/MQ2XAssist/-/issues/1#note_797699167.

You're receiving this email because of your account on gitlab.com. If
you'd like to receive fewer emails, you can unsubscribe
https://gitlab.com/-/sent_notifications/REDACTED/unsubscribe
from this thread or adjust your notification settings.

[Redbot]

In GitLab by @jessebevil on Dec 29, 2021, 16:38

I don't think that would be unreasonable. /xtarget reset auto would reset them all to auto?

[Redbot]

In GitLab by @Knightly1 on Dec 29, 2021, 17:37

You can just /xtarget remove for that with the built-in EQ command.

[Redbot]

In GitLab by @towbes on Nov 29, 2022, 24:54

Sorry for the necro bump, but the behavior I'm experiencing an issue similar to this. /xtarget remove , and /xtarget auto on are not resolving the issue above, however I am able to right click the xtarget window and click auto and the target goes away.

Note this is with EMU build and ROF2 client. Way I was able to reproduce:

1. In a raid with 8 chars standing near Aaryonar spawn spot in VP (no macro running at the time)
2. Run char over to Feshlak who is rooted, aggro him then run the char back
3. Whole raid has Feshlak in Xtarget
4. Used commands /xtarget auto on , /xtarget remove but Feshlak stays on xtarget
5. Right click Feshlak in xtarget window -> Click Auto - Xtarget window is cleared

It seems that step 5 is what the /xtarget auto on command should be doing? Or would that be the functionality required with the /xtarget reset auto command?

Would also like to note that when this happens and use the steps above, the target does not automatically go back onto the top auto hater slot. I had to manually target it and right click add current target. (Probably could have used /xtarget add as well). Once I killed Feshlak and pulled next mob, everything works as expected and mob goes straight to slot 1 on the xtarget window.