Possible production timer bugging when using EMP on a factory

Bug #896311 reported by mevitar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Incomplete
Medium
Unassigned

Bug Description

When a factory gets disabled, but the sidebar tab doesn't disappear due to some reason, the blacked-out construction options can be still queued for production. This is only a Units Tab problem, because 3 factory types use that tab: War Factory, Naval Yard and Airpads.

##### STEPS TO REPRODUCE #####
1. Get a War Factory and a Naval Yard (or an airfield), so the unit sidebar won't disappear after using EMP on the War Factory.
2. Use EMP on the War Factory. NO UNITS SHOULD BE QUEUED FOR PRODUCTION BEFORE THIS, OR IT WON'T WORK.
3. Now try to start production of any of the blacked-out units. It works! The timer gets to roughly 40% done and then stops. You can only cancel the production, as the timer won't move any further no matter what you do.
4. Wait for the EMP to wear out. The unit is still at 40% done, but the timer doesn't move. Again, clicking on the unit does nothing, you have to cancel the production. After canceling, everything is back to normal.

##### ADDITIONAL INFORMATION #####
This doesn't block the production of anything else from the deactivated and reactivated factory - you can still order it to build any unit except the one locked on the sidebar, and it will work normally. The locked unit, however, won't get included in the production queue until you cancel its "production".

When the factory is disabled, if you try to queue more that 1 unit at a time, all the units will get the "constructing" timer activated, but every one of them will stop once they reach 40%, and become locked.

At the moment of reporting this, I don't remember if any money is subtracted for the "production" while the factory is disabled. I will post it after I check it tomorrow.

Revision history for this message
AlexB (alexander-b) wrote :

The cameo behavior has some flaws for EMP'd factories. Thanks for reporting.

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

When you build objects with broken BuildCat=, the engine auto-queues a second instance, which also gets stuck at ~40% - maybe it's related?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.