Huxley: The Dystopia gets new teaser site with countdown

by James Egan on Apr 25th 2009 12:00PM

Sci-Fi, Huxley, MMO Industry, New Titles

Huxley: The Dystopia is one of the new breed of games about to hit the massively multiplayer online world -- a hybrid first person shooter and sci-fi MMO, built on Unreal Engine 3. Massively took a good look at Huxley at GDC 2009, which we (naturally) feel is a solid starting point to catch up with what this game is shaping up to be, given its long hiatus between the early announcements and its re-appearance in the games journalism sphere.

So what will come of this splicing of FPS and MMO? We're not sure how well-received titles like Huxley: The Dystopia and Global Agenda will be, but it'll certainly be interesting to see what these games will add to our online gameplay options. In the meantime, Huxley: The Dystopia has launched a teaser web site with a countdown clock showing just under 30 days. We don't believe this is an actual launch countdown, but it's expected that more game info will be revealed at that time. If you're devouring everything you can about this particular game, you'll want to have a look at the Huxley teaser site and its front page video showing off more of the game.

[Via IGN]

Source

Tags: gdc-2009, huxley, huxley-the-dystopia, ijji.com, mmo-industry, mmofps, new-titles, sci-fi, teaser-site, unreal-engine-3

Reader Comments (2)

Flash code in the page says: "openDate=20090506183000"

That's something ;)

yeah.
the javascript does something similar but utterly non-functional.
i have the suspect that they may be good on content creation but if they program as they made the javascript...
try to read it! it's completely senseless, as if they tried to do something and then weren't capable of doing so in time. they seem to be complete incompetent idiots!

i know the problem: they wanted to get the time of now (read with new Date() in javascript) and they tried to do it by reading the client's time. then they realised that the client might have a wrong time set. in fact, they should have used a script that gets the time from the server, which is a reliable source.
then they tried to set the countdown date (20090506) but they used a completely senseless script, so they failed in this, too. then they realised there are timezones and that the client might not be set to the correct one.... so, in the end, the countdown is completely wrong and restarts always from 30 days.
the CEO of the company might have said: publish it NOW! make it work and publish it NOW!!!

*giggle* this promises very bad things... AOC docet.