on your server, put `serverinfo no_pogo_stick 1' into your server.cfg. It's
called no_pogo_stick for two reasons: the effect is called "pogo stick" in the
source code in a comment from the original id source code and also as a minor
(and very week:/) obfustication for `cheaters' trying to set it in their
clients. However, the client checks for no_pogo_stick in the server info and
forces it on when appropriate and having them in disagreement would only make
prediction a little screwy anyway :). BTW, when enabled this actually fixes the
original bug that allowed bunny hopping in the first place (though you still
get a jump grunt when you try to bunny hop; minor bug).
input.h: Use int_val for freelook
cl_input.c: Use freelook macro instead of in_mlook.state
in_svgalib.c: freelook support and whitespace
in_win.c: whitespace and minor optimization in mouse support
in_x11.c: freelook support
vid_ggi.c: joystick support and minor opt in mouse support
vid_sdl.c: joystick support, freelook support, minor mouse opt, spaces->tabs
time, by checking whether the device is busy or temporarily unavailable (I
haven't seen the latter happen, but the former may occur if your window
manager is set to make noise when a window pops up). Between tries, the
client sleep()'s for one second (should this be half a second or even
faster?).
name of the program is. It's "`basename $0`.PROGRAM".
Also, create a window size ICCCM hint, forcing the window to the size it
should be -- we don't want it resized, so now the window manager ought to
get the picture. :)
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.
remove *qsg_version and *cap on disconnect
set *qsg_version and *cap after connection but only if the server presents
*qsg_version (it will have big enough info buffers if this key exists). Doesn't
yet send the updated values to the server as there is currently no way to do
so :( I started out creating a setfulluserinfo, but ran into design/security
problems with that approach. What's needed is to either find a secure way to
update these two star keys (however, special casing is ugly) or make them
non-star keys (I don't like that either: too easy to fiddle with). Another
possiblity is to force a reconnect after they are set.
