5E Life Ledger

[rhagelstrom]

We use the icon under the Class & Level section of the character sheet. Removing and re-adding them to the combat tracker doesn't seem to resolve the issue. When I leveled up a character in my own campaign, everything worked as expected.

I can't reproduce the issue. Might be a campaign issue, if you want to zip that up and post that.

[rhagelstrom]

@rhagelstrom

With Life Ledger loaded, viewing any MM2024 monster's record changes the status of the record (i.e., "the Revert Changes..." button appears, along with the revert arrow in the NPCs list). This does not happen if the extension is disabled. Is this expected behavior? I would prefer that a record be only marked as changed if the record is unlocked and/or modified. For my own education, what is Life Ledger doing to the NPC record that causes it to be marked as changed?

I can take a look at that.

[rhagelstrom]

@rhagelstrom

With Life Ledger loaded, viewing any MM2024 monster's record changes the status of the record (i.e., "the Revert Changes..." button appears, along with the revert arrow in the NPCs list). This does not happen if the extension is disabled. Is this expected behavior? I would prefer that a record be only marked as changed if the record is unlocked and/or modified. For my own education, what is Life Ledger doing to the NPC record that causes it to be marked as changed?

So looking at it what is going on is format of this module is different than how was previous. The module is not read only and this ext adds extra health fields, specifically temp HP and Adjusted HP. which are linked to database nodes within the xml. These fields obviously don't exist in the original record and are initialized when the record is opened. Since they aren't in the original they are written out to the moduledb/modules.xml. Since anything is written to this location, it marks the changed flag because technically they are.

Those fields show up hidden because this isn't a CT node and that's how it always was because you couldn't write to the db before so the ext hid them.

The solution, I'm not sure there is one other than removing those features from the NPC sheets entirely. It doesn't cause any problems per se other being an annoyance on that flag getting marked. I guess additionally I'd think this issue would also happen to other records for things that extensions are adding things to if module isn't readonly like before.

Maybe there is a solution but I'll have to think on it and maybe ask around

[cwsoots]

So looking at it what is going on is format of this module is different than how was previous. The module is not read only and this ext adds extra health fields, specifically temp HP and Adjusted HP. which are linked to database nodes within the xml. These fields obviously don't exist in the original record and are initialized when the record is opened. Since they aren't in the original they are written out to the moduledb/modules.xml. Since anything is written to this location, it marks the changed flag because technically they are.

Those fields show up hidden because this isn't a CT node and that's how it always was because you couldn't write to the db before so the ext hid them.

The solution, I'm not sure there is one other than removing those features from the NPC sheets entirely. It doesn't cause any problems per se other being an annoyance on that flag getting marked. I guess additionally I'd think this issue would also happen to other records for things that extensions are adding things to if module isn't readonly like before.

Maybe there is a solution but I'll have to think on it and maybe ask around

I appreciate the detailed analysis! I’ll stay tuned for your decision on the solution you choose, if any. Thanks!

[Dax Doomslayer]

Hi,
I'm trying to use this extension and I think I may be having issues. Clean campaign, running only this extension, the base "max hit points" is not properly calculating for a 2nd level multi-class PC (Lvl 1 Monk / Lvl 1 Fighter). The Monk was the original class chosen and it's hitpoints show. However, the Fighter hitpoints don't seem to be taken into account nor are they showing under the class drop down menu. I've attached an image that hopefully depicts the issue I'm having. Has anyone else experienced this?

Also, as a side note, the link on the Forge page for "Fix Discrepancy" seems to be broke.

Thanks.

[MrDDT]

Hi,
I'm trying to use this extension and I think I may be having issues. Clean campaign, running only this extension, the base "max hit points" is not properly calculating for a 2nd level multi-class PC (Lvl 1 Monk / Lvl 1 Fighter). The Monk was the original class chosen and it's hitpoints show. However, the Fighter hitpoints don't seem to be taken into account nor are they showing under the class drop down menu. I've attached an image that hopefully depicts the issue I'm having. Has anyone else experienced this?

Also, as a side note, the link on the Forge page for "Fix Discrepancy" seems to be broke.

Thanks.

I'm not seeing this.
Try changing the level from 1 to 2 for the class that is not showing the HP options below it, then change it back to 1 again. To see if that triggers it to show.

The link is meant to be a picture, and the picture is not showing correctly. That's why the link isn't working because it's not a link its a picture =P

[Dax Doomslayer]

Thanks MrDDT. That seemed to work for whatever reason. I appreciate the assist here!!

[rhagelstrom]

Version Update: v2.7.0

Support automation of HP reduction for 2014 Exhaustion
Fixed: Adjusting HP from 0 HP removes unconscious (likely) PHB p197
Fixed Forge documentation for linked image. Its also the same image that is one of the two associated Forge Images

[eporrini]

I am seeing the following error on load. It started with the latest update as far as I am aware of.

[3/22/2025 3:04:48 PM] [ERROR] Script execution error: [string "LifeLedger:scripts/manager_hp.lua"]:450: attempt to call field 'is2024' (a nil value)

[rhagelstrom]

I am seeing the following error on load. It started with the latest update as far as I am aware of.

[3/22/2025 3:04:48 PM] [ERROR] Script execution error: [string "LifeLedger:scripts/manager_hp.lua"]:450: attempt to call field 'is2024' (a nil value)

That would seem to imply that you are running a version of the exhausted extension < v2.9