Will this extension get updated on the forge? Looks like the bug fixes in this thread haven't made it up there yet. (I still see the gear for example)
Printable View
Will this extension get updated on the forge? Looks like the bug fixes in this thread haven't made it up there yet. (I still see the gear for example)
I realize that this extension hasn't seen a formal update in a while, and (like many others) I am running the 'fixed' 2.7.1 version by Mr. DDT. That being said, I did encounter a new console error in our session on Sunday night. I've attached the compiled logs (look in the -prev ones), and the error message is shown below.
The circumstances in which this error appeared are a niche use case. The players are all playing from NPC stat blocks at this time because they have been temporarily 'transformed' into yuan-ti. This error occurred on my host system, but I don't recall the actual steps to recreate it. I am assuming that it's related to Life Ledger, as it's mentioned in the error message.
[1/18/2026 8:41:05 PM] s'ActorManager.getTypeAndNode/getTypeAndNodeName - DEPRECATED - 2025-04-22 - Use ActorManager.isPC/isRecordType/getCreatureNode/getCTNode'
[1/18/2026 8:41:05 PM] s'ActorManager.getTypeAndNode/getTypeAndNodeName - DEPRECATED - 2025-04-22 - Use ActorManager.isPC/isRecordType/getCreatureNode/getCTNode'
[1/18/2026 8:41:05 PM] s'ActorManager.getTypeAndNode/getTypeAndNodeName - DEPRECATED - 2025-04-22 - Use ActorManager.isPC/isRecordType/getCreatureNode/getCTNode'
[1/18/2026 8:41:05 PM] [ERROR] Handler error: [string "LifeLedger:..s/manager_action_damage_ll.lua"]:317: attempt to index local 'nodeTargetCT' (a nil value)
Great extension. Thanks for this.
Started getting this error after an update this weekend:
Attachment 66740
Occurs when a NPC is in the tracker and on the map, whenever a player moves. Multiple errors all at the same time.
Occurs with both the version on the Forge, and Mr. DDT's updated version.
Let me take a look and I will get back to you.
I'm not getting this error. You mind giving me the campaign file to see if I can make it happen to see what is going on?
Are you using any other exts that might be causing a conflict?
Is this also happening on a new campaign or just this one?
Double checking, what is the version # of LL you using?
It appears to be some sort of conflict with Aura Effects.
I noticed that it happens whenever something moves in or out of the aura of protection on the Paladin in my game. The error stopped when I disabled Aura Effects, though I still got the same error (just one instance) on load after I turned it off.
Yeah, I have a good number of extensions running - I was going to set up another campaign and test, but I don't have the time atm.
Using V.2.7.1 from the forums here - but the same error occurred with the version on the Forge, too.
For reference there is a conflict between mad nomad's combat helper and life ledger.
To recreate just have those 2 extensions enabled. Show combat helper must be on.
Add a tough onto the combat tracker and give it 5 wounds. Then cycle a round though the CT. You will see that the max HP of the tough is decreased by the amount of wounds each time you cycle.
I'm pretty sure this isn't something that can be fixed life ledger side so is more for reference in case others encounter the same issue.