Problem - Tank groupwatch not working (1 Viewer)

[kett73]

So on my pally tank I have groupwatch=2|60 selected so he watches the mana of my druid healer. I also have druid set to med at 60% with medcombat=0. The tank never stops pulling for mana and then my druid will be at 0% and everyone dies. What am I doing wrong here??

P.S Using mq2nav to pull and it is non-stop. Is there anyway to make nav pause between pulls?

 

[Akatora]

just turn groupwatch=1 it will default stop at 20% see if that changes whats going on

 

[kett73]

Thats what I started with and it never worked.

 

[Akatora]

so he pulls under 20% not 20 or 21?

 

[kett73]

He never stops pulling no matter what the healers mana is at. I have seen the "my mana is at 50% medding" message, but unless I physically stop him by hitting backoff he will not stop pulling. The tank will med if his mana reaches the limit set, but not healers.

 

[ctaylor22]

Make sure everyone has groupwatch set off except your puller. The if this continues to happen, when a member of your group gets below the level where the puller should stop pulling and med, then get a debug log from your puller and post it here..

 

[kett73]

Resolved: I changed my group window and everything is working properly now. Old window did not show mana or endurance just health. As soon as I changed it everything started working.

 

[Zorduk]

Since yesterday(5/18) I have started having this issue - using default ui, puller continues pulling even if healer is at 10% mana, groupwatch is set 2|45, tried with multiple characters as puller, using default groupwatch=1, as well as groupwatch=2|45, or 1|45 makes no difference.

I am sure there is a way I can get feedback from the program to see what is going wrong, how do I trigger that? :P

 

[ctaylor22]

/debugall will spam the debug info.

GroutWatchOn=2 will only watch Cleric, Druids, and Shaman.

Setting it to 1|45 would be better for testing.

 

[Zorduk]

Ok, I turned on /debugall, using groupwatch=1|45, but I am not seeing any spam regarding groupwatch, it goes straight from mob dying(turned chain pulling off because of this issue) to looking for mobs and then pulling again... I would think it was a messed up ini, but it's happening on all toons, and only happened after the most recent patch(may 17?).
Is debug info sent to a log file of some sort? I could possibly be missing the messages, though I set up conditions to test it upon activation, which used to work fine, and they go straight to pulling.

-----Edit-----
Figured out how to turn on logging - and though I used /debugall, I am not seeming to get the debug spam in the log file. Log just shows mob killed, and starts looking for new mob to pull w/ no reference to groupwatch or anything.

-----2nd Edit-----

Just added a long pause between pulls to try and mitigate the issue - puller doesn't pause the set time either. Something funky has started since last patch.

 

[ctaylor22]

Yea, you have an issue with your aliases. You need to run the Remove_Aliases.mac macro and reset your macro version in your characters ini file.. The aliases get reset if you run an older version of kiss by mistake.

Run the newest version of kiss on all characters... The Aliases are global..

 

[Meistro]

Question, if you delete all Kiss files, do you need to run the Remove_Aliases.mac macro?

 

[ctaylor22]

Yes... If your only deleting the stuff in the Macros Directory. The aliases are stored in the MacroQuest.ini file in the MQ2 directory. Not in the macros directory.