- file system change
        all files required by mqwcl are now groupped in one directory,
        'mqwcl' in your quake directory. To get mqwcl 0.95 working,
        please follow these steps:

        - all required files should come with mqwcl itself, so
            you should have correct directory structure with files
            after extracting,

        - if you want to use your old server browser files, move
            them from quake/qw/sb/ to quake/mqwcl/sb/,

        - move your *.loc files to quake/mqwcl.loc, locs can now
            be packed to pak files (pak0.pak etc)

        - move your user configs from quake/qw/users/ to
            quake/mqwcl/users

        - you can delete old mqwcl files to save HDD space and
            have your QW dir tidy. These are:
                - GFX in quake/qw/gfx/mqwcl/
                - server browser in quake/qw/sb/
                - users in /quake/qw/users/

        and all should work fine. Location files directory is no
        longer customizable. Loc files MUST reside in mqwcl/loc.

        You can backup everything first, if you're scared :)

- new security system
        means new and extended f_version query. f_version is the
        most important query in client and proxies security.
        Without passing f_version, all other replies from given
        client or proxy (replys to f_skins, f_modified etc)
        should be treated as invalid, because they can always
        be faked.

        New f_version is generated and checked by external program,
        which is a requirement for releasing mqwcl as open source,
        which is requirement for it to be fully legal.

        In general, system introduced by proxies, in which they
        generate a CRC of their EXE and human is responsible
        for comparing that, is no longer good. Writing a client
        which may simulate proxy is a mattar of one hour. Of course
        I'm not going to give you directions.

        mqwcl uses a different approach. It automatically responds
        to f_version queries, and automatically checks other clients
        reponses. I won't go into details now, but you need to know
        few things:

        - if you look at the big CRC at the end of mqwcl reply to
            f_version, first four characters of this reply are
            the CRC code of the f_version query. So clients that
            answer the same f_version query should have that
            number equal. In fact, this information is needed,
            but you may wonder why these numbers match.

        - clients check themselves, but you may and should check
            the results of that "checking". At any time you may
            issue 'list_clients' command, which will list all
            connected players (and only players) along with their
            clients (if known, currently mqwcl only) and
            authentication status. Authentication is what you are
            interested in: if it is OK, player is using a genuine
            mqwcl. If not ok, client is unknown. Of course, after
            successfull f_version query status of all legal
            mqwcl users should be known.

        - mqwcl only checks clients with this new security system,
            which meanse versions 0.94 and below are not checked.

        - spectator does not respond to f_version query, but still
            checks other clients. Spectator may also issue
            'list_clients' at any time. This allows spectators to
            check players, which should be very useful during
            official matches.

- mqwcl2, which is mqwcl extended version [currently WIN32 only]
        see below.

- no fps limit during demo playback

- r_clearcolor works in GL now
        for setting "clear" color, especially useful when watching
        MVD demos in free fly mode

- fps_grenadetrail
        allows you to disable grenade trail

- 'screenshot' extended
        naming convention for screenshot has changed, so it is possible
        to take more than 100 shots without deleting prevous first.

        There are also new variables for screenshots:

        - scr_shot_gamma - regulates screenshot gamma
        - scr_shot_contrast - regulates screenshot contrast
        - scr_shot_brightness - regulates screenshot brightness

- movie capturing
        so many ppl asked for that, especially for capturing MVD's, so
        here it is. Demo capturing system let you capture demos you
        watch with desired FPS, producing series of screenshots, TGA
        in case if GL, and PCX in case of soft. You can only do
        capturing during demo playback. It is designed in a way to
        produce perfect output. Playback may not be realtime during
        capturing.

        There are two new commands:

        - demo_capture_start <time>
            starts capturing currently watched demo. All effects you use
            during playback, like slow motion, will find it's place
            in your movie. <time> argument is mandatory. It is a time
            after which capturing should stop, but it is a demo time, not
            a real time. It means, that if you, for example, play demo
            at 50% speed, and issue "democapture 20", you will get shots
            for 40s movie in effect. Capturing respects "scr_shot_*"
            variables.

        - demo_capture_stop
            No arguments. Stops capturing, if you decide to break it
            before time given.

        There are also some variables, which configure the whole thing.
        These are:

        - demo_capture_fps (default: 30)
            FPS at which mqwcl should capture FPS. If you plan to make
            movie at 30 fps, set it to 30. Capturing process may be
            somewhat slow, especially with GL and higher resolution,
            but output shots FPS will always match what you set here.

        - demo_capture_viewfps (default: 0)
            This is maximum fps limit for watching demo during capturing.
            0 means no limit. It doesn't affect output in any way, and
            often does not affect what you see. It may only slow down
            the whole process. Useful if you want to control playback
            during capturing (make slow motion, switch pov or sth) and
            your CPU is too fast.

        - demo_capture_dir (default: capture)
            Demo for your capture sessions, starting from quake (or
            you can give absolute path). mqwcl will create a separate
            subdirectory in it for every capturing session you start.

        - demo_capture_nth (default: 1)
            If more than 1, mqwcl will only take a shot every n'th frame,
            where n is what you typed. This is designed for using higher
            FPS, because sometimes things look different depending on FPS.
            So if you want all of demo to look like at 60 FPS, but your
            movie will be at 30, set it to 2. You should rather not use it
            for speed control, although it is possible. There is no speed
            control with MVD currently, but demo_capture_fps may work
            better that demo_capture_nth.

        I'll also give you some tips, which I found useful while playing
        with movies. I bet many ppl can know much more about this subject,
        mayby someone can create a little FAQ for newbies, because some
        movies look ugly because of bad setting / compression, while they
        are quite gool with frags, music etc.

        - don't think higher resolution makes better movie. Try different
            resolutions before you decide to use 640x480 because it's far
            too much for quake. 400x300 looks nearly the same, except
            crosshair and text. Consider using space saved this way
            to better aspects - longer movie, less-sized movie, smoother
            movie (with more fps) or anything else. Also, higher res
            means much more CPU power required to play it.

        - smoothness is the biggest problem. In most cases 30 fps should
            be enough, but you can try higher settings if your movie
            has really fast actions or presents high-sens players.
            Keep in mind that higher FPS = bigger size and more CPU
            power required to play, like with res.

        - in many cases MVD demos play more smoothly than QWD/QWZ. It
            may be a good idea to convert QWD to MVD before capturing.
            Try yourself.

        - to keep high quality after encoding, you may wish to grab
            screenshots at high res, produce movie also at high res, but
            lower res at the last stage - compression. Most programs
            allows you to specify resolution to which movie is converted
            during compression. For example make screenshots at 800x600,
            but during compression choose 400x300. Of course, capturing
            shots will take much more time, but quality may be better.
            Your higher res should multiply your lower res.

        - play with different compression settings. Compression should
            lower the size, lowering the quality. If you want high quality
            movie, it doesn't mean you need to set all quality values to
            maximum. It might be the best case for your movie, but mayby
            not. (My connection will be 128 kbit, keep that in mind :)

        - if you have same actions twice in your movie, but with different
            playing speed (like first time at normal speed, than slow-
            motioned repeat), capture such actions twice, with different
            speed settings. If you make a slow-motion in movie editor,
            from your 30 FPS captures, the result can be only bad.

        - it may be a good idea to make captures at high FPS (like 150),
            and lower it during final rendering. This way, you can use
            your movie editor effects with good quality. But this
            requires much time, and really good machine.

        - I really suggest Windows NT4/2000/XP for such job, you can only
            loose nerves with win9X.

        - In general experiment, try different settings, codecs etc.

- cl_warncmd
        This command was used to block "execing ..." text. Now it is not
        enabled by client automatically after executing config, and blocks
        more prints. If you set it to zero, you will never see any of those
        prints:
        - WARNING: oldcopy on full update
        - WARNING: U_REMOVE on full update
        - WARNING: delta on full update
        - Three keys down for a button!
        - Scripting not allowed..
        - Dup connect received.  Ignored.
        - execing <config>.cfg
        - <key> is not bound
        - <key> is unbound, hit F4 to set.
        - Couldn't load skin <skin>
        - Bad skin <skin>

- some bugs fixed, expecially
        - bug when deleting a source in server browser,
        - bug with 'addserver' command


==========================================================================
 mqwcl 2
==========================================================================

mqwcl2 is meant to be regular mqwcl with features, that not necesarily are
required to play this game. This is a room for many improvements.
Currently the only additional implemented thing is MP3 player.

It is completely unfinished and contain many bugs, but nothing destructive.
But your machine may hang ocasionally. Use at your own risk. For me, it has
proven to be both useful and stable.

First thing you need to know is: mqwcl2 defaults -sndspeed to 44,1 kHz.
Thus, your sound may be a little different. Use -sndspeed 11025 to override
to default settings, but music quality will be poor then.

Setting up
==========

First, you may want to setup your mp3 directory in variable mp3_dir.
To run mp3 player bind it to a convinient key, like this:

bind F12 menu_mp3

This rather should be F* key, because it will also work while in menus.

Some keys:
==========

In 'files'
----------

'/', '\'    - root dir,

backspace   - leaves to parent directory,

enter       - add to playlist (or play if mp3_defaultadd = 0),
              or enters a directory

ctrl+enter  - play (or add if mp3_defaultadd = 0),

alt+letter  - search for a string in this directory,

alt+ctrl+letter - change drive to given letter (like alt+ctrl+a
                will select floppy disk A),


In 'playlist'
-------------

enter   - play highlighted track,

delete  - remove from playlist (stops if being played),

1, z, [ - previous track,

5, b, ] - next track,

2, x    - stop (with ctrl pressed fade-stop)

3, c    - pause (with ctrl pressed fade-pause)

4, v    - play

-       - volume down

+, =    - volume up

"," "<" - seek left

"." ">" - seek right


In 'equalizer'
--------------

This is a little complicated.. mayby I'll find sth better

DEL     - reset settings,

TAB     - next position,

shift+TAB   - previous position,

PG_UP   - go to bands,

PG_DN   - go to settings,

If in band:
-----------
arrows  - up and down,

backspace, ctrl+left arrow - one band left

enter, ctrl+right arrow - one band right

If in settings:
---------------
+, -, enter - adjust

arrows - change position


Besides that, mp3 player has many variables with preferences, and some
commands, which you can bind to control MP3 playback in-game. Commands are:

mp3_prev, mp3_next, mp3_play, mp3_pause,
mp3_stop, mp3_info, mp3_add, mp3_open

Variables are:

mp3_dir         - directory for MP3's

mp3_volume      - self-explanatory, values from 0 to 1

mp3_maxwidth, mp3_maxheight - like in server browser,

mp3_files_show*     - if should show some columns in files list,

mp3_files_sortmode  - file list sort mode,

mp3_showstatus      - if show status bar,

mp3_stripnames      - make file names look nices,

mp3_files_movedown  - if move down to next file after adding one to list,

mp3_list_show*      - if should show column in playlist

mp3_defaultadd      - default actions fo enter and ctrl+enter in files list,

mp3_repeat          - if repeat after meeting playlist end,

mp3_list_follow     - if playlist cursor should follow track being played,

mp3_template_list   - song name template for displaying in playlist,

mp3_template_list_nt    - same if sond has no MP3 tag,

mp3_template_status, mp3_template_status_nt - same for status bar,

mp3_template_print, mp3_template_print_nt - same for prints at song start,

mp3_list_print      - 1 - prints song title when track begins as echo,
                      2 - spams song name to all users on server,

mp3_list_autoremove - if 1, will remove tracks from list after playing,

mp3_list_single     - if 1, will stop after each track,

mp3_eq_*            - for equalizer, can be set in menus,

mp3_fade_time       - fade time,

mp3_autopause       - if 1, will pause music during matches, this feature
                      has some errors, for example pauses even if you are
                      a spectator, but still may be useful.