3 replies to this topic

[Bigman]

Hey guys.

Just for a little shits and giggles, i wanted to check the MWO clock to see what day exactly it is. Unfortunately i found a little bug.

It is currently 29/2/2016 here, and it's naturally showing 29/2/3051. Slight problem. 3051 aint a leap year. Saw it, Checked it. Had a giggle, and am now posting it here

Catcha later guys

[Thorn Hallis]

It might not be on Earth...

[Paigan]

Thorn Hallis, on 29 February 2016 - 05:16 AM, said:

It might not be on Earth...

That's not relevant:
The calendar system might have originated on one particular planet, but be simply used across many systems as a standard.
Just like the year 0 has no actual relevance any more (afaik not even to Jesus' birth as it turned out). It's just a standardized metric.

---
My take:
Leap year logic/offset will get patched/resetted/whatevered in the future. Problem solved .

Edited by Paigan, 29 February 2016 - 05:27 AM.

[D V Devnull]

Heck, their clock should already say 3053... It was already 3049 when it was 2012 here, and four years have passed, not just two. There's supposed to be a 1037-year difference, and it's unfortunately acting like only a 1035-year difference at the moment, which is some serious "Fourth-Wall Breakage".

~Mr. D. V. "That clock is way beyond overdue for repairs." Devnull