Voyage - Failed mission bug?
SevenOf919
✭✭
This morning, I attempted to recall a voyage at 5 hr 57 min with 19 antimatter left. I was watching the screen and the countdown the entire time and there were no warning icons that a new crisis was looming, so I should have been able to recall without any problems.
Instead, when I confirmed the recall of the mission, I received a FAILED notification and lost 5 hrs and 57 minutes worth of rewards (5 3-star crew, numerous 4* trainers, federation credits, various components and perhaps slightly under 200 chron). When the FAILED message appeared, there wasn't even an option to extend the mission by using dilithium. The only action available was to COMPLETE, which then took me back to the main screen as if this voyage had never happened. See attached screenshot of the failed notification.
At first I thought that this might have been an issue of my cutting things too close with the voyage (hoping for that 3rd dilemma), but I know of at least one other player who experienced the same issue with over 200 AM left.
There are a couple of issues here:
1) I have to believe/hope that the FAILED behavior with no option to extend the mission was a glitch rather than by design, so I wanted to make you aware of the problem.
2) It appears that the game initiates crises before alerting the player. I'm not sure if this is a deliberate design (which it shouldn't be) or another glitch, but there should be ample notification BEFORE a "crisis" actually starts in the system; otherwise the antimatter counter is always going to be inaccurate, to the players' detriment. In either case, this needs to be fixed.
I have also submitted a support ticket regarding the problem. Thanks for your consideration.
Instead, when I confirmed the recall of the mission, I received a FAILED notification and lost 5 hrs and 57 minutes worth of rewards (5 3-star crew, numerous 4* trainers, federation credits, various components and perhaps slightly under 200 chron). When the FAILED message appeared, there wasn't even an option to extend the mission by using dilithium. The only action available was to COMPLETE, which then took me back to the main screen as if this voyage had never happened. See attached screenshot of the failed notification.
At first I thought that this might have been an issue of my cutting things too close with the voyage (hoping for that 3rd dilemma), but I know of at least one other player who experienced the same issue with over 200 AM left.
There are a couple of issues here:
1) I have to believe/hope that the FAILED behavior with no option to extend the mission was a glitch rather than by design, so I wanted to make you aware of the problem.
2) It appears that the game initiates crises before alerting the player. I'm not sure if this is a deliberate design (which it shouldn't be) or another glitch, but there should be ample notification BEFORE a "crisis" actually starts in the system; otherwise the antimatter counter is always going to be inaccurate, to the players' detriment. In either case, this needs to be fixed.
I have also submitted a support ticket regarding the problem. Thanks for your consideration.
0
Comments
I'm waiting on my ticket now hoping for more than chronitons.
Document with screenshots, file a ticket, and be patient for a response. They'll refund your Dil.
I got a rude reply about how i made my choice putting my crew on a voyage and i need to better manage my crew if i need them back, say for an event.
It's my choice to weigh the cost/benefits before assigning my crew. NOT to have that choice turned into a cost/cost fiasco with no benefit that cs then blames on me WHEN THE GAME GLITCHES!!
They only cared about dilithium spent. Nothing about how these glitches, that randomly put some at great disadvantages when planning for events, makes strategy impossible.
The only thing i got from cs so far about glitched voyages was not denial that said glitches are occurring, but rather advice to make my choices more wisely next time. Somehow these buggy voyages blamed on players is SOP.
Ask for a Supervisor.
~· Fly with the Subspace Eddies! ·~
Filled in the ticket, no problem. Just had my next voyage do exactly the same at 20AM to go, this time at around 7h10. Is this new bug becoming more common or have I just hit the bad luck that dogs this stuff sometimes, I wonder.
ps. Trait switch bug for me seems to happen whenever I don't restart the game after the refresh of the stats. The refresh of voyage gold,silver, traits, seems to be at gauntlet end/1 day left times. If my voyage crosses that point, I need to finish my voyage and then restart the game to see the new stats, otherwise the start page lies and when I start voyage they correct to the actual ones.
I just put this down to one of this game's many 'fail to refresh page' bugs, like the ones that show chrons available that have already been spent, or the start shuttle mission page that shows the stats from the 'open shuttle mission' page instead of the actual mission's values. Old data on pages is a feature that occurs often, i just put my trait switch bug down to those.
Have open tickets. No answer. NOTHING!
If have no update on this issue, otherwise I would have shared it - we are investigating.
If that was the case, then you would be seeing that exiting and going straight back in would result in a quick AM adjustment, perhaps over 200 fast adjust after watching it 15 minutes? I haven't seen that before, so maybe its tied in how you say, with how much load your device is under. Certainly I watched about 30 voyages for the last 10-20 minutes without having the problem, but that might be just my device was under less load in those situations.
It still doesn't quite explain why the recall button suddenly functions as an abandon button, but I guess they are in the same place but the screen hasn't refreshed. The game probably just says 'touch at x,y coordinate, and translates that as 'abandon' even if our button says 'recall'
Joint Fleets
Temporal Defense Initiative (TDI)
Deep Space Armada (DSA)
Temporal Defense Initiative 2 (TDI2)
Discord Server
I did. Have not heard back. Why I'm posting here.
Perfect example of lag. Events shown are very clearly 1 minute behind what actualy happening.