Skip to content
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

Advantage and disadvantage logic fails on certain cases. #6

Open
pmfirestone opened this issue Feb 13, 2024 · 2 comments
Open

Advantage and disadvantage logic fails on certain cases. #6

pmfirestone opened this issue Feb 13, 2024 · 2 comments

Comments

@pmfirestone
Copy link

An example on page 20 of the 1e PSG fails:

My worst Save is Sanity at 14. So I get a 22 and a 56. So that would be a Crit Fail, but with Advantage it’s just a normal fail.

Expected behavior (in this case): normal fail.
Actual behavior (in this case): critical fail.

Advantage and disadvantage do not equal higher and lower rolls: there are cases where the "worse" result is the lower one, or the "better" result the higher one. Consider if both rolls succeed but the higher is a critical. When rolling advantage, the result should be a critical success, but in the current implementation rolling advantage in this case will report a normal success.

@pmfirestone pmfirestone mentioned this issue Feb 13, 2024
@pmfirestone
Copy link
Author

I've fixed this on my fork, but I did it by way of a major refactor of the types: StatRoll and SaveRoll are now a single type, Roll, and the change is propagated through the whole code base. Does that seem like a reasonable solution? I'll prepare a clean pull request for that fix this weekend.

@sbergot
Copy link
Owner

sbergot commented Feb 22, 2024

Yes it makes sense. I don't remember why I split the two to be honest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants