Originally Posted by
Moon Wizard
Ok, I wasn't able to recreate; but after some more thought, I think I've tracked down the situation.
It has to do with the fact that sometime during his development, SilentRuin set his player user as the owner of the combat tracker node (and thus all children). This never happens during standard usage of the default rulesets. Due to that change, a call that was running on both host and client was triggering that normally just failed quietly on the player client, since it didn't own the combat tracker node. Since SilentRuin's player user is now the owner, it was able to change the combat tracker when the PC was removed.
I'll add a check in the base ruleset code to only do that for the host just in case someone ends up in that state again; but it won't be available until the next release.
Regards,
JPG