Changes between Version 4 and Version 5 of ioquake3

Timestamp:

Jun 23, 2011 12:45:57 PM (13 years ago)

Author:

jpawlick

Comment:

--

ioquake3

@@ -1 +1 @@
 The following is what I've learned about the ioquake3 engine, which I hope will be helpful to you guys while I'm away.
 
-== General Terms ==
+== General Terms & Tips ==
+=== Finding Things ===
+Trying to find a struct or function definition? Your best bet is probably grep. Most structs (though not all), you'll do better looking for structname_s rather than structname_t, since the _s version is usually only used in the definition, and _t will return a lot of chaff. Function definitions you can probably narrow down by only selecting lines that also contain a "{". Example:
+{{{
+grep -r "BotQuagentAI" code | grep "{"
+}}}
+Most things that you're looking for will probably be in the code/game directory or the code/qcommon directory.
+
 === Frames ===
 We call an iteration of a game-driving loop a "frame". Because the client and the server are on different machines, client frames and server frames may operate at completely different frequencies. Quagent AI is called every single server frame (unlike normal Quake bot AI). This is unlikely to cost much computationally on a modern machine, since they are far more powerful than machines made in the early 90s.