I appreciate the input from all of you but I prefer to play the game when I have time and not when the game thinks it's okay to cooperate. It's also nice to see a fairly quick response from their customer support acknowledging the problem and stating the developers are looking into it.
But no mention of it in the patch notes or a fix before the end of the event I find rather disappointing as a customer. Especially because it's the second time the character got part of an event bugged out.
Did you get a message from Support that this was being looked into? I have not seen any official word that they even acknowledge a problem exists.
If they just came out and said, yep, this is busted and we don't know how to fix it for this year, I still would not be happy it is broken, but at least I wouldn't be upset with how it was handled.
Yup and I have seen it mentioning here on the forums as well but going through the thread I don't see it anymore. Anyway this was the response I got.
Thanks. The resident rules hawk will probably have felt a disturbance in the force (even though that message from support is literally the copy/paste they use for most bug reports), so your post might *poof*. Which doesn't mean what support said isn't true, but it would still have been nice to have the bug mentioned at least once in the known issues over the past month.
With the anniversary event ending in less than a day ended it is obvious it won't be fixed this year. If it shows up again at the start of the 15th, though...well, we'll have to see what happens then.
0
rattler2Member, Star Trek Online ModeratorPosts: 58,577Community Moderator
As mentioned earlier, Private Correspondence is to remain private. This is to avoid potentially revealing private information. Even if something doesn't have any potentially account compromising information, ANY private coorespondence is still considered private and will be redacted. Please refrain from posting anything you got in in game E-Mails or Private Messages.
Comments
Did you get a message from Support that this was being looked into? I have not seen any official word that they even acknowledge a problem exists.
If they just came out and said, yep, this is busted and we don't know how to fix it for this year, I still would not be happy it is broken, but at least I wouldn't be upset with how it was handled.
Private Coorespondence Redacted - rattler
Thanks. The resident rules hawk will probably have felt a disturbance in the force (even though that message from support is literally the copy/paste they use for most bug reports), so your post might *poof*. Which doesn't mean what support said isn't true, but it would still have been nice to have the bug mentioned at least once in the known issues over the past month.
With the anniversary event ending in less than a day ended it is obvious it won't be fixed this year. If it shows up again at the start of the 15th, though...well, we'll have to see what happens then.