We will be bringing down Star Trek Online this morning in just few minutes for maintenance and to apply a new patch. Patch notes can be found here, and we expect this maintenance to only last for 2 hours. The test server may also be unavailable during this time.
Thanks for your patience and understanding,
- The Star Trek Online Team
EDIT: The patch notes state "general server stability improvements" -- this means there are no content updates/ changes in it, and the goal is to improve the experience in-game in terms of "lag", connectivity, etc. Thanks for your patience and understanding!
--------------------
Brandon "BranFlakes" Felczer | Community Manager
Follow us on Twitter: @trekonlinegame | "Like" us on Facebook
Follow me on Twitter: @PWE_BranFlakes If you wish to speak to someone on the community team, file a "Forums and Website" support ticket here.
Last edited by pwebranflakes; 02-01-2013 at 04:59 AM.
Join date is wrong, I've actually been around since Beta.
My fleet means something to me, it is a home. But because it has less than 25 members and I don't want to be a nameless face among 500, I'll never reap the rewards of an upgraded starbase. Not cool.
No surprise, things have been hugely unstable since the patch yesterday. Guess they figured out how to fix it. What's an anniversary event without a little unexpected downtime, eh?
No surprise, things have been hugely unstable since the patch yesterday. Guess they figured out how to fix it. What's an anniversary event without a little unexpected downtime, eh?
Probably thanks to the million or so balloons flooding ESD and The First City.
Join date is wrong, I've actually been around since Beta.
My fleet means something to me, it is a home. But because it has less than 25 members and I don't want to be a nameless face among 500, I'll never reap the rewards of an upgraded starbase. Not cool.
I just glad I got the main event done on my chars last night, but there was a bit of instability last night I noticed. The balloons even started giving my system trouble...thats a first for me.
It appears that it was probably lag, considering how many people were trying to log in at the same time, as all the instances were full...at one time I saw the queue to log in at over 5000 people..