If you have purchased a Legacy or Starter Pack, please see this thread for instructions on how to claim your items in-game. (Please see the yellow text in the linked thread for instructions on creating a Reman.) (Not seeing your pack in-game? Please see the lime-green text in the linked thread above for information.)
If you have additional questions about the Legacy or Starter pack, please read this FAQ.
Thanks SO MUCH for all your support, and we'll see you in-game!
- The Star Trek Online Team
***Resolved Issues***
"Login failed for unknown reason" error
Missing additional character slot for current/ lapsed Gold Members
Slow patching in the launcher
A bug that involved Romulan Liberated Borg captains and their skills once they chose an ally
Some characters were stuck in a loading screen with a "Server Not Responding" message
As we all know, after Dstahl left Cryptic, the "Engineering Reports" kinda left with him. We've had very little in the form of recurring communication from Cryptic since his departure, other than the 15 or so "blog reports". While yes, the blog reports have been quite informative, and the graphics that go alongside the reports have been helpful, I'd like to take this opportunity to provide a suggestion to keep your customers (and potential customers) fairly updated on what's going on:
A list of the "main developers" for Star Trek Online, such CapnLogan, Heretic and Gozer, could have their very own "blog reports", on a fairly regular basis (weekly or semi-weekly updates), and in each report they be allowed to share the latest information in regards to what is actively being worked on, things that are intended for release in the relatively "near future" etc.
Using my examples above it would be:
- Weekly update on what's being worked on in terms of new ships (CapnLogan)
- Weekly update on what new game systems are being added/changed such as the DOff system (Heretic)
- Weekly update on upcoming/new/changed STFs (Gozer)
All 3 of the above, do post somewhat frequently in the forums, and the occasional "tweet leak" on Twitter. But my suggestion involves keeping the visitors to -this- site, somewhat informed so that you don't have to go browsing through dozens/hundreds of forum threads, or looking through various Twitter feeds to get the information.
All of the above in regards to new "blog reports", would ofcourse be subject to if the developers are allowed to release such information by the Executive Producer and other "higher ups" in the command hierarchy.
Linear Mode
