Plugin - MQ2Eskay (1 Viewer) 3.1.52471.11

[Daryldixonurmouth]

for emphasis
View attachment 27462

Its gotta be the Assigned Group MT thing then. Most of the time on Raids Im a Group leader/MT for that group. What that does however is make it so I have to turn off MQ2ESKAY for buffing purposes. Which is fine, I would just prefer to be able to always use MQ2ESkay because I prefer it

 

[Sic]

trying to update it and link isnt working, anyone else having an issue?

you use the VV launcher to update the plugins.
if says here your launcher downloaded it just fine today

 

[vandersl]

Getting this message on startup (rebooted, ran EQ patcher, updated from Launchpad, updated plugins):

The servers are back down again, but this message seems to be completely MQ2 related and not getting the same message for MQ2Ber, MQ2Cleric.

 

[Sic]

Getting this message on startup (rebooted, ran EQ patcher, updated from Launchpad, updated plugins):
View attachment 27522
The servers are back down again, but this message seems to be completely MQ2 related and not getting the same message for MQ2Ber, MQ2Cleric.

VV isn't patched yet - so you can't load mq2 or the cwtn plugins until VV is updated.

 

[Wolfborn]

"Please recompile mq2eskay - it is out of date with mq2main"

 

[Sic]

Try patching now - red just released VV early

 

[Sic]

"Please recompile mq2eskay - it is out of date with mq2main"

because today is a patch day.

 

[vandersl]

Ah, NVM - just looked more carefully at the plugin page and noticed that MQ2Eskay date is 01-16. So I guess it didn't update. Did update all again (I really did do that before) and now the date looks good.

 

[Wolfborn]

all gud

 

[Grainer]

I've unloaded and reloaded mq2nav and mq2eskay and every time i go into sictank mode or another modes and set a camp, the red circle on my map no longer shows. It works on my beast and other toons, just won't show on my SK

 

[Sic]

I've unloaded and reloaded mq2nav and mq2eskay and every time i go into sictank mode or another modes and set a camp, the red circle on my map no longer shows. It works on my beast and other toons, just won't show on my SK

you probably have your layer 3 hidden



if it was an mq2nav problem you would get kicked out of modes with "camps" and get told that you need mq2nav and a valid mesh.

 

[Draknocht]

Tonight SK is no longer using DoT Snares, hasn't been memming either. AAsnares and use DOTsnares were both still on, even turned off the AAsnares as I don't have AA snares yet. Been an ugly night of wipes before realizing the snare wasn't even getting used. and the Shrooms in Direwind are faster than Usain Bolt.... anything else i need to check?

 

[Sic]

Tonight SK is no longer using DoT Snares, hasn't been memming either. AAsnares and use DOTsnares were both still on, even turned off the AAsnares as I don't have AA snares yet. Been an ugly night of wipes before realizing the snare wasn't even getting used. and the Shrooms in Direwind are faster than Usain Bolt.... anything else i need to check?

nothing has changed in the spell loadouts.

are you byos - is your mana above your dotmanamin?

we stop auto-memorizing dotsnare when we get touch of daygun at 69

 

[drkdmn79n]

Hiya,

My sk is not auto attacking the mob. He will just stand there and get beat down. He runs to the mob and just stands there. I may be missing another macro or plugin for that. I did have to move some things around. This is only a recent issue, so I imagine I've done something. I'm using hunter tank.

 

[Sic]

Hiya,

My sk is not auto attacking the mob. He will just stand there and get beat down. He runs to the mob and just stands there. I may be missing another macro or plugin for that. I did have to move some things around. This is only a recent issue, so I imagine I've done something. I'm using hunter tank.

sounds like you need to adjust your campradius

 

[drkdmn79n]

sounds like you need to adjust your campradius

OMG! Your the man!

 

[arander]

hey you two, i started having an issue today (hasnt been before today cause i have been at this camp many times over last 2 weeks)

i set the SK pull radius 460 and arc to 110, then play with it till i get it aimed right. normally that keeps the SK out of the lava. and pretty much constant pulls.

Today 2 issues come up
1 he will stop pulling to "wait for mobs" when there are 10+ mobs up inside the pull radius
2 keeps running off to the left into the lava and dieing.

Attaching screen shots of map. 1 is of SK pull setup, other is of where he keeps dieing at. So you can see there is absolutely NO reason for him to even be CLOSE to that location

 

[arander]

heres another one, i snagged a shot as it was pulling. as you can see, WAY outside the range that is showing as set on the map. Keep having to pause the plugin to get him out of lava and to a safe place or stop him from pulling a certain mob

 

[vandersl]

heres another one, i snagged a shot as it was pulling. as you can see, WAY outside the range that is showing as set on the map. Keep having to pause the plugin to get him out of lava and to a safe place or stop him from pulling a certain mob

Not sure of the zone, but you don't have map height filter enabled. What is your zradius set to? If there are mobs below you, and there is a path to them, SHD will try to pull them even if he has to go outside your pull radius to do it.

I typically make sure map height filter is set same as pull zradius to make sure I dont try to pull any unintended mobs.

 

[vandersl]

On the topic of pulls - I have noticed a new behavior where SK will stop pulling to let group rest at levels unrelated to pull settings. So I get messages like "Shm mana current: 83%

This seems possibly related to new 'don't pull when snared' logic, which I have started seeing after the patch:
We are snared! Holding pulls.

 

[vandersl]

Oops - posted early. Snared message shows "Group needs rest" immediately below it. But sometimes I get "Shaman current mana is 83%, threshold is 90%" and he rests until Shaman recovers to 90%.

Problem is pull watch settings has mana start at 20%. And Shaman isn't medding at 80%, so sits there for a while waiting for the regen.

 

[arander]

Not sure of the zone, but you don't have map height filter enabled. What is your zradius set to? If there are mobs below you, and there is a path to them, SHD will try to pull them even if he has to go outside your pull radius to do it.
I typically make sure map height filter is set same as pull zradius to make sure I dont try to pull any unintended mobs.

480
35
35
110
just odd it has been working great for weeks. ive been leveling up some alt toons. ive pretty much been camped in there for almost 3 weeks. Yesterday it happend once, but today its happening ALOT.

and no, he isnt supposed to pull anything that isnt in the pull area

 

[vandersl]

Sorry for the separate posts. Caught one of them:

Seems like the snare logic kicks in, then the cure happens, so it thinks we are resting for mana?

 

[Jalerian]

I have added both Duskbringer's Plate Chestguard of the Hateful (which has Leeching Embrace clicky: Increase Melee Lifetap by 150%) and Tarnished Dreadheart Plate Breastplate (which has Vthlalix's Painskin clicky: add defensive proc: Painskin strike rate 400) using /shd addclicky defensive and neither one of them have ever been used as far as I can see.

So, I have 4 questions:
1) How do I check if I have successfully added them? I know there is a report as soon as you do it, but how do I check what clicky is being used when after the fact?
2) When is a defensive clicky supposed to be used?
3) What is the difference between offensive and burn clicky categories?
4) Is defensive the best category for those?

Thanks!

 

[ChatWithThisName]

Sorry for the separate posts. Caught one of them:
View attachment 27593
Seems like the snare logic kicks in, then the cure happens, so it thinks we are resting for mana?

If you get snared the plugin will hold pulls.

 

[Sic]

Sorry for the separate posts. Caught one of them:
View attachment 27593
Seems like the snare logic kicks in, then the cure happens, so it thinks we are resting for mana?

adjust your group watch settings if you don't want to med until 90 that would be your manamedend

 

[Sic]

I have added both Duskbringer's Plate Chestguard of the Hateful (which has Leeching Embrace clicky: Increase Melee Lifetap by 150%) and Tarnished Dreadheart Plate Breastplate (which has Vthlalix's Painskin clicky: add defensive proc: Painskin strike rate 400) using /shd addclicky defensive and neither one of them have ever been used as far as I can see.

So, I have 4 questions:
1) How do I check if I have successfully added them? I know there is a report as soon as you do it, but how do I check what clicky is being used when after the fact?
2) When is a defensive clicky supposed to be used?
3) What is the difference between offensive and burn clicky categories?
4) Is defensive the best category for those?

Thanks!

1. you can do /shd reportclickies which is in the commands tab which you should familiarize yourself with
2. defensive is used when you're the target of the mob you're fighting
3. offensive is used anytime when you're fighting (doing offensive stuff).
3b. burn is when you're meeting your burn conditions
4. your bps i personally use as burn clickies because of the longer recast - but you can use defensive, but you would pop it any time the mob you are fighting is targetting you.

 

[ChatWithThisName]

I have added both Duskbringer's Plate Chestguard of the Hateful (which has Leeching Embrace clicky: Increase Melee Lifetap by 150%) and Tarnished Dreadheart Plate Breastplate (which has Vthlalix's Painskin clicky: add defensive proc: Painskin strike rate 400) using /shd addclicky defensive and neither one of them have ever been used as far as I can see.

So, I have 4 questions:
1) How do I check if I have successfully added them? I know there is a report as soon as you do it, but how do I check what clicky is being used when after the fact?
2) When is a defensive clicky supposed to be used?
3) What is the difference between offensive and burn clicky categories?
4) Is defensive the best category for those?

Thanks!

1) /shd reload
2) When you are the target of your current target.
3) offensive is used anytime you're in combat and burn is used anytime you're burning. If your first target is a named then it would use both offensive and burn is the items are ready.
4) Probably.

 

[Sic]

480
35
35
110
just odd it has been working great for weeks. ive been leveling up some alt toons. ive pretty much been camped in there for almost 3 weeks. Yesterday it happend once, but today its happening ALOT.

and no, he isnt supposed to pull anything that isnt in the pull area

you can always /shd debugpull on once and it will spit out why you didn't pull a specific mob.

 

[Jalerian]

2. defensive is used when you're the target of the mob you're fighting

I double checked using the /shd reportclickies command and both of these breastplates are listed in the defensive category and both are available to click, but as I mentioned before....they are not being used. I am in puller tank mode and it also does not use them in Sic tank mode. Any ideas why?

 

[vandersl]

If you get snared the plugin will hold pulls.

I understand that. While I think that is new, that isn't the problem. What seems to be a problem is that SK will stop pulling saying 'group needs rest' even when not snared (or at least, I don't see a snare in the buff window). When it does this it shows 'current 83%, threshold 90%' even though pull threshold is 90%. Just 30 seconds ago it did it again. I immediately moved the SK around - he was not snared. But he sat right back down with the 'group needs rest' message.

It seems to me that if I get snared the 'wait until med stop threshold' logic kicks in, so all conditions to exit med and start pulling need to be met, rather than just the removal of the snare. This would be OK, except the chars aren't medding (never reached there med thresholds) so it can take a while before starting to pull again.

For myself, I wouldn't mind if 'stop pulling if snared' was an option. While this may be a great addition for pulling back to camp, I often run in HunterTank mode where this option isn't necessary (doing that now). I question the value of the setting in the first place, as usually the snare happens on the way back to camp, and not the way out, so I don't know how often this will really help the puller avoid a death.

 

[Sic]

I understand that. While I think that is new, that isn't the problem. What seems to be a problem is that SK will stop pulling saying 'group needs rest' even when not snared (or at least, I don't see a snare in the buff window). When it does this it shows 'current 83%, threshold 90%' even though pull threshold is 90%. Just 30 seconds ago it did it again. I immediately moved the SK around - he was not snared. But he sat right back down with the 'group needs rest' message.

It seems to me that if I get snared the 'wait until med stop threshold' logic kicks in, so all conditions to exit med and start pulling need to be met, rather than just the removal of the snare. This would be OK, except the chars aren't medding (never reached there med thresholds) so it can take a while before starting to pull again.

For myself, I wouldn't mind if 'stop pulling if snared' was an option. While this may be a great addition for pulling back to camp, I often run in HunterTank mode where this option isn't necessary (doing that now). I question the value of the setting in the first place, as usually the snare happens on the way back to camp, and not the way out, so I don't know how often this will really help the puller avoid a death.

like i responded, adjust your manamedend.

your shaman is at 83, and waiting to meet your setting of 90 to continue

since i don't really care about waiting for my shaman's mana, i have that med to start at 5 and stop at 30

 

[Sic]

I double checked using the /shd reportclickies command and both of these breastplates are listed in the defensive category and both are available to click, but as I mentioned before....they are not being used. I am in puller tank mode and it also does not use them in Sic tank mode. Any ideas why?

well it is checked in combat (irrespective of mode) - more than likely the spell isn't going to stack with whatever buffs you have at the moment.

I would recommend using them in your burn routine anyhow

you're not on a tlp or server that doesn't have aggro information available are you? I think that needs VOA or RoF unlocked?

your vthally'x doesn't appear to stack with the defenseproc line of buffs

 

[Jalerian]

you're not on a tlp or server that doesn't have aggro information available are you? I think that needs VOA or RoF unlocked?

You are remembering correctly. I am on Ragefire.

well it is checked in combat (irrespective of mode) - more than likely the spell isn't going to stack with whatever buffs you have at the moment.

The only thing that I can think of that Duskbringer's Plate Chestguard of the Hateful wont stack with would be the epic click and that is no where near 100% uptime. So should have been used at some point. It might not be casting Tarnished Dreadheart Plate Breastplate (which has Vthlalix's Painskin clicky: add defensive proc: Painskin strike rate 400) because of Malarian Skin. I just checked and this clicky does overwrite Malarian skin tho...

 

[Sic]

you can see here my defensive clicky is one of the first things that happen

 

[Sic]

You are remembering correctly. I am on Ragefire.


The only thing that I can think of that Duskbringer's Plate Chestguard of the Hateful wont stack with would be the epic click and that is no where near 100% uptime. So should have been used at some point. It might not be casting Tarnished Dreadheart Plate Breastplate (which has Vthlalix's Painskin clicky: add defensive proc: Painskin strike rate 400) because of Malarian Skin. I just checked and this clicky does overwrite Malarian skin tho...

ah well that's it. defensive clickies is going to check your aggro - which if you don't have that information available, then defensive clickies aren't going to work for you.

i'd suggest moving it to burn or offensive

 

[Jalerian]

Ahh, the TLP bites again! Thanks for helping me track it down! I really appreciate how willing you are to help all of us better enjoy this game!

 

[Sic]

Ahh, the TLP bites again! Thanks for helping me track it down! I really appreciate how willing you are to help all of us better enjoy this game!

you're welcome dude - I'm sincerely hoping next tlp cycle they decide to open aggro information to all xpacs

 

[vandersl]

like i responded, adjust your manamedend.

Whoa-major time warp. When I posted (and yes, I am woke enough to refresh the page) there were no posts from you Sic, even though there's only a 1 minute gap between CWTN and your response. In fact I don't think I responded to CWTN for a while yet none of the other posts were there.

Anyways, yes, there may be ways around this. But they defeat the purpose (or at least IMHO they defeat the purpose) of the watch settings.

It isn't that I don't care about the Shaman mana levels - he's my primary healer (as of a couple days ago) and when he reaches 20% it may be time to med up. But if everything else is going along fine, chars are at 70%, and the puller gets snared, it seems it shouldn't trigger the 'OK, lets have everyone wait until they reach 'ManaMendEnd/HPMedEnd/EndMedEnd'. Seems like the puller could get back to the job of pulling as soon as the snare wears off (which can be quickly if cured) rather than triggering a group med watch. If you want to say 'bugger off, that's the way it works' then that's OK. I just figured it is a pretty minor tweak to a feature (stop pulling on snare) that probably not that many asked for in the first place (wasn't in my top 10 anyway).

 

[Sic]

Whoa-major time warp. When I posted (and yes, I am woke enough to refresh the page) there were no posts from you Sic, even though there's only a 1 minute gap between CWTN and your response. In fact I don't think I responded to CWTN for a while yet none of the other posts were there.

Anyways, yes, there may be ways around this. But they defeat the purpose (or at least IMHO they defeat the purpose) of the watch settings.

It isn't that I don't care about the Shaman mana levels - he's my primary healer (as of a couple days ago) and when he reaches 20% it may be time to med up. But if everything else is going along fine, chars are at 70%, and the puller gets snared, it seems it shouldn't trigger the 'OK, lets have everyone wait until they reach 'ManaMendEnd/HPMedEnd/EndMedEnd'. Seems like the puller could get back to the job of pulling as soon as the snare wears off (which can be quickly if cured) rather than triggering a group med watch. If you want to say 'bugger off, that's the way it works' then that's OK. I just figured it is a pretty minor tweak to a feature (stop pulling on snare) that probably not that many asked for in the first place (wasn't in my top 10 anyway).

no group watch is just that - it will start at the start amount and stop at the end amount

so if you have your ManaMedStart at 10, you will start medding the group when one of the group watch toons reaches 10 mana if your ManaMedEnd is at 30, once those toons hit 30 you go back to pulling, if you have ManaMedEnd at 90, you will go back to pulling at 90.

you just happened to have both snare and a mana med group watch trigger at the same time. once the snare was gone, your shaman was still not at the 90 setting, so it was going to continue to wait until it met your setting.

now - am i understanding that you're saying that you believe that the snare made you wait for the ManaMedEnd despite you not meeting the ManaMedStart? Because if that is what you're trying to say, then that isn't right and that is definitely a bug that does need correcting. (and means i didn't understand you before, so my apologies)