[WARNING] setValue: Database node not owned

[Willot]

I had the problem with the client gradually slowing down and then (at end of the night, 3hrs session) it just froze up and crashed. (I hardly ever gotten the slow down before)
So I had a look back through the console log and couldnt see anything that stuck out, except I did have alot of

[WARNING] setValue: Database node not owned (combattracker.list.id-00001.death)

The number 00001 does change throughout the log

Is this something to be worried about or is it just one of those warnings that can be ignored?

[Zacchaeus]

I suspect that some extension is causing that. Test in a fresh campaign without extensions.

[LordEntrails]

Please remember to include critical information when reporting issues. See the link in my signature if you need a reminder of what is needed to isolate and reproduce issues.

[Kelrugem]

I had the problem with the client gradually slowing down and then (at end of the night, 3hrs session) it just froze up and crashed. (I hardly ever gotten the slow down before)
So I had a look back through the console log and couldnt see anything that stuck out, except I did have alot of

[WARNING] setValue: Database node not owned (combattracker.list.id-00001.death)

The number 00001 does change throughout the log

Is this something to be worried about or is it just one of those warnings that can be ignored?

That was a warning which can be ignored :) However, this was from the wound overlay extension of PF2, I updated Cupcakus's extension for that :) But the freezing is likely from something else, maybe :)

[Willot]

That was a warning which can be ignored :) However, this was from the wound overlay extension of PF2, I updated Cupcakus's extension for that :) But the freezing is likely from something else, maybe :)

Nice! I shall update forthwith!

Thats strange? No sooner had I read your post there was a violent flash of lightning and an appalling crash of thunder? (REF: Dead Eyes Opened, for the uncultured!)