aboutsummaryrefslogtreecommitdiffstats
path: root/code/tools/lcc/src/null.c
diff options
context:
space:
mode:
authoricculus <icculus@edf5b092-35ff-0310-97b2-ce42778d08ea>2009-09-14 15:45:52 +0000
committericculus <icculus@edf5b092-35ff-0310-97b2-ce42778d08ea>2009-09-14 15:45:52 +0000
commit63e6b4f6cfecdc912da62aad80e5be78a996e749 (patch)
tree8e3768524284f4bd53c5652f5179049d16f69417 /code/tools/lcc/src/null.c
parentbec584811a9ec5d525f2b31a58f40b2a58780caa (diff)
downloadioquake3-aero-63e6b4f6cfecdc912da62aad80e5be78a996e749.tar.gz
ioquake3-aero-63e6b4f6cfecdc912da62aad80e5be78a996e749.zip
SetTeam fix from Martin Doucha.
"Actually, client->ps.clientNum is unsafe. We had a little hunt for this some time ago in Tremulous last year (it caused kick failures, annoying popup windows and other nasty bugs). The problem is that a following spectator gets full copy of client->ps of the followed player including clientNum. If you then try to use this "shared" clientNum, you might affect someone else than you wanted. r1019 changes are safe as long as bots don't spectate players. However, a brief grep on current code has revealed unsafe client->ps.clientNum usage in SetTeam(). If a following spectator uses team command when forced balance is on, it'll count teams incorrectly and send the error message to the followed player instead. Here's the fix." Fixes Bugzilla #2986. git-svn-id: svn://svn.icculus.org/quake3/trunk@1587 edf5b092-35ff-0310-97b2-ce42778d08ea
Diffstat (limited to 'code/tools/lcc/src/null.c')
0 files changed, 0 insertions, 0 deletions