Star Trek Online: State Of The Game Report

26 Feb 2010 at 16:21:13 by Bill Vaughan

Cryptic Studios has released its latest state of the game report for Star Trek Online.

The team talks about a number of issues including the tremendous amount of effort needed to provide support for all the STO players out there, now that the game is live. Not only that, but the worker bees are also making sure the game is stable and that any urgent adjustments are implemented quickly.

The queues experienced by players at the beginning should now also be much shorter, thanks to the “metric ton of hardware and man hours” that's been thrown at the problem, according to the report.

There's a number of things on the to-do list, many of which were mentioned in our recent interview with the game's executive producer. Among them are a respec facility, a death penalty, better auto-fire and a difficulty slider. Feedback is constantly being gathered by the community team, assessing what players want from STO.

The game's first post-release raid, Infected, is almost ready for release, which will be closely followed by the other raids Cryptic has lined up (find out more about them in our earlier news). The first major update is also coming along nicely, and should appear on the test shard soon. Beyond that the slate is pretty clear because developers are basing future content on the wants and needs of the players.

“We haven't set the future of STO's content into stone because so much of it will be determined by you, but we're laying out what we'd like to focus on for the next 6 to 12 months.”

So far, the basic plans are to explore the Undine, make use of the Genesis System, add more missions and more playable factions. But that's just the start:

“Ship interiors, more bridges, crew quarters, First Officers, Fleet advancement... You have subscribed to a service that delivers a universe unending, and we shall see that universe populated with compelling content or, by the Prophets, we will die trying.”

Drop by the report for more musings from the development team.

Comment