Kelrugem's extensions

[Kelrugem]

Update, I seem to have resolved the issue. I went back through the restore/update steps from above. Then I deleted a dying troll with regeneration from the combat tracker.

I noticed on a previous attempt that the issue triggered when I manually advanced the combat tracker and reached the troll's turn, or clicked the "next round" button. Something about the troll wasn't playing nicely with the updates.

Thanks for the report

It sounds like a known issue with advanced effects and extended automation This issue should be fixed recently, but I see that you updated FGU and all extensions. Do you still see the issue and can reproduce it, or is this error now gone forever?

[MDarque]

err.png
I am still getting the error:
[ERROR] Script execution error: [string "..Full OverlayPackage:..r_action_damage.lua"]:279: attempt to index local 'rSource' (a nil value)
For me it is happening when clicking next actor in the Combat Tracker, and the next character has the effect: DMGO: 1

[Kelrugem]

err.png
I am still getting the error:
[ERROR] Script execution error: [string "..Full OverlayPackage:..r_action_damage.lua"]:279: attempt to index local 'rSource' (a nil value)
For me it is happening when clicking next actor in the Combat Tracker, and the next character has the effect: DMGO: 1

Thanks for the report

Just to make sure, you all have extended automation and advanced effects loaded, right?

Then there might be still an issue, I try to fix it later

[MDarque]

Thanks for the report

Just to make sure, you all have extended automation and advanced effects loaded, right?

Then there might be still an issue, I try to fix it later

Yes, I have Advance Effects v1.18-hotfix.1 and Extended automation v4.2.2.2

[Kelrugem]

Hmm, that is a strange issue. I cannot reproduce the error but effects like DMGO and REGEN do not work together nicely right now, if the actor has both effects and I have extended automation and advanced effects loaded. So, there is indeed still an incompatibility, but the error suggests that there might even a third extension intervening.

MDarque, can you still produce the error with just these two extensions loaded? If yes, did you already update the extensions again?

I try to solve the existing issue, but I am a bit puzzled about the incompatibility right now

[Kelrugem]

Hmm, that is a strange issue. I cannot reproduce the error but effects like DMGO and REGEN do not work together nicely right now, if the actor has both effects and I have extended automation and advanced effects loaded. So, there is indeed still an incompatibility, but the error suggests that there might even a third extension intervening.

MDarque, can you still produce the error with just these two extensions loaded? If yes, did you already update the extensions again?

I try to solve the existing issue, but I am a bit puzzled about the incompatibility right now

Oh, wait, there is no incompatibility I can reproduce. I think I accidentally found a problem within FG itself which is a totally different issue (It seems that a REGEN effect turns (untyped) DMGO effects to nonlethal damage)

So, I am back to zero, I cannot reproduce the reported problems.

Can you, Schneiderpants and MDarque, update and confirm the errors with just advanced effects and extended automation loaded?

[MDarque]

Using only Advanced Effects AND Extended Automation, I was able to get the exception with DMGO, REGEN and FHEAL. REGEN and FHEAL only threw the exception when the character was damaged.
If running Advanced Effects OR Extended Automation, the error does not occur.

[MDarque]

Oh, wait, there is no incompatibility I can reproduce. I think I accidentally found a problem within FG itself which is a totally different issue (It seems that a REGEN effect turns (untyped) DMGO effects to nonlethal damage)

So, I am back to zero, I cannot reproduce the reported problems.

Can you, Schneiderpants and MDarque, update and confirm the errors with just advanced effects and extended automation loaded?

I decided to look at the code itself, and noticed that Extended Automation v4.2.2.2 does that have the code fix that bmos committed to Github. I updated my local files with the same changes, and it fixes the issue.

[Kelrugem]

I decided to look at the code itself, and noticed that Extended Automation v4.2.2.2 does that have the code fix that bmos committed to Github. I updated my local files with the same changes, and it fixes the issue.

Ah, very good; but you mean that the forge version did not work while the github version worked? I just checked the forge version, it should be the same as on GitHub; I hope it is not a problem with the forge itself

[MDarque]

Ah, very good; but you mean that the forge version did not work while the github version worked? I just checked the forge version, it should be the same as on GitHub; I hope it is not a problem with the forge itself

Correct. The forge version did not work, but the github version did work. The version numbers seem to be the same on both. So maybe up the version number and reupload to forge to make sure it sends the correct version to the clients?

To verify that the forge version has issues, I just removed the extension and had FG download it again, and the exception returned. I then replaced the corrected version and it worked again.