I was wondering if anybody else has been stuck in Fire Delay and how they got out of it?
Doesn't matter how often I reload or refresh it just starts counting down from 1 minute to zero and then nothing happens.
I did try the help IRC but no one was active, and I have started the process to join the bug reporting area but I am not able to do much until I get my verification email sent to me so I can gain access.
My question is, how come this never affects the cockpit timer?
I will use the normal <1 minute server delay as an example.
Whenever I go hunting and my fire delay counter reaches 0, I cannot immediately fire again because any click/refresh will make the timer jump back to 60 seconds left. I'm talking here about the normal server delay that happens every time for every action (e.g. crafting, installing doors etc.) and always resolves itself within up to 1 minute (you can either just wait the full extra minute, or keep hitting refresh until it's gone). Let's call this the Groundhog Minute.
However, this perfectly normal issue, that I've learned to live with, never happens with cockpit timer. Why is that? If you are in the cockpit and looking at the timer up to when it reaches 0, the screen quickly refreshes to update your location, and you can immediately click to perform another action or go to another screen and the timer will not reset to 1 minute. But if you are not in the cockpit and instead looking at the side-bar travel timer when it reaches 0 (as you arrive at your destination), any click to any other screen than the cockpit will always reset the counter to 1 minute. You can now either wait the full minute or keep refreshing the screen for up to one minute, OR you can go to the cockpit to immediately to kill the groundhog minute.
So, what makes the cockpit timer so special, and can we apply this special something to the side-bar timer to fix the groundhog minute and perhaps even the groundhog day issue?
The cockpit has extra code in it to process any remaining travel actions outside of the normal way in which actions are triggered for processing (via cron job). Other things don't... it could be added in principle, but it also has the potential to create problems when the cron job is running as normal, so I am not going to.
"On two occasions I have been asked,—"Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question."
- Charles Babbage