• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
MQ2CWTNCommons

Utility - MQ2CWTNCommons (1 Viewer)

Overview Updates (274) Reviews (7) Discussion
I was wondering if it was possible to make a change to the pulling system; right now you can choose min max levels for which mobs to pull. Would it be possible to add a new feature that makes it dynamic? So instead of set levels, change it/add a new option to make it + and -? Would enable us to be a bit more dynamic in which mobs we'd pull as we leveled.
 
EQFoli said:
I was wondering if it was possible to make a change to the pulling system; right now you can choose min max levels for which mobs to pull. Would it be possible to add a new feature that makes it dynamic? So instead of set levels, change it/add a new option to make it + and -? Would enable us to be a bit more dynamic in which mobs we'd pull as we leveled.
Click to expand...
no, no plans on doing that

but you could easily make a lem to do that. your LevelMin and LevelMax are type members - ${CWTN.LevelMin} ${CWTN.LevelMax}
 
I was wondering if there was/could be any plan in the future for a /swarm leave on pull option? It is fairly frequent that if I have a swarm class (to include my SK) pulling. Even though pet ghold is on, the swarm has no such control and will engage the mob for several seconds before dying and allowing the target to come into camp. It could be nice to have a pulling toggle to allow a /swarm leave every time the puller starts a pull routine.

Especially as you're trying to keep up with 7 groups and your beastlords end up as the puller/tank in 3 of them. 🙄
 
Last edited:
Barnal said:
I was wondering if there was/could be any plan in the future for a /swarm leave on pull option? It is fairly frequent that if I have a swarm class (to include my SK) pulling and although pet ghold is on, the swarm has no such control and will engage the mob for several seconds before dying and allowing the mob to come into camp. It could be very nice to have a pulling toggle to allow a /swarm leave every time the puller starts a pull routine.

Especially as you're trying to keep up with 7 groups and your beastlords end up as the puller/tank in 3 of them. 🙄
Click to expand...
no, but all toons have an option not to use swarm abilities - so if you're doing the "old timey method of pulling to a camp" instead of "hunter tanking and taking the fight to them" i'd suggest turning off swarms
 
Sic said:
no, but all toons have an option not to use swarm abilities - so if you're doing the "old timey method of pulling to a camp" instead of "hunter tanking and taking the fight to them" i'd suggest turning off swarms
Click to expand...
Thank you for the quick reply. I know you suggest hunter tanking, but when I'm managing 7 groups, it's easier for me to have a solid position. This way it's easier to monitor camp checks, onlookers, etc. When I am running a single group, I will often run hunter tank and chase, or sictank and chase.

I have run my tanks with swarm off (as that was the first most obvious answer to my problem) and I still do now most of the time, but the amount of DPS I lose (from the beastlords in particular) is pretty significant. I just thought I would ask about a toggle, but I understand why you would say no. Appreciate what you guys do as always.
 
Is this a bug or am I using it wrong? It's the same for all the CWTN plugins I have. /cwtna CampOverlapBuffer 25 gives this message on all of them.

1717941247038.png

1717941173365.png
 
Is there a repo for the cwtn commons plugin to track issues\feature requests, etc... that subscribers can view? I was looking specifically to see if there was future enhancement in the backlog that would provide sort functionality to the level column in the info>spells tab. When a spell rune drops I generally use this tab to see which toons still need their Rank3 for that level, which is awesome, but it would be even more awesome if I could sort the level column to see all the lvls together and not hunt them down in the list.
 
Altermego said:
Is there a repo for the cwtn commons plugin to track issues\feature requests, etc... that subscribers can view? I was looking specifically to see if there was future enhancement in the backlog that would provide sort functionality to the level column in the info>spells tab. When a spell rune drops I generally use this tab to see which toons still need their Rank3 for that level, which is awesome, but it would be even more awesome if I could sort the level column to see all the lvls together and not hunt them down in the list.
Click to expand...
no there isn't

yes sorting is something we'll be doing soon
 
So I been playing around with the class plugins, and it seems to happen to them all, so I don't know where to put this. My plugins are casting spells at the spell's max range, but not MY max spell range. I have campradius set to 300, line of sight, can cast on mobs, MA has target, casting on the target, is standing right next to the casterbot, etc. I have to move up to the spells normal range for it to start casting spells. The extended range will assist, but will not begin casting (or send pets) until i move closer to the target.

I have noticed its also doing this for healers healing as well. Have to move up healers to < 200 range to get them to heal their tank

I was looking at the MacroQuest docs and I have noticed there is a TLO for Spell[myspell].Range and Spell[myspell].MyRange. Not sure if there's anything to do with this.
 
Having this same issue with necro and shaman. It's making it difficult to get caster dps on Magus when my guild tries to do the temperature shock achievement.
Need to keep toons out of range of the aura but still do dmg. Like you they'll get the target but then they just sit there.
 
Myysterio said:
So I been playing around with the class plugins, and it seems to happen to them all, so I don't know where to put this. My plugins are casting spells at the spell's max range, but not MY max spell range. I have campradius set to 300, line of sight, can cast on mobs, MA has target, casting on the target, is standing right next to the casterbot, etc. I have to move up to the spells normal range for it to start casting spells. The extended range will assist, but will not begin casting (or send pets) until i move closer to the target.

I have noticed its also doing this for healers healing as well. Have to move up healers to < 200 range to get them to heal their tank

I was looking at the MacroQuest docs and I have noticed there is a TLO for Spell[myspell].Range and Spell[myspell].MyRange. Not sure if there's anything to do with this.
Click to expand...
well you mentioned this and i mentioned that we do, use the "my extended range"

so maybe there's an mq issue with the extended range calculation. i'll take a look
 
I have also noticed this same situation on enchanter on Magus in raids. I assumed it was some sort of line of sight issue, so I just default to my hot key to cast. Thanks for you bringing it up and looking into it!
 
Chibz said:
I have also noticed this same situation on enchanter on Magus in raids. I assumed it was some sort of line of sight issue, so I just default to my hot key to cast. Thanks for you bringing it up and looking into it!
Click to expand...
without a specific spell to check, it is just about impossible for me to say.

I am looking at it right now, and it appears we are using the focused ranged modifier correctly.

we have a "how to ask for help" thing for a reason. This will li kely end up being something completely unrelated to what myysterio says it is related to, even tho him and i already spoke about it.

which doesn't mean there *isnt* a problem. it just means i need more specific information
 
Sic said:
This will li kely end up being something completely unrelated to what myysterio says it is related to, even tho him and i already spoke about it.
Click to expand...
Nope, I was wrong. While we do correctly use the modified range for casting, we weren't using modified range for our target validation checks.

This is why giving reproducible steps/scenario is important.

But yep, thanks for writing it up, this would have been a bug for ever and ever - even when adjusted distances were added
 
@Myysterio @Chibz @Fargrim rebuilding now - this update should address this - if you all can just confirm that it is working as expected when you get back to the raid events / whatnot i'd appreciate it.

thanks
 
Sic said:
@Myysterio @Chibz @Fargrim rebuilding now - this update should address this - if you all can just confirm that it is working as expected when you get back to the raid events / whatnot i'd appreciate it.

thanks
Click to expand...
Thank you! I'll check it when lockouts are up for that event specifically and whatever else I can do to test it in the meantime. Sounds like you figured it out though! Thank you for taking the time to look into it! Very much appreciated!
 
To simulate conditions, I put my necro and shaman on vorpal, camp radius 300, Auto Assist at 100.
I then slowly pulled mobs from distances greater than 300, once in that 300 distance camp radius pets were sent in.
After getting the mob to 270 distance casting begins.
At this point the thing is doing the stuff.
I'll confirm the specific situation with Magus after lockout is up but this seems like it's good to go.

Thank you again for taking the time to find the hiccup and taking quick action.
 
Fargrim said:
To simulate conditions, I put my necro and shaman on vorpal, camp radius 300, Auto Assist at 100.
I then slowly pulled mobs from distances greater than 300, once in that 300 distance camp radius pets were sent in.
After getting the mob to 270 distance casting begins.
At this point the thing is doing the stuff.
I'll confirm the specific situation with Magus after lockout is up but this seems like it's good to go.

Thank you again for taking the time to find the hiccup and taking quick action.
Click to expand...
perfect thanks for the followup
 
Worked beautifully in the raid, casters are casting at max range under the same conditions as before the change.
Mythic Charm...Equipped.
 
Not sure if this is the right place.

Having trouble with camp radius line on the map after using mapfilter settings. It and pull and cast radius no longer drawn automatically to the new settings when changing them in the MQ2BST UI. I found the /mac map command to reset the map and that got the cast radius working (green line). But I no longer see the blue line and the yellow line is centered on 0,0.

Any idea on how to get these to reset and work when making changes to the BST ui?

Thanks,
 
You must log in or register to reply here.
Utility - MQ2CWTNCommons
Next unread thread 🦁

Users who are viewing this thread

Total: 2 (members: 0, guests: 2)
Back
Top
Cart

Cart

Total -