I edited the 1.03 Client Guide for language and updated it to reflect changes in 2.0a. However, I don't consider it complete. Also, please note that it was designed for the OpenArena Community not Quake III.

http://oa.goquake.com/wp-content/e+_docs/client.html

Anyone is welcome to edit and use it as the basis of a new Client Guide for E+ on Q3.

I will have a server version done sometime over the weekend or early next week. I will post the link here as well.

http://oa.goquake.com/wp-content/e+_docs/server.html

I have, a idea, how more further documentation can progress

I say all documents can have a option for a different languages, I've with pleasure will translate to mine native language some most important things.

split please separately Client Cvars & Commands to:

Client Commands

Client Cvars 

That way at cvars section we can add some cool stuff examples with vstr's:

like 2 guns binded on 1 button

like Gama, sound, or fow, or connections switchers(increase decrease) on one button,

like separate sensitivities to separate guns and something like

cause now cvars/vstrs have no place, commands section is for default commands, but not for stuff that can be made combining all

thanks

its just more comfortable way - but you know i use it cause my fingers arent that long ..  same scripting is used to do those fow or sound or gama increas/decrease or demo recording, speking about demo (so it hink users can have and use these things):

created demo entry maybe there can be 3 sections 

simple demos

mvd demos

avi demos

OR it IS OK as it is cause there isn't much info about it (i think)

EDIT: agree, there is topic http://www.excessiveplus.net/forums/thread/should-using-of-scripts-be-allowed

created getting started section