Voyage Issues
SMM
✭✭✭
After the length of time that Voyages have been in beta testing and live why are there still issues?
Is DB currently working on identifying and fixing issues with voyages?
(It is extraordinarily upsetting that my 7.30 Hr voyage just disappeared when I hit the Recall button with 20 anti to spare.)
Is DB currently working on identifying and fixing issues with voyages?
(It is extraordinarily upsetting that my 7.30 Hr voyage just disappeared when I hit the Recall button with 20 anti to spare.)
0
Comments
Exactly the same thing happened to me earlier - except everything disappeared from (I assume) pretty early on. Tried restarting and different platform but still empty - no dilemmas etc. Recalled the voyage after nearly 6 hours and when it got back, got rewards consistent with 2 hours ie 2 honour and a couple of dozen chronatons.
Poor show
Was going to post a screenshot but apparently I have to be around a little longer to post links. Obviously the day to get poked in the eye multiple times by DB.
There are fixes coming for Voyages, I have not ETA yet.
However I would like more information on this disappearance.
What exactly do you mean by that? The Voyage disappears and is not in a recall state?
The crew is immediately released?
Shan, I believe that the issue occurs when clicking recall at below about 40 antimatter. The post above seems plausible that the voyage timed out on the server but not on the local app.
If you people at DB can't make a damn counter bulletproof, put a setting to allow players to program the recall to automatically work when AM reach a certain point. Stop trying nickel and dime on us, especially because this bug DON'T EVEN LET ME TO REFILL the failed mission.
I'm pretty sure the bug is related to a sort of "desync" between your server and our client. Any amount of lag will gradually increase the problem to a point that I lost missions with 90+AM to spare.
We (most of us hopefully) really appreciate your diligence on this Shan! Although, having a better timeframe than "soon" would be helpful. Just sayin'
I think that the issue is being caused by the apps automated messaging sending a message to the server, overriding the servers status for the voyage which has been modified by the user.
This would account both recalled voyages subsequently failing, the phantom messages and other issues.
Check that manually recalling a voyage properly updates the local apps messaging status.
Whats odd is I almost always ONLY get the wrong Dilemma notices. I've gotten 1 in the last week when I actually did have a dilemma waiting.