I’m pretty sure it still happens after the new DLC launched. It’s hard to say for sure, sometimes people just think they got kicked and don’t ask questions afterwards, and when you’re hosting you might think that people left on their own accord instead.
I’ll write here if I know for sure it has happened again. Was this meant to be fixed in the new patch though, as I don’t think there’s a line about it under the Lobbies section of the patch notes. The other lobby bug (lobby crashes before it can start) is still not fixed and I assumed the two bugs are connected.
@Felizon89 player drops and receive a “kicked” message as if host kicked them which isn’t the case.
a normal kick from host would result in them unable to see the lobby or rejoin for 1 whole minute, but this they can rejoin and it isn’t a kick from host, just a message which can lead to misunderstanding.
further more, this isn’t UI mod or some sort. this is any datamod, scenario etc. the game isn’t only supporting normal games lobby, but also mods as it is a huge part of the game.
I can understand the devs are less likely to help and troubleshoot for modders but this is a game feature and it needs to be fixed.
@Nerathion I feel that there is some correlation for sure. whenever player drops randomly due to this bug, I find that the lobby on countdown start has a much higher chance of dropping all players (the offending player getting the bug would stuck in countdown screen and not proceed onto loading screen).
we got a mod group and play mods daily and this is what we observed after like 20-30 games. for now the player who got the kicked message have to try restarting the game to lessen the effect.
Yes, I believe the same. At least, a workaround for that is to close the spot every time after someone leaves (or gets kicked), and then reopen it again after a few seconds. Supposedly the lobby can bug out when someone leaves or gets kicked and isn’t properly updated, so when a new player takes that spot the lobby will read it as 9/8 players in the lobby on start, causing the crash.
This is all assumption though, so I don’t know if that’s actually the case. Most of these ‘workarounds’ I’m aware of are just people trying out things and seeing if there’s any correlation, at the very least closing spots has in my experience lowered the chances of lobbies crashing before loading screen even appears. Mind you - I’m talking about the crash where everyone gets an unknown error right after the lobby has counted down to 0, but before everyone would go to loading screen. The ‘offending player’ stays in lobby while everyone else gets booted, too.
@Felizon89 I’m pretty sure this bug happened again today, where someone got kicked and host said they didn’t kick the player. I don’t think it was a map kick (where if a player accidentally clicks anywhere but Agree to downloading the mod, they immediately get kicked from lobby) either.
I think this happens when people leave or get manually kicked on their own, then new joiners to lobbies will have a higher chance of getting kicked - but this is also just a hypothesis. I’ve noticed they’ll get kicked when the lobby gets full, but not always.
So perhaps something like… while lobby is getting full or is full, kick someone or have them leave and do not do anything with the spot. Immediately after the kick have someone else join the lobby to take the spot. And then maybe wait for a minute or so? Or just start the lobby.
I don’t know if this would 100% reproduce the issue, but this is what I’ve noticed leads to problems most often.
We found an issue that makes some players that join a lobby crash. If the host creates a public lobby, then change the server setting to private, invite some people and then add some AI, the guests crash. We’re still investigating more issues related to players dropping.
giving more info here. our lobbies are never private. like 99% of these crashes on startup or player dropping are all in public lobbies, but the bug you guys found may likely be related. so fixing that may fix this too