A solution to the problem of when to set the extended info keys. This allows

for nice large amounts of client info to be sent to a QuakeForge server.

sv_main.c:
	Append " QF" to the challenge reply. This DOES NOT break older clients
	because atoi stops parsing at the first non-number character but
	returns the value of what it successfully parsed. If a client does
	choke on this, its libc is broken and not to spec.

cl_main.c:
	Check for "QF" in the challenge string and if it's there, set the
	QF extended info keys before connecting. Also, make sure the extended
	info keys are NOT set prior to starting the connect process. This is
	done is the CL_Disconnect function.
This commit is contained in:
Bill Currie 2000-10-04 16:22:51 +00:00
parent 065abe9464
commit fc6ff9374d
2 changed files with 38 additions and 14 deletions

View file

@ -626,7 +626,7 @@ void SVC_GetChallenge (void)
}
// send it back
Netchan_OutOfBandPrint (net_from, "%c%i", S2C_CHALLENGE,
Netchan_OutOfBandPrint (net_from, "%c%i QF", S2C_CHALLENGE,
svs.challenges[i].challenge);
}