Utility - MQ2CWTNCommons

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

01/30/2021

CWTN Plugins - ALL
- Correct some issue with Active Discs reporting back erroneously which causes stopdisc to not occur.
- If you say "reminder" to Virtuous Dusk, we will now refresh your disciplines.
- Rez Sickness and Snare pull holds were seperated from groupwatch, apologies.
- Not using clickies in safe zones has been changed to not use clickies with charges in safe zones.
-- This does not apply to burn, offensive, or defensive clickies. Yay cookie...

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

02/14/2021

CWTN Plugins - ALL
- added ${CWTN.MobsToPull}
-- boolean true/false if we think we have mobs we want to pull.
- Adjusted BurnCount msg output.

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

02/22/2021

CWTN Plugins - ALL
- Fixed an issue that could cause your UI to "lag out" when clicking inside it.
- Clicking the CWTN Icon on the settings tab now acts as a temporary pause toggle.
-- You will now see a large "PAUSED" icon over your window when paused (via button or command etc).
--- Clicking this "PAUSED" icon will unpause you.

MQ2Bst
- Adjusted Buff Check Timer.

MQ2Monk
- Fixed a missing check for Bandoswap.
-- (Bandoswap...

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

02/26/2021

CWTN Plugins - ALL
- StickHow has been replaced with StickSelection.
-- AS ALWAYS the "stickselection" options are only for during an assist mode.
-- The default for "castery" classes has been updated to be more functional for castery classes
-- AS ALWAYS Do not use percent signs in the stickhow listings, unless you double percent it like: 55%%.
--- You will crash otherwise.
-- So if are currently using a custom StickHow you will want to ensure...

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

03/08/2021

CWTN Plugins - ALL
- Updated DoT Checks to check for *our* dots on a mob, and not just "any dot" that matched our dot's name.
-- this required code addition to mq2 main.
- our "safe zones" checks will ignore instanced Plane of Tranquility.
- Downtime clickies, if they are "Target Type Single" we will target ourselves to cast it.
-- Mainly lower lvl / TLP items like Lodi boots.
-- We currently do not have an option to use items like this on others.

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

3/16/2021

CWTN Plugins - All
- For Necromancer, Mage, and Enchanters who are set to MA's, we will now use their pet's distance from the MA's target to determine if we should engage.
-- instead of not engaging because the MA is a ranged pure caster with a pet tanking. The pet is still expected to be within melee range from the mob.
- /blah UseStick off/on will now save to the appropriate ini section.
- Debugpull will now also spit out mob's ID.
- Debpugpull now has...

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

03/24/20201

CWTN Plugins - ALL
- We have added additional logic to try and help stagger clickies that give group buffs or give you an aura.
-- Examples: Unified Phoenix Feather and Rage of Rolfron.
-- We still don't actively track or wait on another group member to do anything.
-- We still say "are we supposed to click our item, is it ready, am i missing the buff from it?"
--- if those are met, we click the item.
-- this additional logic will try and help...

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

03/31/2021

CWTN Plugins - ALL
- Progressive spell preference now uses this order:
-- "comp 6, 5, 4, 3, dissi 6, 5, comp 2, dissi 4, comp 1, dissi 3, 2, 1, dicho" with a change to composite 2 over dissi 4
--- there are mostly minor secondary reasons why composite 2 is better than dissi 4 - but improvements non-the-less.
- Corrected typo in ReportAssist ini entry.
-- Thank you Hylander for the Aassist.
- Pet Shrink Clickies (like earrings or Curious...

Read the rest of this update entry...

 

[Undefeated]

The post made to this thread will have dates. Those are the dates of submission to my repo. If the date on the plugin update notes are BEFORE the date of the "Lastest Version" on the redguides launch. It's probably live. If it's AFTER, then they are not yet released and will be in next patch.

View attachment 19676

If there are changes listed here that are not currently live. Make sure you've updated your plugin to the latest version as sometimes Redbot builds between EQ updates.

View attachment 19677

View attachment 19678

Red is out of date. Green is up to date.

HEY I use Mq2 Shaman,Zerker,SK, and Bst. After the update today when I press chase hot key the one Sic has my toons are not changing into chase mod why is that? Can u help plz.

 

[Sic]

HEY I use Mq2 Shaman,Zerker,SK, and Bst. After the update today when I press chase hot key the one Sic has my toons are not changing into chase mod why is that? Can u help plz.

Plz don't post in multiple locations.

The update didn't change any of that functionality as I mentioned in the other place you asked.

Sounds like you are not connected to eqbc ir dannet etc.

Or you reinstalled mq2 and didn't reinstall nav meshes

 

[Undefeated]

Sorry about that. Ya for some reason I got disconnected.

Thanks,

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

04/13/2021

CWTN Plugins - ALL
- Fixt a check for decapitate when user is using mq2headshot.
-- this gives mobs a "last name", which we normally try and avoid while pulling.
--- this allows if mq2headshot is used and it has the last name of "Decapitate", that we don't ignore them for purposes of pulling.
- Updated some Addclicky and target swapping logic so you should no longer try and target someone to cure with a clicky and then change target back quickly.

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

04/21/2021

CWTN Plugins - ALL
- Fixt potential issue with shrinkclickies actin` up.

Read the rest of this update entry...

 

[ItsMeIntrikit]

Hey guys, I think there might be a busted config value reference in the pulling/med logic. I noticed on mq2monk and mq2eskay that they would always pause pulls whenever the watched members (Cleric Only in the attached screenshots) have less mana than ManaMedStart, this seems good. But then it would only wait until the watched members have more mana than ManaMedStart, this seems bad. I only end up pausing long enough to let the healer get a couple perecent and then resume, rather than waiting until they top off at the ManaMedEnd value. Is this intentional?

 

[Sic]

Hey guys, I think there might be a busted config value reference in the pulling/med logic. I noticed on mq2monk and mq2eskay that they would always pause pulls whenever the watched members (Cleric Only in the attached screenshots) have less mana than ManaMedStart, this seems good. But then it would only wait until the watched members have more mana than ManaMedStart, this seems bad. I only end up pausing long enough to let the healer get a couple perecent and then resume, rather than waiting until they top off at the ManaMedEnd value. Is this intentional?

View attachment 29736
View attachment 29737

manamedstart - the mana % you start medding at
manamedend - the mana % you end medding at

if you're asking if they continue medding until manamedend - yes.

the message above you says "Cleric is at 16 mana, and our threshold to start medding is 40, so we need rest"

that same message can get spit out later with the same threshold message - I can update that for clarity.

 

[ItsMeIntrikit]

manamedstart - the mana % you start medding at
manamedend - the mana % you end medding at

if you're asking if they continue medding until manamedend - yes.

the message above you says "Cleric is at 16 mana, and our threshold to start medding is 40, so we need rest"

that same message can get spit out later with the same threshold message - I can update that for clarity.

The problem is that the puller is actually not waiting until ManaMedEnd is reached for the watched members, only for itself (in the case of mana for the SK). I will gather more steps for reproduction and report back, I have a hunch that it only gets into this state when I change the ManaMedStart after the plugin has loaded.

 

[Sic]

The problem is that the puller is actually not waiting until ManaMedEnd is reached for the watched members, only for itself (in the case of mana for the SK). I will gather more steps for reproduction and report back, I have a hunch that it only gets into this state when I change the ManaMedStart after the plugin has loaded.

are you changing it with the slash command or the window?

I don't seem to be able to reproduce what you're saying.

both the window and slash command adjusts the value correctly

 

[ItsMeIntrikit]

are you changing it with the slash command or the window?

I have tried both, after recognizing it was in this state.

Scenario I just confirmed:

Right before a mob (`a shrieker`) died, I executed `/shd ManaMedStart 60` resulting in the following Pulling settings in mq2eskay:



As soon as the mob dies, the Cleric and SK are both @ 50% Mana, so we start our Med routine. Coincidentally our health is below `HPMedEnd` of 85% so we will also, presumably, med until that is 85%.



As you can see in the above screenshot, the `Threshold` value for the Cleric's Mana is 60 (which matches `ManaMedStart`) however the `Threshold` value for the SK's Mana is 85 (which matches `ManaMedEnd`).

When the SK fulfilled both of their conditions @ 85% the Cleric's Mana was at 75% (10% short of `ManaMedEnd`) and the SK initiated a pull.

 

[Sic]

I have tried both, after recognizing it was in this state.

Scenario I just confirmed:

Right before a mob (`a shrieker`) died, I executed `/shd ManaMedStart 60` resulting in the following Pulling settings in mq2eskay:

View attachment 29739

As soon as the mob dies, the Cleric and SK are both @ 50% Mana, so we start our Med routine. Coincidentally our health is below `HPMedEnd` of 85% so we will also, presumably, med until that is 85%.

View attachment 29738

As you can see in the above screenshot, the `Threshold` value for the Cleric's Mana is 60 (which matches `ManaMedStart`) however the `Threshold` value for the SK's Mana is 85 (which matches `ManaMedEnd`).

When the SK fulfilled both of their conditions @ 85% the Cleric's Mana was at 75% (10% short of `ManaMedEnd`) and the SK initiated a pull.

this says "starting to med because 50 is lower than 60


this says "continuing to rest because 49 and 66 is lower than 85


but you're saying at 75% mana on the cleric, it started pulling instead of the 85?

if so you reaching your threshold must be bumping the rest of the group check

 

[ItsMeIntrikit]

this says "starting to med because 50 is lower than 60
View attachment 29740

this says "continuing to rest because 49 and 66 is lower than 85
View attachment 29741

Ahh, ok. I interpreted all of these messages as "We are medding, the <Class> is at <*MedStart> and we want to wait until threshold of <*MedEnd>" but I understand these now.

but you're saying at 75% mana on the cleric, it started pulling instead of the 85?

That is correct.

if so you reaching your threshold must be bumping the rest of the group check

Iirc, when the Monk was pulling, the Cleric would be the only character needing to Med and it would still only wait until it met the MedManaStart threshold to begin pulling again. This was like 10 days ago and I just had my KA Bard do pulls, but where I am now the SK was better for pulling. I will adjust the group and try to get an example with the monk and try to confirm my recollections.

If it is worth any additional value, I'm a senior software engineer and this behavior smells of a misplaced ManaMedStart where a ManaMedEnd was intended in the Group Check logic. Likely somewhere where it is checking if we should "Start Pulls" and the value to check is actually the *End value not the *Start value, for example. That's at least where I'd start to look, if I were looking through the code.

 

[Sic]

If it is worth any additional value, I'm a senior software engineer and this behavior smells of a misplaced ManaMedStart where a ManaMedEnd was intended in the Group Check logic. Likely somewhere where it is checking if we should "Start Pulls" and the value to check is actually the *End value not the *Start value, for example. That's at least where I'd start to look, if I were looking through the code.

well if you don't think that is the first thing i looked at then asking cwtn or i for help is absolutely going to be no use to you what-so-ever.

 

[Sic]

but i'll continue to see if i can replicate your report - which i can't so far.

 

[ItsMeIntrikit]

well if you don't think that is the first thing i looked at then asking cwtn or i for help is absolutely going to be no use to you what-so-ever.

Ahh, dang, sorry. I definitely didn't mean to assume you wouldn't have done that. I did assume you wouldn't just immediately jump directly into the code based off of a single user call out, let alone on a Saturday. My bad, no disrespect. I really appreciate the real-time support.

I'll continue to get more data on the behavior. I've been able to mostly work around it by making my Cleric more efficient or using the Bard to pull, so it's not a fire drill but more of a bug report. Thanks, again, for the weekend help.

 

[Sic]

Ahh, dang, sorry. I definitely didn't mean to assume you wouldn't have done that. I did assume you wouldn't just immediately jump directly into the code based off of a single user call out, let alone on a Saturday. My bad, no disrespect. I really appreciate the real-time support.

I'll continue to get more data on the behavior. I've been able to mostly work around it by making my Cleric more efficient or using the Bard to pull, so it's not a fire drill but more of a bug report. Thanks, again, for the weekend help.

nah was just messing with you. I try and jump on everything the moment i see it. - I added the tomcat to help imply i was teasing

I think i may have found something, and if i didn't i'll keep looking until i can confirm/rule it out.

 

[ItsMeIntrikit]

nah was just messing with you. I try and jump on everything the moment i see it. - I added the tomcat to help imply i was teasing

I think i may have found something, and if i didn't i'll keep looking until i can confirm/rule it out.

I've worked in Operations for a few years, I'm _exceedingly_ empathetic with user support

Here is an interesting data point that just happened... I pretty much always run in Cleric Only watch mode for the puller because I have a Shaman in the group, but I rarely care about their Mana because of Canni.

My shaman had just been rezzed and I wanted to get the SK to pause for a second, so I flicked it over to Healer watch mode and the output makes more sense, now:



Looks like the Cleric isn't getting registered as a group member still needing to wait for Med when in Cleric Only mode?

 

[Sic]

I've worked in Operations for a few years, I'm _exceedingly_ empathetic with user support

Here is an interesting data point that just happened... I pretty much always run in Cleric Only watch mode for the puller because I have a Shaman in the group, but I rarely care about their Mana because of Canni.

My shaman had just been rezzed and I wanted to get the SK to pause for a second, so I flicked it over to Healer watch mode and the output makes more sense, now:

View attachment 29742

Looks like the Cleric isn't getting registered as a group member still needing to wait for Med when in Cleric Only mode?

well that's only possible if eq is saying your cleric isn't a cleric - and the output says that your cleric is a cleric so that doesn't appear to be a problem

re: the message and clarity - like i mentioned before i'll have some clarity in that for next update with Starting Threshold and Ending Threshold and the missing ":" for the health output as seen below

 

[ItsMeIntrikit]

well that's only possible if eq is saying your cleric isn't a cleric - and the output says that your cleric is a cleric so that doesn't appear to be a problem

After I sent that last response I thought I should have added the previous image for comparison, here is what I am seeing that looks different...

`Cleric only` watch mode: Cleric triggers the Med Start, but in the next section (printed near instantly after) even though their Mana was still below either Threshold it wasn't printed



`Healer` watch mode: Cleric and Shaman trigger the Med Start, but in the next section (also printed near instantly after) the Cleric, Shaman, and SK are all included.



Sorry if I'm not making sense or just repeating back to you what you've already realized. I think that's about the limits of what I can provide, if you need a tester for a hotfix or anything else, let me know. Good luck, these plugins are awesome.

re: the message and clarity - like i mentioned before i'll have some clarity in that for next update with Starting Threshold and Ending Threshold and the missing ":" for the health output as seen below
View attachment 29743

Nice catch! I didn't even see that until you mentioned it :P

 

[Sic]

lmfao


found it

 

[Sic]

tl;dr - there was a missing case check in a switch for cleric group watch when we're already resting, to continue resting for cleric =p

 

[Sic]

@ItsMeIntrikit lemme shoot you a fresh mq2eskay

 

[Sic]

 

[Sic]

 

[ItsMeIntrikit]

 

[ABDon]

Hey folks - is there any ETA on if/when the CWTN plugins will be available on MQNext please?

 

[ChatWithThisName]

Hey folks - is there any ETA on if/when the CWTN plugins will be available on MQNext please?

msg me on discord.

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

4/25/2021

CWTN Plugins - ALL
- Fix't GHBuffBot possible crash (unreported, but still possible).
- Added some clarity to groupwatch output (Starting and Ending).
- Corrected some missing punctuation in groupwatch output
- fix't issue where the "we're now group watching should we continue to do so" check for cleric was *missing*

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

5/10/2021

CWTN Plugins - ALL
- Corrected unreported issue where the "visibility state" of the CWTN UI window (shown / unshown) didn't save between sessions.
-- This means if you close your window, and log out, it won't pop back up unless you ask it to.
-- So if this has been happening to you, you're not crazy, and its not your fault.
- AddClicky ManaSelf: Can now safely use mana conversion items without fear of trying to chain cast if the
-- conversion would...

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

5/19/2021

CWTN Plugins - ALL
- Fixed an issue that was causing AA's to respect GCD when they shouldn't have.
- Workaround for mq2 issue related to active campfire in instances.

Read the rest of this update entry...

 

[Redbot]

Redbot updated MQ2CWTNCommons with a new update entry:

5/25/2021

CWTN Plugins - ALL
- Corrected issue that would cause some classes to re-apply AAs when not needed.
- We will now force open your player window if it is closed.
-- This is because MQ2 uses player window information for "Combat State".
- Emu: buffstacking updates.
- Emu: fixed some emu specific buffing issues.

Read the rest of this update entry...

 

[Rusang]

I know this request could be very difficult, but is it possible to implement a similar method to ignore non-killable mobs that Pocketfarm uses? This is for the CWTN plugins and in hunter tank modes.

If not familar with PKF, the macro recognizes a non-killable mob. It tries attacking for a few seconds and when nothing happens, it adds it to a temporary ignore.

I know the /class ignore command works, and I am using that, but I wanted to place a request for added features if its not too much work.