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

Better Attack descriptions #351

Open
tukkek opened this issue Sep 28, 2022 · 0 comments
Open

Better Attack descriptions #351

tukkek opened this issue Sep 28, 2022 · 0 comments
Labels
Milestone

Comments

@tukkek
Copy link
Owner

tukkek commented Sep 28, 2022

A list of Attack +3 (1d6+2) becomes less useful the more attacks there are. A better format would be "Bite, claw x2 (probable miss)", with scratch/hit/wound/injury/death if a hit is more probable. This would require changing the Target preview, ChanceNodes, StatsScreen, Attack selection... which may turn out to be a decent-size change as it would involve having Target and null-Target scenarios API-wise.

BattleAi-side, this would enable culling Attacks rather than branching them into the decision tree (or at least for Attacks without damage Effects) - it's not ideal but it's trivial enough to warrant the performance gain. In the case of Effects, cull down to one per effect (plus one for non-Effect, if any).

To achieve obth goals, this would involve a numeric and textual return. AttackResolver would seem like the most likely unit for all that.

@tukkek tukkek added the Fight label Sep 28, 2022
@tukkek tukkek added this to the Middle-term milestone Sep 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant