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
Hi, I was playing yesterday and was seeing some confusing behaviours on the rolls using better rolls but since I'm new to swade, I'm not sure if there is a problem or not.
the image below shows a melee attack made by an extra against a wildcard character.
this roll was made without "auto roll trait and damage" ( I clicked on the card to roll attack and then damage after)
The attack succeeded with 1 raise, so the damage should be increased by 1d6, correct?
however, as you can see the raise die was not applied.
This new role however, was made with auto roll train + damage active
See how the raise die is being included ?
Do you know if this is a bug?
regards
The text was updated successfully, but these errors were encountered:
PalaNolho
changed the title
Raise damage missing?
[Bug?] Raise damage missing?
Feb 18, 2025
If you want to roll damage manually you need to hit the left button for normal damage and the right one for a raise. It doesn't force a raise on you if you are doing things manually.
There should be also a tool-tip when you hover over the buttons.
Closing this as this seen to work as designed (if it is a good design nor not is not another matter)
Hi, I was playing yesterday and was seeing some confusing behaviours on the rolls using better rolls but since I'm new to swade, I'm not sure if there is a problem or not.
the image below shows a melee attack made by an extra against a wildcard character.
this roll was made without "auto roll trait and damage" ( I clicked on the card to roll attack and then damage after)
The attack succeeded with 1 raise, so the damage should be increased by 1d6, correct?
however, as you can see the raise die was not applied.
This new role however, was made with auto roll train + damage active
See how the raise die is being included ?
Do you know if this is a bug?
regards
The text was updated successfully, but these errors were encountered: