Bug 4000 - STANDALONE flag prevents client from connecting to a server.
Status: RESOLVED FIXED
Alias: None
Product: ioquake3
Classification: Unclassified
Component: Misc
Version: GIT MASTER
Hardware: PC All
: P3 normal
Assignee: Zachary J. Slater
QA Contact: ioquake3 bugzilla mailing list
URL:
Depends on:
Blocks:
 
Reported: 2009-03-02 00:27 EST by Kyle Monson
Modified: 2009-03-02 12:29:46 EST
0 users

See Also:

Attachments
Fix for STANDALONE flag connection bug. (649 bytes, patch)
2009-03-02 00:40 EST, Kyle Monson

Description Kyle Monson 2009-03-02 00:27:16 EST 
When compiling with the STANDALONE flag clients cannot connect to a server.

Repro:

compile with STANDALONE enabled.
start a server
start a separate client
connect to the server.

Actual Results:
client never connect with the client waiting for a challenge response.

Expected:
client promptly connects 

NOTE: enabling com_standalone will allow clients to connect but this defeats the purpose of the STANDALONE flag.
Comment 1 Kyle Monson 2009-03-02 00:40:16 EST 
Created attachment 2004 [details]
Fix for STANDALONE flag connection bug.

The STANDALONE flag is supposed to forgo the talking to the auth server and send an immediate challengeResponse. 

The code compiled with the STANDALONE flag checks the com_standalone setting. If it is not set the challengeResponse is skipped and nothing is sent back to the client leaving it hanging.

This patch removes the com_standalone cvar check.
Comment 2 Ludwig Nussel 2009-03-02 12:29:46 EST 
applied, thanks

It would probably make sense to initialize set com_standalone to 1 if STANDALONE is defined instead and get rid of all those #ifdef's.