• Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
  • We've added LLM sections to our Terms & Rules and Resource Rules, for everyone's sanity & in-game safety.
    Read more
    a. Do not replace your voice with an LLM. This goes for your posts and your scripts. Drafting and editing with a tool is fine, but don't take you out of what you share.
    b. Do not replace your EQ character's voice with an LLM. We don't want scripts that speak over /ooc, /shout or other public channels. This has been an unwritten rule that's kept casino scripts off the site for decades, but we're now compelled to make it clear: keep automated communication private.

    Why Does RG Review Scripts?
    Nearly every LLM-written Lua script we see is making your character do impossible things, and rarely in a way that's beneficial to you. We've seen heavy server hammering, /target over impossible distances when /nav spawn would passively accomplish the same thing, a spawn search that fires 20+ times per second, and other pointless actions that are likely annoying GMs.

    You are welcome to use LLMs as a tool to structure, draft, and edit your work, but please read critically before hitting /lua run
MQ2CWTNCommons

Utility - MQ2CWTNCommons

I seem to be having issues with encounter locking recently. There are random pulls where my team won’t attack a mob. I only use the cwtn plugins.

If I pause the plugin I can attack. If I yell on my chars I can attack. A /con of the mob does not say it is encounter locked (before yelling, while not being able to attack). It has happened in a group and raid setting. In all of those instances my characters are the only ones in the group or raid.

I thought maybe it was a group or raid bug where it showed chars in the groups but maybe actually were not but restarting and reforming didn’t help.

I can’t exactly recreate it on command but it usually happens when I pull 3-5 mobs one of them will be locked. These aren’t long pulls more like running into the middle of a room and aggroing that many.
 
I seem to be having issues with encounter locking recently. There are random pulls where my team won’t attack a mob. I only use the cwtn plugins.

If I pause the plugin I can attack. If I yell on my chars I can attack. A /con of the mob does not say it is encounter locked (before yelling, while not being able to attack). It has happened in a group and raid setting. In all of those instances my characters are the only ones in the group or raid.

I thought maybe it was a group or raid bug where it showed chars in the groups but maybe actually were not but restarting and reforming didn’t help.

I can’t exactly recreate it on command but it usually happens when I pull 3-5 mobs one of them will be locked. These aren’t long pulls more like running into the middle of a room and aggroing that many.
i'll check

edit: i bet it is a pet who got the target lock - i'll edit our checks that if it has a master we check the master owner

if it happens again can you do something like this for shits
INI:
/echo ${Target.EncounterLockStatus} - ${Target.EncounterLockOwner} (${Target.EncounterLockOwner.Type}) master: ${Target.EncounterLockOwner.Master}

edit edit: - updated and rebuilt, patch and it *should* hopefully be fixed - I also did a PR for MQ to be able to check that too
 
Last edited:
ChatWithThisName updated MQ2CWTNCommons with a new update entry:

11/15/2026b

  • lower the amount of time we ignore a corpse if we've been told another character is rezzing it from 90s to ~10s
  • adjust priority order
    • RAMA1/2/3, group MA/MT, group clr/shm/dru, then regular class list (tank, priests, necro, everyone else)
  • if you see any oddities, make sure to get a "debugrez" and/or "broadcastrezfailures" outputs which will tell you why someone was skipped

Read the rest of this update entry...
 
Not sure if this is due to new settings, but during raids, my clerics, druids and shammy's are not rezing corpses automatically like they used to. Is this a function that was changed during the most recent class plugin updates. They have use rez sticks checked, and everyone is accepting rez's at 90%. But nothing is being done while engaged in a raid/fight.

Anyone else experiencing this or know if I need to change settings for some reason?

Any help would be greatly appreciated. Thank you.
 
yes, they are. i would be dragging a corpse (so i knew it wasn't bugged), and it would just be dragging the corpse around unless I manually rezzed it. That's seems to be across the board for clerics, and shammy's. haven't check the druid out, but if noone is rezzing, then I'm guessing it's consistent.
 

11/15/2026b​

  • lower the amount of time we ignore a corpse if we've been told another character is rezzing it from 90s to ~10s
  • adjust priority order
    • RAMA1/2/3, group MA/MT, group clr/shm/dru, then regular class list (tank, priests, necro, everyone else)
  • if you see any oddities, make sure to get a "debugrez" and/or "broadcastrezfailures" outputs which will tell you why someone was skipped
We could use some debugs to determine where abouts the failure is occuring. If you can PM some information it would assist us in tracking the issue down.
 
Will check tomorrow. already logged. will get on, update redfetch and any plugins that need it, then go die and see what happens and either I'll get a rez, or i'll get data to submit. Might try in a couple hours after dinner.
 
Will check tomorrow. already logged. will get on, update redfetch and any plugins that need it, then go die and see what happens and either I'll get a rez, or i'll get data to submit. Might try in a couple hours after dinner.
sorry to hear about that - hopefully this is already fixed

Yes, if you're not already updated then please do so first, then if you are please turn on broadcastrezfailures so you can see what failures are reports, and turn on debugrez and send me a snip in pm.
/cwtnbuffs rez broadcastfailures

based on download times, i suspect you weren't running the latest and ran into whatever "failure" resulted in delayed rezzes. I updated and built yesterday which would lower that delay from 90s to 10s for certain checks (someone was already going to rez that corpse)
 
Last edited:
ChatWithThisName updated MQ2CWTNCommons with a new update entry:

11/17/2026

  • added additional rezzing "about to rez" claim
    • this helps coordination of actors related rezzing
  • non-actors rezzers should still go to a next corpse if they can't rez something
  • this update and previous updates should hopefully maybe potentially possibly be a potentially fixing fix ™️

Read the rest of this update entry...
 
ChatWithThisName updated MQ2CWTNCommons with a new update entry:

11/22/2026

  • I'm looking for a couple of raid testers that have a small raid crew (3-5 IRL people) to test something pretty sweet, please PM Sic if you're interested
  • Thanks for the feedback on the rez skipping (especially Myysterio)
  • We'll now max out at ~30s before we try and re-rez someone (down from 90s)
    • this is unless it is an invalid corpse, too old for a rez, or we get a "can't find corpse" response from the server
  • We will also recognize if we are rez didn't...

Read the rest of this update entry...
 
Utility - MQ2CWTNCommons

Users who are viewing this thread

Back
Top
Cart