Kicked From Server
-
Anytime i try to join a lobby with decent ping i get kicked upon choosing a create a class option. I understand that there are priority admin slots on a lot of the popular servers, but this happens even when there are only a handful of people in the server. My only option is to join servers with nearly unplayable connections. If somebody could explain this, I'd be grateful.
-
I got the same problem.
-
Same thing happening here. Lets me join fine. But once I choose a class I'm instantly kicked out....
-
Indeed, seems to only happen when selecting custom classes and not default ones.
-
I figured out why. If you unlock all stats and try to use a custom class it will kick you out but if you unlock all, reset the game and unlock all again it'll fix the issue! I hope this helps!
-
I figured out why. If you unlock all stats and try to use a custom class it will kick you out but if you unlock all, reset the game and unlock all again it'll fix the issue! I hope this helps!
@Carlwheezer1011 dont work
-
Yoshite_ sorry to hear that :(. someone in game told me about it and it worked for me. hopefully theres a fix in the near future
-
Yoshite_ you could also try unlocking all stats, join and get kicked from a server, reboot the game, unlock all stats again and see if that works. I did this in order and somehow I was able to get in and play. I also noticed that after playing for a bit and getting xp my stats saved and didnt need to use the unlock all command again.
-
-
Yoshite_ quit the game entirely and relaunch it
-
i try but no chang
-
U have to made you'r classes on the 5 last slots. The first 5 are glitched
-
has anyone figured out a fix?
-
Any help? Same here.
-
So, mine fixed itself doing this: Unlock custom classes, quit the match and go back in. it will kick you, and for me also put me back to the rank before the unlock. Fully quit BlOps1 and plutonium. Load it up again and re-earn thew rank. Choose a custom class in the same match you unlocked it, from then on it was fine. IDK what step fixed the issue, but it did
