[Zanthis]

SunDevil:
Well, they do each have hit points right now. At least, they have a maximum hit points. They *don't* have a current hit points because they cannot be damaged, only destroyed.

This is most likely a programming choice for two reasons. First, it is easier (less code to write) to just not track individual component damage. Second, it requires less space (memory). Every component would get bigger by at least 2 bytes. How many components have you seen in tactical combat? Not that many right? But guess what, it would increase the size of every components in game, not just in combat. So, how many components have you seen anywhere in the game at one time (remember to include fighters, troops, mines and platforms)?

The only way to avoid that memory waste would be to make two Versions of the component structure, one with current hit points, one without. Then, in tactical combat, use the former, otherwise, use the latter. Lots of programming and doubles the work required whenever code changes are made to the components structure (since you have to change both Versions).

Drake:
Another possibility is to have two "this is the component we are trying to kill" pointers. One for normal attacks, which will typically be pointing to a piece of your armor, and one for armor-skipping attacks which would be pointing to something other than armor.

I said in the FAQ that I thought they already did this (using only one pointer) so it shouldn't be a problem to implement two.

[This message has been edited by Zanthis (edited 06 February 2001).]

[This message has been edited by Zanthis (edited 06 February 2001).]