

/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./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./lua run
i'll checkI 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.
/echo ${Target.EncounterLockStatus} - ${Target.EncounterLockOwner} (${Target.EncounterLockOwner.Type}) master: ${Target.EncounterLockOwner.Master}
- fix issue with buffing when in a raid (issue introduced in aug)
- fixed issue if a FTE owner was a pet (now we check if that pet's owner is in our raid/group)
- one of the bug fixes earlier this week exposed a 5+ year never-hit bug with doing stuff "off-target" (mezzing or even the new necro multidotpyre)
- this is fixed
- bards should reliably single target mez again
- fixed near impossible-to-replicate issue where you had to click on your settings panel for you to do stuff after entering raidmode
- thanks to Levox for helping figure this out. Could not have done it without their help replicating the issue and testing debugs.
- 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
Thank you for this, I was wondering what was going on but couldn't quite figure out where the issue was happening. Much appreciated change.ChatWithThisName updated MQ2CWTNCommons with a new update entry:
11/15/2026b
Read the rest of this update entry...
if you see something please get me a debugrez snip or a broadcastrezfailures snipThank you for this, I was wondering what was going on but couldn't quite figure out where the issue was happening. Much appreciated change.
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.
- 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
sorry to hear about that - hopefully this is already fixedWill 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.
- 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
- 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...