Drake wrote:
quote:
You actually wouldn't need to track partial damage to components outside of combat, so you wouldn't constantly need to store that information with the component, increasing its size everywhere in the game.
True, but if components had a "current damage" stored with them, the easiest coding solution is to make it a universal change. OTOH, since I believe tactical combat is basically a separate program, using to different data structures for components may not be so bad.
quote:
Couldn't you just create a temp damage tracking table one combat starts for all the components? Heck, you'd only need to track components that were hit - when applying damage, if you don't see an entry for that component, it's undamaged.
But this gets messy. How does this "damaged" list indicate that Quantum Engine-III #6 is damaged? The components look identical, but you have six of them. Basically, extra work for the programmer. Not saying impossible, or hard, just extra work. Other solutions are easier to do and would appear to do the same thing.
quote:
I do think this ought to get passed on to Aaron, if it hasn't been already.
Yeah, guess I'll mail it off. Is
se4@malfador.com the address to use?
Re: Armor, Shields and Damage (FAQ)
Threaded Mode