Opened 3 years ago
Closed 3 years ago
#6328 closed defect (fixed)
Negative amount of resource gatherers
| Reported by: | Langbart | Owned by: | Freagarach |
|---|---|---|---|
| Priority: | Should Have | Milestone: | Alpha 26 |
| Component: | UI – In-game | Keywords: | |
| Cc: | Patch: | Phab:D4274 |
Description (last modified by )
While playing the latest SVN version, the amount of resource gatherers in the top panel displayed a negative number.
In the attached replay, the issue can be observed for the blue Player around the 3min:10sec mark.
Attached replay: negative_resourceGatherers.zip
The cause of the problem might be related to my experiments with the cheat code wololo (see wiki/Manual_Cheats). I turned a few units of the red player into my people. But I remember that I also saw a negative number in Delenda Est because slaves can be captured there.
EDIT: When I change the ownership (via cheat code) of one of my enemy units to mine, the status of the unitAI changes. It subtracts a food gatherer from me (Player 1), but the number for my enemy (Player 2) does not change.
I assume the issues sits in ResourceGatherer.js or UnitAI.js.
Issue is reproducible for A24b.
Attachments (4)
Change History (10)
by , 3 years ago
| Attachment: | negative_resourceGatherers.jpg added |
|---|
by , 3 years ago
| Attachment: | negative_resourceGatherers.zip added |
|---|
comment:1 by , 3 years ago
| Description: | modified (diff) |
|---|
by , 3 years ago
| Attachment: | after_wololo_cheat_code.png added |
|---|
by , 3 years ago
| Attachment: | before_wololo_cheat_code.png added |
|---|
comment:2 by , 3 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 3 years ago
As far as I know this has been the case since its inclusion in r24357, but I see on the patch Phab:D3155 that I haven't noted it down.
comment:4 by , 3 years ago
(The problem is we want to change to IDLE before the ownership change actually happens, but that might put us in another state again (e.g. enemies in range).) I might be able to figure something to fix this.
Issue is reproducible for A24b.