49 replies to this topic

[TexAce]

Bryan just tweeted me its a typo

https://twitter.com/...989622930386944

To clarify: I am NOT against a rollback, but only if its communicated appropriately, because I think seeing the clans in 2015 is more realistic than anything that was mentioned before by staff.

[Nehkrosis]

damn, i was almost hoping we'd get a proper roll-back.

[NeonKnight]

I find it especially funny, because 3050 was a perfect, and I mean PERFECT fit for our current time.

According to websites:

http://henry.pha.jhu...nHTML/3050.html

http://www.timeandda...th=11&country=1

3050 meshes perfectly with the year 2013. Today is November 4th (Monday), and in 3050, November 4th is ALSO a Monday.

Putting the time to some other year would lose that fun quirk

[Lightfoot]

Still says 3050 on the page, http://mwomercs.com/clock .

[Whatzituyah]

Lightfoot, on 04 November 2013 - 08:40 PM, said:

Still says 3050 on the page, http://mwomercs.com/clock .

That's because they fixed the typo.

[Roadbeer]

Lightfoot, on 04 November 2013 - 08:40 PM, said:

Still says 3050 on the page, http://mwomercs.com/clock .

Does it? Or is that what they want you to think?

[Stonefalcon]

Roland, on 03 November 2013 - 09:22 AM, said:

In galactic time, daylight savings time involves falling back two years.

That was the shortest galactic daylight savings ever, it just sort of flew by didn't it?

[GalaxyBluestar]

[Kyle Polulak]

I just...can't...stop...laughing.

The clock display of 3048 was a typo, since calendars are not calculated that far. The weeks line up, but the calculation did not. This clock isn't actually set to 3050 as no computer could handle the time; so we just display it for 'fun' as Bryan mentioned. The clock on our servers is set to 2013 and will always be set to real UTC time.