Yeah, thats the only problem though, because i myself am new to coding but im reading up on Quake C and trying to digest it slowly, but when you see code being churned out, I find it hard at times to grasp where people get what parts to put where to make certain things happen. Also if possible, could somebody set up a glossary for Quake C and a beginners turtorial with full explaining of what each part of code has an effect on what area and the concept of creating a model then making it come to life with code from our animations, but im guessing what i said is probably easier said than done so im gonna button it.

(Just a suggestion thats all)