I made sure that Framelimiter was set up on all toons (it was not before). My settings are attached. The behavior still occurs. As can be seen in the attached picture, I set camp, pulled a mob and the bard used intimidation and his first dot before attempting to mez. Wouldn't the fact he is casting intimidation and the dot indicate that he is 'in combat' for the purposes of this discussion?
-
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! 👋
- Thread starter ChatWithThisName
- Start date
Call to combat
Check charm
Check mez
Check bunch of other stuff
intimidate
Dots/nukes
Rinse and repeat
Well move to get line of sight as long as long as you're not in manual mode, but other than that we would if needed.
Can try adjusting your camp radius, but other than what I mentioned, we always check it first
But like I said, I'll have a think/check about that adjustment or not
Should I adjust camp radius on my bard, my tank, or both? I assume make it bigger? I have not touched camp radius on any of the toons since I installed the plugins...so they are all set to the default radius of 60. I will try playing around with camp radius on both and see what happens.
I hope that this would be the case, but I still don't understand why my guy is doing intimidate/bellow and dots before he is mezzing.
I upped the camp radius on my bard to 75 (my tank and rest of the group are all at 60). The bard is still using intimidate and bellow before every mez attempt. He even did it when I pulled 4 and then used Wave of the Conductor (level 95 aoe mez).
@Jalerian ok, spent some time with the code this morning to ensure i'm explaining well, and not confusing myself or you.
For purposes of mezzing, we are checking that the mob is in our camp, and not the target of our MA, so it makes sense that the bard is immediately engaging the MA target (cause the MA is gonna grab the first mob that comes into camp), and then start doing stuff to it and once the other mobs come inside your camp, it would start. (assuming in camp, health at or below assistat value)
I'd suggest a couple of things, you can mix/match and see what works for you.
since we don't enter combat until the MA's target meets our requirements (in camp, health at our assist at value), i'd make sure you have all your toons set to assistat 100 --- because otherwise you won't do your combat stuff (in this case including mezzing) until you meet that assistat value on the MA's target - by that time other mobs are probably in camp doing shit
I'd also have your MA's camp being lower than your assistat toons camp
I usually do something like 45 MA 60 assist, or 60 MA 80 assist
again, the idea is that you're not going to care about mezzing until a: your regular combat conditions are met and b: the mob is inside your camp (otherwise you wander across norrath and beyond trying to mez)
For purposes of mezzing, we are checking that the mob is in our camp, and not the target of our MA, so it makes sense that the bard is immediately engaging the MA target (cause the MA is gonna grab the first mob that comes into camp), and then start doing stuff to it and once the other mobs come inside your camp, it would start. (assuming in camp, health at or below assistat value)
I'd suggest a couple of things, you can mix/match and see what works for you.
since we don't enter combat until the MA's target meets our requirements (in camp, health at our assist at value), i'd make sure you have all your toons set to assistat 100 --- because otherwise you won't do your combat stuff (in this case including mezzing) until you meet that assistat value on the MA's target - by that time other mobs are probably in camp doing shit
I'd also have your MA's camp being lower than your assistat toons camp
I usually do something like 45 MA 60 assist, or 60 MA 80 assist
again, the idea is that you're not going to care about mezzing until a: your regular combat conditions are met and b: the mob is inside your camp (otherwise you wander across norrath and beyond trying to mez)
All my toons were set at 100 assist before my original post.
I will try to bump the bards radius up to 80 and see, but last night with it at 75, there were many pulls where the 1st mob was below 50% health before my bard started his first mez on the second mob.
i saw where you said you bumped to 75, 60->75 isn't that much of a difference, especially depending on what mob type you're fighting. 50% on the main mob before you're doing stuff is sus - because again, before we even get to the rest of the "intimidate/dot/nuke/whatever" we're checking to mez, those mobs need to be in your campradius and not targeted by your MA.
I'd try something larger and then dial it back as needed - 45 MA campradius, 100 bard campradius
i almost always have the MA shorter than the dps, and all the dps the same
if they're the same, you can run into a thing where the mob is in the MA's range but not the dps's
I set the bard's camp radius to 100, Tank's to 45, and dps to 60. Unfortunately, the behavior is still the same. Intimidate, Bellow, and then it varies between a dot or mez. Mez never comes before intimidate or bellow. Bright side is that I did not wipe because of it...!?
- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
- Seller
- #492
Okay, so I gave this a once over based on the information you've provided so far.
Lullaby of the Forlorn - Mez up to level 95 mobs.
Slumber of Kolain - Mez up to level 98 mobs.
The information I was able to look up suggests that these two mobs are likely right on the edge of your mez ability or over it. We'll need you to verify the level of the targets does not exceed the capabilities of the spell you are casting.
The fact that Allakhazam suggests these mobs are 104-106 that I've clearly seen the output showing you're casting on means that the either the data on the mobs is inaccurate, or the data on the spell is inaccurate (least likely), or they exceed you ability to mez (most likely).
How to test - pause the plugin, con the mob that isn't being mezzed that you expect to get mezzed, get level from output. Verify the mob is less than or equal to level 98
Lullaby of the Forlorn - Mez up to level 95 mobs.
Slumber of Kolain - Mez up to level 98 mobs.
The information I was able to look up suggests that these two mobs are likely right on the edge of your mez ability or over it. We'll need you to verify the level of the targets does not exceed the capabilities of the spell you are casting.
The fact that Allakhazam suggests these mobs are 104-106 that I've clearly seen the output showing you're casting on means that the either the data on the mobs is inaccurate, or the data on the spell is inaccurate (least likely), or they exceed you ability to mez (most likely).
How to test - pause the plugin, con the mob that isn't being mezzed that you expect to get mezzed, get level from output. Verify the mob is less than or equal to level 98
a pestilent invader | 106 - 106 | Monster | Plane of Health: In Defense of Health |
|
| a bubonian soothsayer | 104 - 104 | Monster | Plane of Health: In Defense of Health |
|
- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
- Seller
- #494
That would make more sense as to how it is you got the bard to cast mez on mobs that allakhazam suggested was too high a level.
Nothing jumps out at me in the logic as being problematic. Will give it some more consideration.
- Joined
- Oct 29, 2025
- RedCents
- 210¢
Anyone have more details on the Bard loadout settings? Does the loadout change the way the Bard does ADPS?
My group is warrior, mage, necro, bard, shammy. Any advice on what loadout I should select?
Thank you.
My group is warrior, mage, necro, bard, shammy. Any advice on what loadout I should select?
Thank you.
if you want to dps, use casterdots, if you dont want to dps and want to mostly be support, be caster
Q: What is the deal with the loadouts?
A: These get stronger the closer you are to "modern game" as many of the spell lines "modern" bards use you don't get until 70s, 80s, 90s and beyond.
tl;dr:
- Raid MT Group - use Tank Support it uses "Requiem", "Accelerando", "Spry Sonata", and "Reckless Renewal"
- Raid/Group caster group - use casterdots for personal dmg, caster for no dots (sic uses casterdots)
- Raid/Group melee group - use meleedots for personal dmg, melee for no dots (sic uses meleedots)
- Joined
- Oct 29, 2025
- RedCents
- 210¢
- Joined
- May 15, 2019
- RedCents
- 552¢
With the upcoming changes to spells and SPA for Shattering of Ro, it would be a significant boost to be able to run Bard Epic and Fierce Eye in a rotation. Currently FE is only used in unison with Bard Epic, which does not provide sustained crit uptime for the enitre group. Can a change be made to treat FE either to be ran in parallel with bard epic or opposite/in rotation with bard epic be considered? Thanks.
we actually do something pretty cool to determine when to throw fierce eye if we're juiced enough group that we have high dot and dd crit bonuses - if we're under our threshold we throw FE anytime we have our epic buff, if we're not under our threshold for both dot crit bonus and dd crit bonus we wait until our epic has less than 60 seconds on the duration
considering the hamfisted smashing of stuff to get things pushed through for xpac, we'll probably make those kind of evaluations in january patch once its been determined if dbg is going to change anything back.
currently there is a lot of SPA stacking that is absolutely broken, so we don't intend on taking everything at face value at xpac launch.
we could have even made the changes already, you don't know :p - but as always, we'll make changes as they are needed, I'm just anticipating the first month of this xpac to be a shitshow
Thanks for the heads up, i'll make sure we keep an eye on this
- Joined
- May 15, 2019
- RedCents
- 552¢
Great stuff as usual Sic!! You guys always amaze me how on top of this stuff you are...for all the classes.
- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
- Seller
- #502
ChatWithThisName updated MQ2Bard with a new update entry:
11/25/2025
Read the rest of this update entry...
11/25/2025
Read the rest of this update entry...
Sentient_Pasta
Active member
- Joined
- Mar 10, 2025
- RedCents
- 408¢
Hey gang,
Hope this is helpful and the right place to report it, but the MQ2 Bard plugin seems to have stopped using the Bard Speed AA with UseSelos Checked on Test Server (have not checked on other servers).
I know you guys are working hard to make sure everything is working with the new expac (And it's very much appreciated!) If this bug is already known please disregard.
Cheers!
Hope this is helpful and the right place to report it, but the MQ2 Bard plugin seems to have stopped using the Bard Speed AA with UseSelos Checked on Test Server (have not checked on other servers).
I know you guys are working hard to make sure everything is working with the new expac (And it's very much appreciated!) If this bug is already known please disregard.
Cheers!
I'll take a look. We haven't changed anything there
- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
- Seller
- #505
ChatWithThisName updated MQ2Bard with a new update entry:
11/28/2025
Read the rest of this update entry...
11/28/2025
Read the rest of this update entry...
knave23
Cookie Champion 2022
- Joined
- Sep 10, 2019
- RedCents
- 6,290¢
I'm noticing since updating that my bards now have UseSelos unchecked and I'm having to check it (after never touching it previously). I assume it's related to this fix and wanted to check if that's expected and if so let everyone know the fix isn't just "update and you're good to go." My suspicion is this flip was also setting the value in the toon.ini "incorrectly" so we all need to update locally for the full fix.
hrm, no not at all.
the only thing touched here was when i did some cleanup i had a > instead of a < because i was adjusting how i was utilizing a timer - which doesn't touch or have anything to do with it being on/off, or on the ini at all.
the fix is "just update and you're good to go"
selos is still initialized as "true" unless you have something in your mq2bard ini that says false/0/off - there is not even a circumstance where we set it to false
We don't try and mez the target of your group assigned ma. so i'd double check the character you want to be MA is assigned as group MA - and if it already is, try reforming your group
Also we don't "twist" like you're thinking
- Joined
- Sep 16, 2020
- RedCents
- 343¢
Possible bug/issue? When leveling from 57 -> 58 you get Chorus of Replinish...it places that in spell jewel #9 but doesn't remove cantata from jewel #1 and it just keeps cycling those two back and forth instead using any other songs. I got my bard back to normal working order by selecting BYOS and removing cantata
It does this. BYOSCustom and take which ever one you don't want in. That's the solution I came up with.
Last edited:
Thanks I'll check. Cycling replacing stuff over and over isn't intended
- Joined
- Sep 16, 2020
- RedCents
- 343¢
Yes, I understand