Do u know ne modding tutorials for ET?
For example I’d like to know what to do for adding a new say-command (equivalent to qsay of etpro), but everything i tried simply didnt work or i didnt find the max-clip-ammo var for the garand, … id simply want 2 know if ne1 has created a faq or a tuto explaining basic things like that for getting ready to code harder things …
THX4YA’HELP!
You might want to have a look at http://code3arena.planetquake.gamespy.com/
It’s for q3, but the organization of the code is pretty similar. I’m not aware of any modding tutorials specific to ET.
though ive been modding for quite a short period of time now ive noticed sth:
“egrep -i string ur searching 4 egrep -i etmain ui/* cgame/* game/* botai/*” while in src-dir helps a lot!
^^ this made me find the ammo-var for teh garand within 5 minutes …
Yes grep is your friend 
Whenever I don’t know where to start looking for something, I either grep for likely terms, or start at vmMain and work my way down.
Taking the time to get a feeling for the basic layout and Q3 API is also worthwhile.
the gamecode is devided into 3 VMs:
cgame/ <- client gamecode
game/ <- server gamecode ( except game/bg_* is linked to both game and cgame, for prediction or shared constants)
ui/ <- user interface
the bot stuff is dead, and so can be ignored.
Each of VMs api is defined in <vm>_public.h
Possible calls into the VM are defined by the <vm>Export_T enum. <vm>_main.c vmMain handles all of these.
Calls from the VM into the engine are defined by the <vm>Import_T enum. These are wrapped with functions in <vm>_syscalls.c
You’ll notice that cvars follow a similar naming convention
cg_ -> cgame
g_ -> game
cl_ -> client engine
sv_ -> server engine
r_ -> renderer
and so on. Of course, like any naming convention, there are exceptions and things that don’t fit nicely.
Q3 source code editing related book:
Focus On Mod Programming in Quake III Arena (The Premier Press Game Development Series) (Paperback)