-
-
Notifications
You must be signed in to change notification settings - Fork 1k
-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Quenoth Fighter unit line multi-attack implementation needs improvement #7447
Comments
SO, this is not at all intuitive or explained. If they make the 9-2 attack, their turn ends. If they make the 9-1 attack first, they can follow it up with the 9-2 attack.
The unit text doesn't explain at all how the ability actually works, and if you're a normal player who always uses the better attack first, you'll likely never figure it out. |
Again, the heading was misleading. As best as I can see there are two issues:
|
I have no idea how it's supposed to be implemented. Since the order of attacks affects the number of attacks, which I assume wasn't intended. |
The UI bug is #7367, but I don't see a bug for the gameplay. Where's the bug for a unit with |
This is intended? Should have an additional key to set that possibility to yes/no |
So that's what those two reports are about, I didn't know they would impact main-line units. Could this be closed as duplicate then, or treated as a campaign-specific subset? |
I think I'd probably say this is something that depends on those but might not be equivalent to them…? |
Game and System Information
Description of the bug
For some reason, the Quenoth Fighter line of units appear to have gained extra attacks that don't do anything. (I don't know what was intended, but at least on the version I'm running, they merely have copies of their attacks that deal less damage)
Steps to reproduce the behavior
No response
Expected behavior
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: