Please restart the game to make sure to see the change.
Let me know:
- if the skills are now what you are expecting them to be
- if Voyages that got stuck after the Noon ET server push are now resuming.
My current voyage has now gone back to showing the 'correct' gold and silver skills, but it is still frozen at the 10hr mark, refusing to display a Dilemma. So, bug #1 is better/fixed, but bug #2 not fully resolved.
Good: The skills are back!
Bad: The AM drain during the bugged period will irreparably set me back . This voyage will be much shorter than it should have been.
Worse: The stuck dilemmas are not unstuck.
I certainly hope something will be in order for a recompense. I recalled my voyage after I saw what the skills changed to mid-flight.
Admiral of the Haus of GaghGagh, Starbase level 94, we are not accepting members at this time.
Captain of the voyage vessels: Queen of Bashir, Landsknecht, and Sunspear, the first luxury starship cruiseliners.
Amenities include wifi, fully-functioning holodecks, a full-service bar, 3 party decks, a Trill spa, and a business centre.
Fun fact: The ships are propelled by bouncy castle technology.
Please restart the game to make sure to see the change.
Let me know:
- if the skills are now what you are expecting them to be
- if Voyages that got stuck after the Noon ET server push are now resuming.
My current voyage has now gone back to showing the 'correct' gold and silver skills, but it is still frozen at the 10hr mark, refusing to display a Dilemma. So, bug #1 is better/fixed, but bug #2 not fully resolved.
Please provide me your DBID via Private Message, thank you!
Erm, this happens to me every other voyage. I thought this was a "feature".
Maybe the irony is that we play because we’re Star Trek fans, those hopeful idealists that like to think things will get better when we raise valid concerns about fairness and balance, etc and we forget that DB’s greed openly mocks the values espoused by the franchise they have a license for.
-Lord Wizzlestix I
I started a voyage before noon ET with Com/Sec. I check my status after solving the 2h dilemma to see that my AM is unusually low. The primary and secondary skills became Med/Eng, which caused my AM to plummet. I recall. When I go to complete the voyage, I notice that it is back to Com/Sec.
On a related note, I've started to restart my game immediately after starting a voyage. Sometimes, if the primary/secondary skills change while selecting the crew for the voyage, it won't show it right away. It will show it if you restart the game (this unusual event notwithstanding). Also, if you do end up with different starred skills, you can immediately recall it and get it back very quickly, so you don't lose much time. Unfortunately, you do lose that time you spent selecting crew for the first voyage. Just a bit of a workaround.
Cool. Glad you got this "fixed" so fast. Except that when it switched to the wrong skills I had to recall so as not to WASTE MY TIME. Now that it's back it's "fixed" back to what it was before and that entire Voyage was a waste. And please don't tell me to "submit a ticket" I'm still waiting over TWO WEEKS on my last one that hasn't even been touched yet.
Between this and the absurd new Arena reward bait and switch I swear I am one more bug away from the uninstall button. This is getting ridiculous.
"The truth is usually just an excuse for a lack of imagination."
Erm, this happens to me every other voyage. I thought this was a "feature".
Do you restart your game before a voyage? There has been a known issue where the incorrect skills were displayed, then updated after you started (thus you assigned using the wrong skills). Restarting the client before assigning would display the correct ones. This is a case where they were correct, then actually changed midstream when the server was updated.
"If it wasn't for autocorrect, we wouldn't have Tuvok on a Giraffe."
I noticed this as I hit my two-hour dilemma this morning and recalled as soon as the dilemma was taken care of. I had already started to loose Antimatter and wasn't worth continuing the Voyage. Was nice as I had command and security with one over 6000 and the other over 7000.
Great, i had Sci (gold) and Eng (silver) as main skills and now after the "fix" i have Eng (gold) and Sci (silver). Great Job DB! This is just more than ridiculous
I am realy getting mad writing tickets. I guess i have to hire a secretary to handle all the correspondence with DB.
I posted a thread about this bug over a week ago. It's in the engineering room "Voyage changing main states mid voyage." is the title. (Forum won't let me post the link, says I need to be around longer first )
Will there be a blanket compensation for people who had one of the following issues:
1. Stuck at dilemma (lost voyage time)
2. Traits changed and had to recall early (lost chroniton/crew/replicator rewards)
3. Traits changed, lost antimatter but didn't recall, then traits changed back (lost antimatter/dilithium)
Or should we all be putting in tickets for this issue?
I posted a thread about this bug over a week ago. It's in the engineering room "Voyage changing main states mid voyage." is the title. (Forum won't let me post the link, says I need to be around longer first )
Prosser-- I think this is a slightly different bug. The previous voyage-skill-change bug happened (to me) if I sent a voyage without rebooting the app first. Today's bug actually happened even with the courtesy reboot.
Both versions of the bug are annoying but today's seems unpreventable from the player's side.
I posted a thread about this bug over a week ago. It's in the engineering room "Voyage changing main states mid voyage." is the title. (Forum won't let me post the link, says I need to be around longer first )
Prosser-- I think this is a slightly different bug. The previous voyage-skill-change bug happened (to me) if I sent a voyage without rebooting the app first. Today's bug actually happened even with the courtesy reboot.
Both versions of the bug are annoying but today's seems unpreventable from the player's side.
Ah ic. Ya it really throws your planning for a loop.
I posted a thread about this bug over a week ago. It's in the engineering room "Voyage changing main states mid voyage." is the title. (Forum won't let me post the link, says I need to be around longer first )
Prosser-- I think this is a slightly different bug. The previous voyage-skill-change bug happened (to me) if I sent a voyage without rebooting the app first. Today's bug actually happened even with the courtesy reboot.
Both versions of the bug are annoying but today's seems unpreventable from the player's side.
Ah ic. Ya it really throws your planning for a loop.
DB doesn't believe in planning.
"The truth is usually just an excuse for a lack of imagination."
I'm still having this issue as well, I ended up eatting a ton of dilithium and now its stuck on a dilema without the ability to see or resolve it. The timer counts down 20 seconds and then resets.
Update on what I know so far:
- earlier today, with the server push, we sent some fixes for Voyages issues such as skill changing and some Voyages getting stuck
- those fixes did not have the desired effect and created additional issues as reported in this thread
We have pushed a hotfix for this around 14:45 ET and can now confirm that:
• the skills that changed today after Noon ET are now back to what they should have been
• some of the Voyages that got into a stuck state after Noon ET are now resuming
• the bug causing Voyage skills to change after 00:00 UTC if you were already logged in at that time should now be fixed
We are aware that there are still stuck Voyages, from today and the days before.
This is currently under investigation, the goal being to be able to get those Voyages going again but also to make sure it will not happen again. I have no ETA at this time.
I am currently waiting on more information regarding compensation.
So question. What do we do if our Voyages ship ran out of fuel? Mine did 10 minutes prior to the decision event and I've no idea to know if it was a legit shortage or a result of skill swaps.
Shan is busy typing up more info for you. But we said half an hour and we are trying to make good on that.
Right now we are working out:
1) Sending out an in game mail with details and some chronitons
2) Looking at a solution we can get out tonight to address some stuck people and help them keep their rewards
During one of our regular event server pushes, our engineers made changes to Voyages to address outstanding bugs. Unfortunately, this resulted in an unexpected issue which resulted in starships ended up becoming stuck.
In order to free all of the starships, Starfleet Command is recalling ALL Voyages, whether stuck or not:
* The rewards from those recalled Voyages will be claimable, including those that are currently failed or are in transit.
* A forced restart will be initiated once all Voyages have been recalled
* We apologize for the inconvenience, and we are sending 1,000 Chronitons with this message as a compensation.
Should you still see a Voyage in an unusual state, please restart the game once more and it should clear up.
Comments
confirmed that Skills returned to original setting...
but had already recalled Voyage, so can not confirm if the "stuck" at dilemma was resolved.
My current voyage has now gone back to showing the 'correct' gold and silver skills, but it is still frozen at the 10hr mark, refusing to display a Dilemma. So, bug #1 is better/fixed, but bug #2 not fully resolved.
so...those of us who lost at least 2h and a dilemma?
Skills have been restored.
Bad: The AM drain during the bugged period will irreparably set me back . This voyage will be much shorter than it should have been.
Worse: The stuck dilemmas are not unstuck.
Proud Former Officer of The Gluten Empire
Retired 12-14-20. So long, and thanks for all the cat pics!
Please provide me your DBID via Private Message, thank you!
Captain of the voyage vessels: Queen of Bashir, Landsknecht, and Sunspear, the first luxury starship cruiseliners.
Amenities include wifi, fully-functioning holodecks, a full-service bar, 3 party decks, a Trill spa, and a business centre.
Fun fact: The ships are propelled by bouncy castle technology.
Please provide me your DBID via Private Message, thank you!
-Lord Wizzlestix I
On a related note, I've started to restart my game immediately after starting a voyage. Sometimes, if the primary/secondary skills change while selecting the crew for the voyage, it won't show it right away. It will show it if you restart the game (this unusual event notwithstanding). Also, if you do end up with different starred skills, you can immediately recall it and get it back very quickly, so you don't lose much time. Unfortunately, you do lose that time you spent selecting crew for the first voyage. Just a bit of a workaround.
Between this and the absurd new Arena reward bait and switch I swear I am one more bug away from the uninstall button. This is getting ridiculous.
Do you restart your game before a voyage? There has been a known issue where the incorrect skills were displayed, then updated after you started (thus you assigned using the wrong skills). Restarting the client before assigning would display the correct ones. This is a case where they were correct, then actually changed midstream when the server was updated.
I am realy getting mad writing tickets. I guess i have to hire a secretary to handle all the correspondence with DB.
1. Stuck at dilemma (lost voyage time)
2. Traits changed and had to recall early (lost chroniton/crew/replicator rewards)
3. Traits changed, lost antimatter but didn't recall, then traits changed back (lost antimatter/dilithium)
Or should we all be putting in tickets for this issue?
Prosser-- I think this is a slightly different bug. The previous voyage-skill-change bug happened (to me) if I sent a voyage without rebooting the app first. Today's bug actually happened even with the courtesy reboot.
Both versions of the bug are annoying but today's seems unpreventable from the player's side.
So I had a potential 7.5 hour voyage shortened to only 6 hours due to this bug.
Ah ic. Ya it really throws your planning for a loop.
DB doesn't believe in planning.
Fixed, yes, but I still had to recall a long voyage before it failed prematurely due to a skill change midway through
- earlier today, with the server push, we sent some fixes for Voyages issues such as skill changing and some Voyages getting stuck
- those fixes did not have the desired effect and created additional issues as reported in this thread
We have pushed a hotfix for this around 14:45 ET and can now confirm that:
• the skills that changed today after Noon ET are now back to what they should have been
• some of the Voyages that got into a stuck state after Noon ET are now resuming
• the bug causing Voyage skills to change after 00:00 UTC if you were already logged in at that time should now be fixed
We are aware that there are still stuck Voyages, from today and the days before.
This is currently under investigation, the goal being to be able to get those Voyages going again but also to make sure it will not happen again. I have no ETA at this time.
I am currently waiting on more information regarding compensation.
Shan is busy typing up more info for you. But we said half an hour and we are trying to make good on that.
Right now we are working out:
1) Sending out an in game mail with details and some chronitons
2) Looking at a solution we can get out tonight to address some stuck people and help them keep their rewards
More info coming...
Greetings, Captains!
During one of our regular event server pushes, our engineers made changes to Voyages to address outstanding bugs. Unfortunately, this resulted in an unexpected issue which resulted in starships ended up becoming stuck.
In order to free all of the starships, Starfleet Command is recalling ALL Voyages, whether stuck or not:
* The rewards from those recalled Voyages will be claimable, including those that are currently failed or are in transit.
* A forced restart will be initiated once all Voyages have been recalled
* We apologize for the inconvenience, and we are sending 1,000 Chronitons with this message as a compensation.
Should you still see a Voyage in an unusual state, please restart the game once more and it should clear up.
The STAR TREK TIMELINES Team