-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spell Library health bars don't register healing when using default Simple5e macros #4
Comments
I misread your issue initially.. Simple 5e uses the same health bar logic as the spell library. I will test on a fresh copy of Simple5e and update this thread tomorrow to see if I can duplicate the issue. |
I wrote some clarifying text on Discord. I'm no longer confident that this is a bug in the Spell Library. |
Indeed, I think you're right. This is due to the use of the Approximate Bar Logic I use and Merudo mirrored. This logic is deliberately simplistic to be approachable and meant to generally protect precise HP values from being exposed to players by accident. If you want to have smarter bar logic that will display the correct bar depending on the owners of the tokens, replace the following three lines in the
With the following:
If you prefer this logic everywhere in your campaign to the simpler default logic, you could further replace the bar logic in the |
Thank you, I will test this out later today and see if I can break it. 😆 I can almost follow this. It's like reading French and getting the context but not the details! |
I hope I understand how this is working. I think this is being caused by the spellbook, and isn't a bug in Simple5e.
If I use a spell to damage a PC token, the health bar is displayed. (I like this.)
But if I heal with the Simple5e 'Heal Damage' macro button, the health bar is not updated.
I think Simple5e doesn't use health bars as it doesn't use macros to target damage on other tokens.
This leaves my token with an indicator out of sync with my actual health. When I heal via the spelllbook it works fabulously, of course.
Aloha.
The text was updated successfully, but these errors were encountered: