"cl_guidServerUniq 1" produces different guid than previous clients
wtfbbqhax opened this issue · comments
Compared to say, "Amanieu/tremfusion", setting cl_guidServerUniq 1 will generate a different cl_guid from the same qkey file.
Originally I thought this was due to the qkey relocation that happend forever ago- but this is not the case. (Tremfusion first checks the new location/then the old location, This is not something I'll be porting).
The md5 code is identical to tremfusion as well.
Tremfusion does add cl_guidServerUniq 2 which will update cl_guid using clc.serverAddress instead of serverString
https://github.com/Amanieu/tremfusion/blob/master/src/client/cl_main.c#L1651
This is due to using different port number to connect to the same server (read GrangerPub/GrangerClub/test7341).
serverString is the amalgamation of serverAddress and port.
What to do about this?
I think I have a hacky solution for this
Not gonna deal with this for now. Removed "bug" tag since this acutally works as expected. Adding a hacky solution would make it "wrong" (TM) as the saying goes.