Home Engineering Room

Issues with merging accounts and invisible 'ghost' crew in fleets?

Wanted to pitch this to the community and see if other folks have encountered it before. It's a pretty convoluted situation, but I hope people can follow along and provide some advice.

We have a new fleetmate who appears to be bugged to high heaven, and we are trying to figure out what his exact issue is, and how we can on-board him successfully. He had recently linked his account to email/DB, which apparently gave him a new DBID with his current game progress---though he still had access to the old account on the previous DBID after doing so. The new DBID was chock full o' errors (possibly because he now had two accounts that he was logging into on multiple devices), so he tried to keep playing on his old DBID.

Long story short, during this time, he replied to our recruitment thread on these forums, asked to join, and it has been non-stop problems right out of the gate. The guy was "invisible" to in-game search, friends lists, and as we found out shortly later, fleet member lists. We could only private chat with him in-game if he initiated the conversation, and we got errors when trying to invite him to the fleet. However, when he applied to the fleet himself, that popped up and we were able to accept him. Again, once we did that, he never showed up on our fleet list, and was even able to join a squadron while in this invisible state. The only way we knew the guy was online was when he was chatting with us in our fleet channel.

At this point, DB made an initial response to our ticket and confirmed that the guy 1) had two DBIDs; and 2) that he was listed as one of our fleet members on the back end even though we can't see him. This prompted a lot of questions, but I'll skip those and cut to the advice from the CS rep, which was for our real-live Vanellope von Schweetz to use only the new account, and for us to invite that one to the fleet.

So...we did that. Fleetmate quits fleet (invisibly), logs out, logs in on the new account, he's visible on my friends list after accepting a friend request, everything is great, and...error message when we try to invite him back to the fleet. He tried applying like last time, and it doesn't pop up for our Admiral. Totally bonkers. And what's more, he's getting a bunch of other errors, mostly connected to when he tries to play gauntlet. But the point is, now the guy is trapped outside our fleet, and ostensibly, there should no longer be any issue. He's only playing his new, linked account.

Has anyone seen anything like this before? What was the fix, if any? Some of our officers think that the "ghost" account is still on our roster and preventing the new account from joining, but that doesn't necessarily explain all of the other game errors. We're extremely frustrated with the situation.

We are still waiting on our tickets to (hopefully) advance, but if anyone from DB wanted to drop in and provide some input or offer a resolution, it'd be greatly appreciated. We like our new friend and it **tsk tsk** having him twisting in the wind like this---now that he's not even in the fleet anymore (albeit in uber bugged fashion), it's even worse for all parties involved.

I hope somebody might have insights to offer.

Best,

Celeres
First Officer - Task Force April
Squadron Leader - [TFA] Bateson’s Bulldogs

Comments

  • Hello! I'm the ghost person mentioned in this post. This all started when I saw the button in app to login to my DisruptorBeam account. DO NOT DO THIS.

    I had assumed the game would recognize I was logging in and connect my dB forums info to my game account, which had been connected via facebook. This facebook login, which uses the same email address as the db account, was how I had been able to log in via steam as well as my tablet, and is how many other mobile games I've played in the past function. I had very little notion of what a dbid even was at that time. Now I know.

    Anyway, as mentioned above, I basically seem to have splinched myself between two accounts and have been getting errors ever since. While all my ships and crew and such are all there on either login, I can't play gauntlet, arena rating reset, monthly card vanished, 10 10x super rare pulls vanished, and my portrait and name are invisible, in addition to being invisible in lists and rankings, as well as fleet bonuses including max chrons not working. This disrupted virtually all of my time trying to succeed on the last event (I ended up missing the third commander chapel by a measly 50 vp), and I'm just praying I don't miss all of this next one, especially considering the mega implications.

    I do want to mention that DB support really has been trying their best to help me with this bizarre issue, and I thank them for the time they have spent trying to help me through this. They've been great. I just want to warn anyone who might stumble across this log in button like I did: just don't do it. It appears it all stems from the interaction between multiple logins across multiple devices.
  • We have recently just recovered from a very similar situation. Many fleets have been caught in the 49/50 fleet error. You have a "ghost" on the DB side server. Customer service can not fix this by themselves. It has to go to a team lead and a programming engineer. It took several weeks working with DB to get this resolved. Let me know if I can be of any more help.
Sign In or Register to comment.