This action removed the player from squad A, but also removed him from squad C, but left behind a ghost in squad C.

Squad A realized that they had a ghost, and so they removed him from their squad. To recap our example, the player applied to 3 squads, and ended up in squad C but left behind ghosts in squads A and B. This solves the problem for you, but also makes the problem worse for the player and the squad they’re actually in. The only solution is to remove the ghost member from your squad. When you visit the squad member’s base, a different squad is listed under the member’s name. A new squad member is accepted, and within an hour or two, they’re already a ghost. This scenario plays out all the time in many squads. So, in the end our player is in squad C and left ghosts behind in squads A and B. Squad C gets around to accepting this player and once again, he’s pulled from squad B (leaving a ghost in B) and he’s now in squad C. Squad B then accepts him and he gets pulled away from squad A (leaving behind a ghost in squad A) and he’s now a member of squad B. Even though he’s accepted into squad A, his applications to join squad B and C are still active. He is immediately accepted into squad A and is happy to stay there. If you’re not in a squad, there is no limit to how many squads you apply to join.Įxample: Let’s say a player, who is not in any squad, applies to join 3 different squads – squads A, B, and C. The most common cause of ghosts is from players trying to join multiple squads. But the “ghost” you leave behind takes up a spot in the old squad.Ģ. Your medals in your old squad won’t change and your donations obviously stay the same. The result is that you will be in your new squad, but it will appear that you’re still in your old squad.

You can apply to join a leaderboard squad even if you haven’t left your original squad. The problem comes because of the squad leaderboard.

Click the “Leave” button to leave your squad.

Star wars commander glitch