Problem - Aggressive Medding

[winnower]

I work around this by restarting KissAssist, and the character will just popup and follow MA.

I also want to say when I run my MA in manual mode, he will constantly sit down in support as well... But not 100% sure about this.

 

[mroutlaw]

i had a shaman always did this as well, he also would cast while invis it was the only one out of the crew who did it , used to irritate me to no end but i never found fix i just used to have to wait for him till he got high enough to actually canni and then it was never a issue again

 

[TreeHuginDruid]

Once Sub DoWeMed is engaged (during post combat check/variable reset/check for adds/check for agro procedures) your pretty much locked into the medding process.

When you issue the "/chaseon" command all you are doing is changing the memory value for the ChaseAssist setting from 0 (inactive.. dont ChaseAssist) to 1 (active, ChaseAssist).

Your still going to sit there and med until you are finished.

Here is the exact loop you are in while medding:

            :wait_for_resume
                    /doevents
                    /if (${ReturnToCamp} && ${Math.Distance[${CampYLoc},${CampXLoc}]} > 10) {
                        /if (!${Me.Mount.ID} && ${Me.Sitting}) /stand
                        /call DoWeMove
                    }
                    /if (${Debug}) /echo DEBUG ${MedStat} ${MedStat1} ${MedStat2}
                    /delay 5
                    /call CheckCasting 50
                    /delay 5
                    /call WaitSubs
                    /if (!${MedCombat}) {
                        /call CheckForCombat 1 DoWeMed
                        /if (${AggroTargetID}) {
                            /if (${Med2On}) /varset MedStat ${MedStat1}
                             /varset Medding 0
                            /return
                        }
                    }
                /if (${Me.Pct${MedStat}}<100) /goto :wait_for_resume

It looks for new event triggers for defined procedures (/doevents)
Checks if you need to ReturnToCamp.
Performs the CheckCasting subroutine.
Performs standard waiting subs.
Then checks your value for medding during combat or not (MedCombat).. and if you have that as 1 it will check if you are currently in a combat situation.

You stuck in that loop and do not even go to the ChaseAssist portion of the DoWeMove subroutine that actually checks your ChaseAssist value and performs the appropriate actions for it (check if the MA is out of range and move accordingly based on your ChaseDistance value).

So.. LONG story short.. YES... /chaseon isn't doing diddly squat for you.. cause you are locked into a medding cycle until you either are in combat, have agro, or finish medding.

As far as i know... Maskoi has it this way for a reason... but I could be wrong. I have to get his input as to if he has specific reasons for not checking if the MA took off and break med for it.

I'm going to change this ticket to "being investigated". Once i hear from lizardboy on this.. we will address it further (if the code needs to be altered).

But as far as if you absolutely want to do this... right now... then just make the following change for now.. should work.. have not tested it yet.

            :wait_for_resume
                    /doevents
                    /if (${ReturnToCamp} && ${Math.Distance[${CampYLoc},${CampXLoc}]} > 10) {
                        /if (!${Me.Mount.ID} && ${Me.Sitting}) /stand
                        /call DoWeMove
                    }
                    /if (${Debug}) /echo DEBUG ${MedStat} ${MedStat1} ${MedStat2}
                    /delay 5
                    /call CheckCasting 50
                    /delay 5
                    /call WaitSubs
                    /if (!${MedCombat}) {
                        /call CheckForCombat 1 DoWeMed
                        /if (${AggroTargetID}) {
                            /if (${Med2On}) /varset MedStat ${MedStat1}
                             /varset Medding 0
                            /return
                        }
                    }
                    /call DoWeMove
                /if (${Me.Pct${MedStat}}<100) /goto :wait_for_resume

I can only assume at this point you might be doing a "roaming camp" scenario.. and this is messing you up.. but for now.. you have a partial answer and may have brought to attention either an issue for us to fix in production, or enlightened me as to the mad lizards mysterious and devious schemes.. lol

- - - Updated - - -

--- UPDATE ---

Just remembered... I'll probably get a "just tell them to use GroupWatchOn=1 on the MA's config so he don't go running off, and on whomever the puller is.. to not start pulls until peoples mana/end are good from medding" response from Maskoi....

GroupWatchOn=0/1/2 - Off/Entire group/Healers only - Clerics, druids and shammys. Toon will stop and med when group members get below 20 Mana/Endurance and resume when they med to 90%.

Make sure all the toons that have GroupWatchOn are set to the same value for MedStart on all toons... otherwise you may encounter issues with things.

- - - Updated - - -

still trying to touch base with maskoi on this.. but in the meantime, please try the GroupWatchOn=1 change suggested on puller and MA... and have all toons set to same MedStart value.

Report back plz.

 

[winnower]

Thanks, I'll try this.

Normally I run the MA in manual. No toons ever run KA in puller mode.

With my crew I really don't care about mana/end. But it is good for them to sit down if nothing is going on.

Looks like very thing is pretty much stock
MedOn=1
MedStart=25
MedCombat=0
GroupWatchOn=1
on all toons, except the shaman is MedOn=0

typical problem is somebody dies, then I want to move after res, but everybody wants to sit on their ass.

 

[TreeHuginDruid]

Thanks, I'll try this.

Normally I run the MA in manual. No toons ever run KA in puller mode.

With my crew I really don't care about mana/end. But it is good for them to sit down if nothing is going on.

Looks like very thing is pretty much stock
MedOn=1
MedStart=25
MedCombat=0
GroupWatchOn=1
on all toons, except the shaman is MedOn=0

typical problem is somebody dies, then I want to move after res, but everybody wants to sit on their ass.

Understood.. you sometimes play the MA manually and want to move after a rez or medding on a toon starts.

But if you are not manually playing your MA and letting KA play it... is having GroupWatchOn=1 on the MA working to resolve this issue????????

As per your "typical scenario" ... yes.. that is how it should work... if everyone has groupwatchon=1.. then EVERYONE is going to sit and wait until the rezzed are back to 90% mana... provided you don't have agro/in combat..... thats the intended way of groupwatch.

typical problem is somebody dies, then I want to move after res, but everybody wants to sit on their ass.

Go chill for 2 minutes and grab a beer or something then.... wait for the toon to med.... Mr. I wanna rush things... LOL (/joke)

 

[winnower]

Woot, he gets up off his ass now!

Thanks!

 

[TreeHuginDruid]

Problem ticket being closed due to resolution provided.