5E - Status Indicators by Mattekure (originally Matjam's Status Indicator)

[mattekure]

It runs on a clean campaign and even seems to run on a clean campaign with my other mods. On current campaign it throws the above mentioned errors. It's possible it's being caused by a setting on a mod that's not modified on the current campaign. Maybe someone else will come across it to provide more data. For now I will need to disable.

Yeah you’d have to turn off other extensions one by one to see what’s causing the conflict. Once I know that I can take a look at what might be causing it

[mattekure]

Just a thought, but are you running one of the extensions that changes the display from showing wounds to showing current HP? I could definitely see that causing an issue.

[ColinBuckler]

There appears to be an issue with the scaling of the overlay tokens.

With no other extensions loaded, I performed saving throws on a token with a Token Scale = 0.8. This task was performed on battlemap with a grid of 50px and a grid of 100px.

The screenshots are attached.

As you can see the red (X) indicating a failed saving throw is not set to the same scale in both images.

I am not sure, but it could be due to scaling to the token size rather than scaling to the grid size....though I could well be wrong.

[ColinBuckler]

|If a creature is has the "Unconscious" effect (maybe they are a sleep?) and is required to make a DEX or STR saving throw, this is an automatic failure (AUTOFAIL).

When this happens the extension does not put a red (X) on the token.

[mattekure]

There appears to be an issue with the scaling of the overlay tokens.

With no other extensions loaded, I performed saving throws on a token with a Token Scale = 0.8. This task was performed on battlemap with a grid of 50px and a grid of 100px.

The screenshots are attached.

As you can see the red (X) indicating a failed saving throw is not set to the same scale in both images.

I am not sure, but it could be due to scaling to the token size rather than scaling to the grid size....though I could well be wrong.

I can reproduce this, I'll see whats going on a post a fix

[mattekure]

I'll have to look into this one. The reason its not applying the save indicator is because a save is never actually rolled, its an automatic fail handled in a part of the code I dont currently monitor. This extension currently only triggers when an actual save is rolled.

[dotsoncs]

Just a thought, but are you running one of the extensions that changes the display from showing wounds to showing current HP? I could definitely see that causing an issue.

That's exactly what appears to be causing it. My game ran last night and the error popped up. If I disable 5E - Constitutional Amendments (Link - mod that shows 'Current' HP in tracker) then I no longer receive the error. In my testing this only seems to happen after I add a new creature to the Combat Tracker.

Let me know if you'd like any help with testing.

Each time I use the 'Next Actor' button it produces the error:

[2/27/2021 12:07:44 PM] [ERROR] Handler error: [string "scripts/Manager_Status_Indicators.lua"]:255: attempt to index local 'nodeField' (a nil value)

[eporrini]

That's exactly what appears to be causing it. My game ran last night and the error popped up. If I disable 5E - Constitutional Amendments (Link - mod that shows 'Current' HP in tracker) then I no longer receive the error. In my testing this only seems to happen after I add a new creature to the Combat Tracker.

Let me know if you'd like any help with testing.

Each time I use the 'Next Actor' button it produces the error:

[2/27/2021 12:07:44 PM] [ERROR] Handler error: [string "scripts/Manager_Status_Indicators.lua"]:255: attempt to index local 'nodeField' (a nil value)

I also use constitutional amendments so this checks out. I had a suspicion it was conflicting with this, but when I loaded them both up in a test campaign I didn't get the error. Based on your findings that also makes sense as I did not add another creature to the tracker in my test campaign.

[mattekure]

v6 posted. I changed how token scaling was being done, so it should be more consistent now across any map and between FGC/FGU.

Added in a save handler to pick up when an auto failed save is made. This should work for most, but there is a possibility that if another extension overrides this or also uses the onSave handler, they may conflict.

Should no longer throw errors with Constitutional Amendments extension

[ColinBuckler]

v6 posted. I changed how token scaling was being done, so it should be more consistent now across any map and between FGC/FGU.

Added in a save handler to pick up when an auto failed save is made. This should work for most, but there is a possibility that if another extension overrides this or also uses the onSave handler, they may conflict.

Should no longer throw errors with Constitutional Amendments extension

Yay!