WS connection don't start map

[GonzalezAtWork]

Hey guys!

Having a specific issue after compiling from latest source:

When I try to connect using WS protocol, it does connect to the FTEQWSV, but it does not initiate the map on the server. If I connect other way, it all goes well.

That does not happen when I run the 2020's version from here: https://fte.triptohell.info/moodles/win32/

Am I having a missing configuration for WS/WSS that didn't exist in 2020?

EDIT: Gone back to the last commit from 2023 and all works good: https://github.com/fte-team/fteqw/commit/ab1e8d321a179bfb97801d900be69b5dc5762267

So the issue relies on something done in 2024

[eukara]

Here's what Spoike had to see regarding a temporary workaround:

The console command cmd new in the client should 'fix' it. FTE's Quake II server is replying with sequence 0, which the client drops, with the server assuming everything is reliable and won't be dropped. Whereas with UDP the issue is still there, but it'll keep re-sending until the reliable packets go through.

[GonzalezAtWork]

cmd new on the client did in fact worked, but once the round is over, the server "kick" everyone out:

and on the server:

Timelimit hit.
Game ending at: Wednesday 25 September 20:42:17
Next map in rotation is .
Server spawned.