-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feel no pain (FNP) for melee/fighting #3
Comments
FNP is implemented for shooting. Are you requesting FNP be implemented for melee/fighting? |
Yes |
Implementing FNP with the smarter fighter strategies probably won't happen. I can take a look at how painful it would be to implement FNP for "Always Strike/Parry". |
FNP in melee is a big pain with an analytical approach (as opposed to Monte Carlo). I can try to take a look to see the least painful way to implemented for the simple "always strike/parry" fighter strategies. |
Awesome, thank you!
…On Fri, Aug 11, 2023 at 4:39 AM Jacob Egner ***@***.***> wrote:
FNP in melee is a big pain with an analytical approach (as opposed to
Monte Carlo). I can try to take a look to see the least painful way to
implemented for the simple "always strike/parry" fighter strategies.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEGRAPWRXDHSVY5WTKY4GDXUUTGTANCNFSM6AAAAAAYPUR6C4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
It's pretty frequent that 5+ or 6+ FNP rules are provided to operatives, and would add to their approximate wound count.
One thing to note is that there's a complexity to account for given that FNP rolls in some ways stack so a unit that's dealing less damage per hit would be less likely to kill a unit with a 5+ FNP than anther unit that's dealing more damage per hit, even if the total damage produced for retained dice across both scenarios is equal. The reason for this is because FNP rolls are performed at the end of each hit, not at the end of combat itself.
The text was updated successfully, but these errors were encountered: