This script hasn't been tested with any of the new releases - it was developed for the "spring release" (2007-04-13) - it might still be interesting for CubeScripters as a reference or example, but since it doesn't use any of the newer scripting commands it's methods and functions can probably be improved upon quite a bit if you start using functions incorporated into the game since 2007 (which was 3 years ago at the time I added this paragraph).
history
v0.1a : alpha release
v0.2 : added DOC-Strings and the voting-function-set
v0.3a : some fixes and additions, HTML-doc still bare skelleton only
v0.4 : fixed some bugs
v0.5a : overhaul and functions added
2010-03-30 : fixed the link to the online-README
2007-05-27 : v0.5a
2007-02-03 : v0.4b4
Usage
Use the GUI menu to power your editing,
the F1 key will popup the Q menus.
Toggle your function sets via N + MouseWheel,
for editing and gameplay different sets are used.
See the documentation README_QCSP.html before downloading, it's contained in the ZIP;
although the stylesheets will only work if you copy them from the install-dir into home-dir/docs/style.css
Don't forget to move your config.cfg before running the first time,
salvage "bestscore_MAPNAME" aliases from it later to the newly written config.cfg!
Config
Basic setup is in the top section of packages/QCSP/init.cfg
Change the value of _QCinfo to your liking, 1 is default and gives only short info, 2 for long, 0 for minimalistic sound supported navigation (geeky)
Your personal/enhanced function sets are in QCSP/iota or QCSP/epsl (for game or edit function-sets respectively).
Gamers
This section is for those little things you sometimes need,
but forget exact syntax for or so.
Put them into a function-set-cfg and quickly scroll to it(n), execute[one of 1-9], and back to weapons (0)
Editors
LALT (left Alt-key) is now your turbo-key, speeds up texture scrolling and entproperty control.
Use your number keys for a range of different functions,
for in-game and in-edit with seperate function-sets ... naturally ;)
MW + J is your gamespeed modification in steps of a bounded list : "10 30 50 100 200 500 1000"
A silent echo to your console is the only feedback you'll get mostly.
On 100, 10 and 1000 you'll get DEF, MIN and MAX messages printed.
Your function sets are in packages/QCSP/epsl/*.cfg, add new functions-cfg's just like for QCSP/iota/.
// Config script