-
-
Notifications
You must be signed in to change notification settings - Fork 995
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
Display max_attacks in the unit sidebar #2667
Comments
Also, the movement_used for an attack might be good to show (if different from the default). |
if this doesn'go into 1.14 coud can also do this in an addon by using luas theme_items hook. |
I think this actually can't go into 1.14 solely because of the |
Added: test case
@CelticMinstrel Could you explain why you think this isn't backportable? If someone replaces or wraps wesnoth.theme_items.unit_weapons, then...what? |
I think it's not backportable because I expected it would be adding a new element to |
It just adds another line to the existing |
Yeah okay... in that case, I'd say it's backportable. |
Need to backport ad0867f too for the |
Will probably need work for the sidebar changes being discussed in https://www.wesnoth.org/irclogs/2021/03/%23wesnoth-dev.2021-03-18.log |
Where does this stand? Probably too late for 1.16.0, but I understand there are no further planned releases for 1.14 so back-porting isn't a concern there. None of the standard campaigns have units with more than one attack per turn, do they? This is mainly for UMC, right? |
What? Isn't it already done? The commit jostephd linked appears to be on master, at least. |
Sorry, yeah, it does seem to be - I was just focused on all the discussion about back-porting to 1.14 which is no longer relevant. In that case, closing. |
Since 1.13 we have the option to set max_attacks via [effect]. Unfortunately, it is not displayed, if the unit has more than one attack per turn. It might be reasonable to display the number of attacks per turn in the unit sidebar.
Maybe we can get something like "Attacks (2)"
The text was updated successfully, but these errors were encountered: