Prevent latejoin duplication doesn't work properly

[Elkondo]

So this has been an issue for a long time, hopefully can be fixed easily. Essentially, it seems that if a player joins during the mission loading they won't have the option to select class and will join as whatever they had selected previously.
This results in people joining games as duplicate classes despite the "prevent duplication" being checked. And it's really annoying.

*************************
Reproduction rate: 100%

Steps to reproduce:
1) Tick "Prevent latejoin class duplication"
2) Host a game
3) Start a mission
4) Have a player join during a loading screen

Expected Results:
Class select screen regardless of when the player joined.

Actual results:
Player who joins doesn't get a prompt to select a class and instead spawns as whatever he had previously, which allows for class duplication.

[GSG Mark]

Strange. I haven't been able to reproduce this internally, despite timing it perfectly with the loading screen.

Can you provide more details on which mission you were playing, which class got duplicated etc.?

[Elkondo]

Really? I thought this was a common thing.

As far as I know it's just as I described. If someone joins while we're in the lobby - it's fine, they can pick whatever they want. If someone joins during the mission - it's fine, no dupes. But if you join someone's mission during the loading sequence (as in eg. there's 2 players at first, 2 portraits when the loading begins, the loading freezes a bit and a new portrait appears) the new player doesn't get to pick a class - just joins with whatever he had picked before.

Most recently I had this happen when I was hosting a public match as an engineer, a gunner joined me in the lobby (as in the base), we started a mission and a third player joined as an engineer during the loading.

Actually, could it be that the player pressed join when the game still considered us to be in the lobby, but only fully connected during the loading screen, and so was allowed to have a duplicate character since it wasn't technically a latejoin? But since we were already starting the mission he had no chance to select another class (Or he had, but was allowed a dupe? Can't say, not sure if character select appears when joining in the base).
Might be hard to replicate if you're on the same network with very low latency, not that I think about it.

[Schwartzy]

Yea I've had this happen to me several times. Not sure how to reproduce it. Just thought it was the occasional loading glitch.

[Chibbity]

Actually the situation you described happened to me, with different results.

I was Engi in lobby and joined a game mid load which already had an Engi and no dupes turned on, and was magically changed to a Driller, which was the class they didn't have.

So, idk. I didn't get a class select screen but it just auto assigned me.

[®omano]

Actually, could it be that the player pressed join when the game still considered us to be in the lobby, but only fully connected during the loading screen, and so was allowed to have a duplicate character since it wasn't technically a latejoin?

seems right. I already seen duplicates when I and my friends all have the anti duplicate thing enabled.

[GSG Mark]

I finally managed to reproduce it thanks to your contributions!

The issue occurs if another player joins while there's very little time left on the Mission Countdown.

I've forwarded it internally.