> > > Hi Captains. Thank you for your patience! We've got our top Engineers checking in on the errors you are reporting. More updates as they become available, so watch this announcement section. < < <
Update! We are aware of the queues players are currently in and are working to get you all in as fast as possible.
Update! We are aware that some players are seeing an error upon login and are working to resolve this.
Jolan tru Captain!
Welcome to Legacy of Romulus!
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.)
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
It's definitely a work in progress, but I don't yet know how frequently I'll be able to add stuff. Hope everyone agrees it's better to release stuff in little bits and pieces rather than hold it all up and release it at once.
I agree with this as it allows us (the end users) the opportunity to test and report issues quicker; and with a smaller group of items, there's more of a chance it'll get corrected quickly then if there was a mountain of stuff released in one huge push.
Formerly known as Armsman from June 2008 to June 20, 2012
PWE Drone says, "Your STO community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
There was an issue where the Journal incorrectly said that some didn't qualify when they did--that was resolved and is on Holodeck as of today.
Every other mission I've checked (since the fix went live) legitimately didn't qualify, whether because it lacked enough plays or because the average play time was too short.
Is dropping the mission or not finishing it while testing it post-publish affecting the average play-time?
There was an issue where the Journal incorrectly said that some didn't qualify when they did--that was resolved and is on Holodeck as of today.
Every other mission I've checked (since the fix went live) legitimately didn't qualify, whether because it lacked enough plays or because the average play time was too short.
I'm gonna have to say there's an issue with how the average play time is calculated then. I've played multiple missions that have the "not qualify" label yet still take far longer than 20 minutes to complete. Some of these have dozens of reviews as well.
If you go to the general Foundry forum you can find a lot of people who say their missions are much longer than 20 minutes yet still do not qualify.
What I'm wondering is if author plays and drops (author and player) are affecting the average which cause the mission to initially start out with an extremely low play time.
Imagine an author play testing a mission (published for testing). The author will be playing incomplete versions, and "F"ing through dialogue continuously causing lower than normal playtimes. All this punishes the author who wants to be 125% sure that everything is perfect.
Implemented a change to possibly address the game client failures reported on machines with Intel integrated drivers.
This may address crashes, black-screen hangs, "Display driver has stopped responding and has been reset" system messages, and blue screens.
This change will also assist with gathering information about the failures should they persist.
Thank you. That's the least I can say after how much I've posted over this issue. :-)
Quote:
Significantly increased the damage of the Kinetic Cutting Beam, but drastically reduced the damage and crew damage of the combo with the Assimilated Tractor Beam.
Interesting. Although I seem to be in the minority that didn't mind how it worked before. Not a problem though as I like it either way. The current (soon to be old) version is neat as a sort of finishing move, but a more balanced overall setup is still fine by me.
Last edited by tsurutafan01; 01-10-2013 at 03:54 PM.
Is dropping the mission or not finishing it while testing it post-publish affecting the average play-time?
Dropping absolutely doesn't count. And if you don't finish the mission, it's not a completion time, so that wouldn't count either.
There may be some other issue here, but it's neither of those. We are investigating these reports, but as I said, I've checked the behind-the-scenes number for playtime and it has come up short on all the examples.
Dropping absolutely doesn't count. And if you don't finish the mission, it's not a completion time, so that wouldn't count either.
There may be some other issue here, but it's neither of those. We are investigating these reports, but as I said, I've checked the behind-the-scenes number for playtime and it has come up short on all the examples.
Well, something weird is going on. I was absolutely paranoid about post-publish testing of a new mission called "The Dance of the Dead." It should take at least half and hour, but more like 45 minutes.
My first 5 reviews (in the review stage) were 4 complete playthroughs and 1 guy who had to drop because a npc was nowhere to be found.
My mission didn't qualify for rewards until it had 24 plays. It would be impossible to play this mission in less than 15 minutes, even if quickly pressing f at every spot of dialogue.