Player Features and Ideas Discussion

Yeah, would be nice to see how much longer I need to wait.
Also, do the same with the repairing of modules in space, and how much longer a Bomb launcher has until it is ready to fire again.

That's probably one of the better ideas. I fear, though, that it would suffer from the same 'overshoot' problem associated with lag that's rampant with modules (e.g. the extra 1/4, 1/2 cycle guns will do and the 1/2 cycle behind missiles show themselves at 99% of the time).
There's a lot of little things that could get added to the UI. This post coincidences chronologically with mine on the same subject and category of UI improvement.

I'm getting the feeling you're replying in response to my comment, but I was speaking particularly about the fact that there is serious module lag clientside that stems from serverside lag. That's reflected visually. Being told when your reload timers are active may cause the UI to lock your input out (like when that module is cycling the extra 1/2 cycle and I'm desperately mashing my guns to try to get them to activate on that frigate which is going to be out of optimal in .000000001s) since it assumes "oh, I don't need to send a request because I am absolutely sure something else is going on right now that would prevent that, so no reason to even try at all". The client does very very little extrapolating so reloading might even be linked to that lag already which the proposed change would make more visible rather than cause. (I haven't timed reloads at all, since I assumed they worked under a different system, but thinking about it makes me more curious as to whether reloads are also subject to lag failures even though they're automatic in most cases.)