Problem - RGmercs crash after VV Live 20250116 update

[LorDeth]

RGMercs Build?

1.2/The Outer Brood

What level is the character?

118

Morning folks.. I am seeing RGmercs crash on tank (SK), healers/hybrid (shm, dru), dps classes (rngr), (only class not crashing is my Bard) this morning after the most recent VV Live update 20250116 that Red pushed this morning ~3am. Each client is throwing the same exact error messaging, and it seems to happen when I am engaging a mob in melee combat (or, specifically, pull has happened, and it crashes as it seems its switching over to the combat module if that makes sense?).


Interesting to note, RGMercs was working perfectly yesterday on the initial VV Live 20250115 update. Only seeing this change as of this morning with the more recent update.

Cheers,
LorDeth

 

[Algar]

I will investigate, thanks.
You are correct to note the timing/update, it is related.

 

[an_image]

I will investigate, thanks.
You are correct to note the timing/update, it is related.

@Algar customer support…

Then a brainstorm session

 

[Derple]

@brainiac did anything change with how delays work? I am not current patched to either MQ or EQ so I cannot debug this right now.

 

[Derple]

Hey @LorDeth can you show me what code you have on casting.Lua at line 1323?

 

[Derple]

The problem I am seeing is that line 1323 should never even fire in combat if you are running the latest version of RGMercs.

 

[LorDeth]

Hey @LorDeth can you show me what code you have on casting.lua at line 1323?

I've loaded a clean vanilla RG and the most recent RGmercs Lua from the launcher.. so I have no custom configs, this is a totally clean updated install..

 

[Algar]

Our consternation is that particular bit of code should only be running when we aren't in combat, so the fact that it happens only when you start combat is decidedly odd (so he verified we are looking at the same code).

View attachment 67851

I've loaded a clean vanilla RG and the most recent RGmercs lua from the launcher.. so I have no custom configs, this is a totally clean updated install..

Derple is on the case!

 

[LorDeth]

Our consternation is that particular bit of code should only be running when we aren't in combat, so the fact that it happens only when you start combat is decidedly odd (so he verified we are looking at the same code).



Derple is on the case!

Let me know if there's anything specific I can test along the way... more than happy to help where I can

 

[LorDeth]

For reference, I reverted back to the 20150115 release of VV from earlier yesterday afternoon, and the older version of RGmercs, and it runs fine.. Other Lua's like overseer do not, but RGMercs works dandy!

So something has changed either in the VV 20150116 release or the updated RGmercs Lua from last night, that this is now happening...

 

[brainiac]

For reference, I reverted back to the 20150115 release of VV from earlier yesterday afternoon, and the older version of RGmercs, and it runs fine.. Other lua's like overseer do not, but RGMercs works dandy!

So something has changed either in the VV 20150116 release or the updated RGmercs lua from last night, that this is now happening...

I matched your error to rgmercs code from december. The code you're erroring on is a month old.

The error you're hitting is new, it is something that was previously failing silently and causing client crashes. I put it in last night so those errors could get reported instead of silently crashing. Why it is affecting just you I have no idea, but the out of date code is a good lead...

 

[an_image]

@brainiac translation … i found ahidden failure…and madeit public. You’re welcome @LorDeth

Disclaimer: post above is humor, all “i am going to kill you @an_image” responses will be treated as invites for further humor.

 

[Algar]

The issue should be resolved once the launcher picks up the update. Thank you for the report!

In case you didn't catch what brain was throwing down, the line numbers in the error didn't seem correct, and while you showed us recent code, the error messages (and other reports) indicate that the version of the script that you are running is nearly a month out of date. I'd take a look and ensure you don't have duplicate MQ installs or something funky like that!

 

[an_image]

The issue should be resolved once the launcher picks up the update. Thank you for the report!

In case you didn't catch what brain was throwing down, the line numbers in the error didn't seem correct, and while you showed us recent code, the error messages (and other reports) indicate that the version of the script that you are running is nearly a month out of date. I'd take a look and ensure you don't have duplicate MQ installs or something funky like that!

@Algar translation…stop looking at…

And update rgmercs…

 

[LorDeth]

Morning guys, I updated VV from last night, as well as the most recent RGmercs push, and everything is running like a boss this morning!

BTW, I'm really impressed with how much you guys have done with RGMercs over the last year or two. I'm only back a month after a long hiatus, and I had used rgmercs when it first came out.. This is a huge improvement in every way! Really loving using it!

 

[an_image]

Morning guys, I updated VV from last night, as well as the most recent RGmercs push, and everything is running like a boss this morning!

BTW, I'm really impressed with how much you guys have done with RGMercs over the last year or two. I'm only back a month after a long hiatus, and I had used rgmercs when it first came out.. This is a huge improvement in every way! Really loving using it!

We gave @Algar and team a raise @LorDeth … they now earn a crisp high five per update each…no longer shared

We trained this vahshir to assist with payments

 

[Robban]

Morning guys, I updated VV from last night, as well as the most recent RGmercs push, and everything is running like a boss this morning!

BTW, I'm really impressed with how much you guys have done with RGMercs over the last year or two. I'm only back a month after a long hiatus, and I had used rgmercs when it first came out.. This is a huge improvement in every way! Really loving using it!

@Algar and @Derple

 

[Algar]

@Algar and @Derple

You ain't exactly slacking on those Laz PRs my dude!

And please don't forget grim, he is the reason for half of the Laz stuff you do have XD