You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
when you are using the mod the injured status above the token hides the height values. this happens in pf2e but it could happen in other systems.
To Reproduce
Steps to reproduce the behavior:
type in height
make the creature damaged
see the conflict between height value and the injured status.
you cant see the height value. which is very useful for gms and players.
Expected behavior
if a height value is used it should be above the status value.
Screenshots
Game Specifics (please complete the following information):
Game System and version: [e.g. dnd5e 2.4.1]
Module Version [e.g. 31.7.11]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
There is the "Elevation Tooltip Position" setting to change the position the tooltip gets rendered.
Alternatively, you can change the estimate's vertical position by changing its Height to a negative value under the Style Settings menu.
E.g. this is what -20 looks like
There is the "Elevation Tooltip Position" setting to change the position the tooltip gets rendered.
Alternatively, you can change the estimate's vertical position by changing its Height to a negative value under the Style Settings menu. E.g. this is what -20 looks like
thank you doing +30 on it looks good. do you think this could be the default? as it fixes that issue.
Describe the bug
when you are using the mod the injured status above the token hides the height values. this happens in pf2e but it could happen in other systems.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
if a height value is used it should be above the status value.
Screenshots
Game Specifics (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: