Use U**x timestamps for all in-game time displays

Shadowdancer

Shadowdancer
Since iti s apparently hard to accept or understand how the game displays times (mostly when the UK enters BST at this point), I propose to replace every time readout with good old and universal U**x timestamps, i.e., a count of seconds since epoch (1970-01-01T00:00Z).

To that end, display the integer value modulo 86400 for a 24h period. "The mission target will be present in the target system between 56100 and 57300."
 

Shadowdancer

Shadowdancer
PocketPsycho said:
Nice to see my bug report inspired you.
Click to expand...
Don't think you're the first one to report this (you're a year or two late), nor that you are the inspiration for this one. If you look closely, you will even find another slightly older thread on the bug reports forum at time of writing.
 

PocketPsycho

P
Shadowdancer said:
Don't think you're the first one to report this (you're a year or two late), nor that you are the inspiration for this one. If you look closely, you will even find another slightly older thread on the bug reports forum at time of writing.
Click to expand...

I'm aware of that, I even mention in my bug post that FDev posted that they were looking into this issue 9 months ago.
 

Nagual

Nagual
I rarely pay attention to time stamps in game, are they different from the in game clock which is UTC?
 

PocketPsycho

P
Nagual said:
I rarely pay attention to time stamps in game, are they different from the in game clock which is UTC?
Click to expand...

Yeah chat timestamps use your local system time. It'd be nice if I didn't have to keep adding 11 hours to the game clock to figure out when a message was sent.
 

Para Handy

Para Handy
Shadowdancer said:
Since iti s apparently hard to accept or understand how the game displays times (mostly when the UK enters BST at this point), I propose to replace every time readout with good old and universal U**x timestamps, i.e., a count of seconds since epoch (1970-01-01T00:00Z).

To that end, display the integer value modulo 86400 for a 24h period. "The mission target will be present in the target system between 56100 and 57300."
Click to expand...

Assuming you are not having a joke - are you joking?


(Unix freaks! [haha])
 
Last edited:

Shadowdancer

Shadowdancer
Para Handy said:
Assuming you are not having a joke - are you joking?
Click to expand...
Not completely serious, not completely joking. But since reading a clock seems to be challenging for some, it may be of advantage to use a system that makes everyone equally upset.

It does, by the way, make sense to have chat timestamps in local time, since it's more local to the singular player than the game world.
 

Para Handy

Para Handy
Shadowdancer said:
Not completely serious, not completely joking. But since reading a clock seems to be challenging for some, it may be of advantage to use a system that makes everyone equally upset.

It does, by the way, make sense to have chat timestamps in local time, since it's more local to the singular player than the game world.
Click to expand...


I'm of the opposite view - I would rather see the timestamps in UTC too - but then again I am used to working in UTC so what makes sense to me would be anathema to some others no doubt.

It seems to me that you can be chatting to people many time-zones away so logically it would make sense to all use the same setting, particularly in organizing a time to meet for a wing-up etc - so use UTC across the board.
 

PocketPsycho

P
Shadowdancer said:
It does, by the way, make sense to have chat timestamps in local time, since it's more local to the singular player than the game world.
Click to expand...

Not really, it makes more sense for the chat timestamps to be in the same time as the clock that is prominently displayed on the ship's HUD. Or do you commonly set your clock to Beijing time but have all your appointment details sent to you in US Westcoast time?
 
You must log in or register to reply here.
Back
Top Bottom