Temporary fix version of Kelrugem's Extended Automation

At Kelrugem's suggestion I am posting up here my attempt at providing a temporary fix version of Kel's Extended Automation extension until he is able to find time to patch and release his official version.

I have already passed all the changes I have made for this version to Kel to hopefully help him with his work. These changes may or may not be doing things in exactly the way that Fantasy Grounds expect but my aim is to have something that works and helps bridge the gap until Kel can fix things in a fully correct way.


No guarantees that everything that used to work will work, but my group has been using this version for a couple of sessions and it currently seems to be in a state where it is working for us.

I am happy to get feedback in this thread on any issues and will try to look into and resolve any issues, and will keep feeding any changes on to Kel.

Also would be interested to get some feedback if you do use this and don't find problems as that will probably also help to know whether there aren't any issues reported just because nobody is using it...

This is not on Forge, so to install you will need to take the attached zip file, unzip it and copy the resulting folder to your FG extensions folder
e.g. C:\Users\<your user>\AppData\Roaming\SmiteWorks\Fantasy Grounds\extensions

Then when selecting extensions look for and select 'RV Feature: Extended automation and overlays' - making sure you deselect Kel's extension 'Feature: Extended automation and overlays'

Thanks a lot :) Appreciate the help! :)

Hey,

Thanks for this fix so far. I did some testing and it looks like (CUSTOM) isn't working while this is turned on. Specifically I tried IF: CUSTOM(test); DMG: +1d6 with a test effect on the same character. I then tried attacking with that character and it cancelled the attack and gave a [ERROR] Script execution error: [string "CoreRPG:scripts/manager_actor.lua"]:71: stack overflow instead. This was the only extension active for this testing.

Quote:

---

Originally Posted by FGMax

Hey,

Thanks for this fix so far. I did some testing and it looks like (CUSTOM) isn't working while this is turned on. Specifically I tried IF: CUSTOM(test); DMG: +1d6 with a test effect on the same character. I then tried attacking with that character and it cancelled the attack and gave a [ERROR] Script execution error: [string "CoreRPG:scripts/manager_actor.lua"]:71: stack overflow instead. This was the only extension active for this testing.

---

Hi FGMax,
I have a completely new Pathfinder 1E campaign with this one extension loaded and I've added effects as I've interpreted from your report. I am getting the expected outcome of the additional damage on a damage roll and attack roll completing. So I'm not able to reproduce this. Let me know if I've not got this setup as you have.
Attachment 67752
Attachment 67754

Edit: Same outcomes for me with a 3.5E campaign

I am getting the same error though i think it is a conflict with something else. Since you are not able to recreate the effect. it is most likely a conflict with another ext. i cant do testing at the moment. but i will later

Quote:

---

Originally Posted by rogerv

Hi FGMax,
I have a completely new Pathfinder 1E campaign with this one extension loaded and I've added effects as I've interpreted from your report. I am getting the expected outcome of the additional damage on a damage roll and attack roll completing. So I'm not able to reproduce this. Let me know if I've not got this setup as you have.
Attachment 67752
Attachment 67754

Edit: Same outcomes for me with a 3.5E campaign

---

The first test was with 3.5 but I just tested with PF and got the same issue. The only other thing loaded for the test was the Theme: Legacy - Wood. I also tested without that loaded and get the same error so I'm not sure yet what the commonality is other than the lone extension being loaded since Arimil is saying the same thing. Latest version too.

While I have not tested the extension alone I think I know what might be going on. You all remember recently with all the effect changes they added Conditionals to Core. I think we are seeing a conflict between how core is handling these and how the temp fix of extended automation. What makes me point to this is the fact that the error is being called by Core with nothing else installed.
I would recommend looking at how Core handles Conditionals for custom tags and if they give similar enough functionality. we disable how extended automation handles Conditionals for the time being until a more permanent fix can be implemented because of how impactful this error is. it does not just not allow a roll it hangs the program.