quakeforge/doc/qw-cap-spec.dox
Bill Currie 6a7b316572 Put my text editing vim settings into the docs.
Vim's autoformating doesn't like our style of comments, so I have to force
it to do what I want. Having to set the appropriate options every time I
edit a file got to be a RPITA, so time to get the computer to do it for me
:)
2011-09-08 10:17:58 +09:00

35 lines
1 KiB
Text

//unfortunately, have to wrap the docs in a C comment for doxygen
// vim:tw=74:formatoptions-=l
/**
\page qw_cap_spec QW Capabilities String
Client capabilities are specified using the "*cap" info key. The info string
is made up of single char flags (possibly with modifiers, though currently
none exist).
Defined capabilities (* = not implemented):
\li z client can accept gzipped files.
\li h http transfers
\li f * ftp transfers
\li a * audio channel (voice chat)
\li i * irc
\li p pogo stick control
\li t team messages
For more information on z and h, see \ref qw_download_spec.
The QuakeForge clients will not send "*cap" to the server unless "QF" or "EXT"
is detected in the challenge string sent by the server.
From the QuakeForge quakeworld server:
\verbatim
if (sv_extensions->int_val) {
extended = " QF qtv EXT";
}
// send it to the client
Netchan_OutOfBandPrint (net_from, "%c%i%s", S2C_CHALLENGE,
svs.challenges[i].challenge, extended);
\endverbatim
*/