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

PF2e Treat Wounds Macro always rolls risky surgery damage, even if not selected #16086

Closed
maplealmond opened this issue Aug 17, 2024 · 2 comments · Fixed by #16099
Closed

PF2e Treat Wounds Macro always rolls risky surgery damage, even if not selected #16086

maplealmond opened this issue Aug 17, 2024 · 2 comments · Fixed by #16099
Labels
bug Functionality that is not working as intended

Comments

@maplealmond
Copy link
Contributor

The PF2e Treat Wounds Macro game.pf2e.actions.treatWounds({ event, actors: [token?.actor ?? actor ?? game.user.character].filter((actor) => actor) })

If used by an actor who has the risky surgery feat, this macro will always roll 1d8 damage, even if the actor has not checked the risky surgery option.

@ammalagonc ammalagonc added the consolidated A consolidated issue made from multiple other issues label Aug 17, 2024
@ammalagonc
Copy link
Collaborator

Hello, will be tracking this issue via #15855. Please use it to track any progress towards this.

I'll close this issue now. Thanks!

@ammalagonc ammalagonc closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2024
@stwlam stwlam removed the consolidated A consolidated issue made from multiple other issues label Aug 17, 2024
@stwlam stwlam reopened this Aug 17, 2024
@stwlam
Copy link
Collaborator

stwlam commented Aug 17, 2024

Keeping this as an independent issue

@stwlam stwlam added bug Functionality that is not working as intended and removed data gap labels Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality that is not working as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants