Log in

View Full Version : TEST - player health bars



SilentRuin
April 6th, 2021, 04:01
I had two players get hit hard and both times the player reported their map icon showed 1/2 heath bar showing on token when combat tracker and other players and GM tokens showed 1/8 health which was correct. After they healed or got hit again it self corrected. Not sure if it was random or not. Just FYI - was running TEST.

Griogre
April 6th, 2021, 05:23
It's probably the same bug in live. That's a script triggering issue where you'll see the status bar/dot and status color text right for every other character but yours will lag one update. The DM always sees it correctly. The hit points are are correct on the tracker and character sheet its only on the status color and dots/bars.

SilentRuin
April 6th, 2021, 15:52
It's probably the same bug in live. That's a script triggering issue where you'll see the status bar/dot and status color text right for every other character but yours will lag one update. The DM always sees it correctly. The hit points are are correct on the tracker and character sheet its only on the status color and dots/bars.

Thanks for info - as long as they are aware of it already I'm good.

Moon Wizard
April 6th, 2021, 17:09
Just pushed ruleset updates that should fix in included rulesets.

Regards,
JPG

SilentRuin
April 6th, 2021, 17:44
Just pushed ruleset updates that should fix in included rulesets.

Regards,
JPG

Note that did not fix the blackout you said was coming in next release.

Moon Wizard
April 6th, 2021, 19:36
I said that the blackout fix was in the next release build of FGU. This was only a small set of ruleset updates.

Regards,
JPG

SilentRuin
April 6th, 2021, 19:47
I said that the blackout fix was in the next release build of FGU. This was only a small set of ruleset updates.

Regards,
JPG

Sorry was not paying attention to what it was updating - looking forward to testing it out :)

Griogre
April 6th, 2021, 22:08
Too many releases to keep track of ... :)

@JPG ruleset release seems to have squashed the update bug, thanks. :)