Page MenuHomeFeedback Tracker

"You were kicked from the game" after joining any ArmA 3 multiplayer session.
Closed, ResolvedPublic

Description

When I join any server no matter what it is, it will load the first screen and show "Group chat" briefly, it will then disappear and nothing will happen. After about 2 minutes a message will pop up saying "You were kicked from the game" and it will take me back to the multiplayer menu. I can see all the different servers so it is almost certainly not internet problems.

Cannot find a solution that is working anywhere.

Details

Legacy ID
796590545
Severity
None
Resolution
Open
Reproducibility
Always
Category
Multiplayer
Steps To Reproduce

Join a game.

Event Timeline

Tayshen edited Steps To Reproduce. (Show Details)Jul 29 2013, 2:32 PM
Tayshen edited Additional Information. (Show Details)
Tayshen set Category to Multiplayer.
Tayshen set Reproducibility to Always.
Tayshen set Severity to None.
Tayshen set Resolution to Open.
Tayshen set Legacy ID to 796590545.May 7 2016, 3:44 PM
Maxyz added a subscriber: Maxyz.May 7 2016, 3:44 PM
Maxyz added a comment.Jul 29 2013, 3:16 PM

Drawster on forums wrote this:
"Have you made sure your Steam is online? I had exactly the same problem after the Beta came out. My Steam went offline for some reason and and I too got the "You were kicked.." -message when trying to join any game. Reconnecting Steam fixed the problem for me."
Maybe you have the same problem? Related to this http://feedback.arma3.com/view.php?id=11601

Tayshen added a subscriber: Tayshen.May 7 2016, 3:44 PM

I just reinstalled it out of rage, but I'm sure that would've been the cure. Thanks man - My steam WAS offline when I tried it.

Ra-USMC added a subscriber: Ra-USMC.May 7 2016, 3:44 PM

I am having the same issue. I have made sure Steam was online...no good, but this is exactly what happens. I cannot play anymore...

MadDogX added a subscriber: MadDogX.May 7 2016, 3:44 PM

Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.

If this issue is still relevant in current dev build, please re-post.