Re: Question on combat procedures

[Jim Kingdon <kingdon@panix.com>]

> The only place I could find something that even fits that is
> action.def where it seemed it went according to the following list.

You should probably see Eric's email which is more likely to be the
answer to your question than what I'm going to say, but here's the
deal on action.def (and by extension, the rest of the .def files which
are used quite a bit).

The idea is that something can #define DEF_ACTION and then #include
action.def.  So for example, actions.c builds up a table actiondefns
(with only 3 of the items from DEF_ACTION).  And kernel.h declares the
prep functions.

The whole can be hard to follow, yes.  But it does allow putting a
bunch of things pertaining to an action in one place, rather than
scattered about.