Bug "estimated" time of building bridge
Posted: Mon Nov 24, 2025 4:46 pm
Hi,
I wasn't sure where to post this, so I'm guessing here at Tech Support? Please do let me know or move the post if it should be under a different thread.
While replaying the Tutorial "Engineering Operations", I realized that when chaining a "build brigde" order behind a "move" order will have a small bug:
Firstly at 7:15, I send it an order to Move down and the arrival order as "build a bridge", it will give a time (8:04) of finishing building the bridge. This will be the correct time.
Once it arrives (during the turn resolution at 7:43), the estimated finish time for the bridge as changed in the Unit log, Engineering tab and on the map to 8:16.
However, we can see that the build was still finished building at the original time of 8:04.
Not sure what's the issue. Is it adding an extra command delay between the two orders by mistake when it arrives when calculating the time? Anyway, hope it helps to fix it, I was experimenting on how to deal with chaining commands with engineering operations and caught that weird behavior.
Cheers.
I wasn't sure where to post this, so I'm guessing here at Tech Support? Please do let me know or move the post if it should be under a different thread.
While replaying the Tutorial "Engineering Operations", I realized that when chaining a "build brigde" order behind a "move" order will have a small bug:
Firstly at 7:15, I send it an order to Move down and the arrival order as "build a bridge", it will give a time (8:04) of finishing building the bridge. This will be the correct time.
Once it arrives (during the turn resolution at 7:43), the estimated finish time for the bridge as changed in the Unit log, Engineering tab and on the map to 8:16.
However, we can see that the build was still finished building at the original time of 8:04.
Not sure what's the issue. Is it adding an extra command delay between the two orders by mistake when it arrives when calculating the time? Anyway, hope it helps to fix it, I was experimenting on how to deal with chaining commands with engineering operations and caught that weird behavior.
Cheers.