Incorrect count of units belonging to commander #1057
Comments
Zarel changed status from |
Zarel set resolution to |
Zarel commented Duplicate of #1248. |
Buginator changed milestone from |
Buginator commented Milestone 2.2.5 deleted |
Emdek changed resolution from |
Emdek changed status from |
Emdek commented Reopening, still happens in 2.3.0. |
Zarel commented Screenshot would be nice. |
anonymous uploaded file |
Emdek uploaded file |
Zarel commented I don't see anything wrong with the screenshot. Five attached units, four attached artillery; matches the commander exactly. |
Emdek commented Replying to Warzone2100/old-trac-import#1057 (comment:5):
|
Zarel commented Erm, give me one screenshot (from 2.3) in which mortars are counted... |
Emdek uploaded file |
Zarel commented Are you sure there aren't non-mortar units off-screen? |
Emdek commented Replying to Warzone2100/old-trac-import#1057 (comment:8):
But it's a bit confusing anyway, couldn't it be somehow shown in the list? Something like 5/10 + n (or maybe even more clear)? |
Zarel commented Yes, I could do something like that... |
Zarel changed status from |
Zarel changed resolution from `` to |
Emdek commented Replying to Warzone2100/old-trac-import#1057 (comment:10):
|
Zarel commented Feel free to start that Ideas thread. |
keyword_commander
resolution_invalid
type_bug
| by gundersen@...I've only used the commander in the campaign, so I don't know if the problem exists in multiplayer as well.
The problem is that when you select a commander from the commander menu (the star in the hexagon in the bottom left), then the commanders have an incorrect number of units assigned to them. It might say 6/14, but when you click the commander, a larger number of units are selected, and they all follow him around.
This might also be the case only if you bring a commander with you on an away mission.
I have no idea how to fix this problem, unfortunately. I might have a look at the source some other time to try to understand it.
Issue migrated from trac:1057 at 2022-04-15 20:03:32 -0700
The text was updated successfully, but these errors were encountered: