Created attachment 1030[details]
Proposed patch
This patch makes it possible to disable the check for pak0 by passing '+set com_disablePak0check 1' on the command line. It works for client and server. Every non-zero value will disable the check.
Created attachment 1033[details]
New patch adding a DEFINE to disable both, pak0 check and
After talking to zakk, he proposed to trigger the pak0 via the Makefile. He also proposed to trigger the q3key check by the same define. USE_Q3_DATA defaults to 1 (meaning both enabled), when explicitely set to 0 both checks will be disabled.
The client will send an empty cdkey to the server when authorizing. This patch only affects client and common, not the ui stuff.
Setting a QA contact on all ioquake3 bugs, even resolved ones. Sorry if you get a flood of email from this, it should only happen once. Apologies for the incovenience.
--ryan.
Created attachment 1030 [details] Proposed patch This patch makes it possible to disable the check for pak0 by passing '+set com_disablePak0check 1' on the command line. It works for client and server. Every non-zero value will disable the check.Created attachment 1033 [details] New patch adding a DEFINE to disable both, pak0 check and After talking to zakk, he proposed to trigger the pak0 via the Makefile. He also proposed to trigger the q3key check by the same define. USE_Q3_DATA defaults to 1 (meaning both enabled), when explicitely set to 0 both checks will be disabled. The client will send an empty cdkey to the server when authorizing. This patch only affects client and common, not the ui stuff.Created attachment 1054 [details] svn883: disable pak0/cdkey check * removed some leftover from my first patch in cl_ui.cCreated attachment 1223 [details] svn1016: disable pak0/cdkey check fixed patch for revision 1016