Armor, Shields and Damage (FAQ)

[apache]

Wow, that is some damn fine research work. Definitely organic armor should not add up extra points if there is no partial damage.

" 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."

But you don't have to know which one is damaged. Like you said, they are all identical. If one of your Quantum engines are partially damaged, then who cares which one it is? The program could automatically count damage on the first component in a list of identical components, if one of those are selected to be damaged. Once that one is destroyed, it could pick another component to damage.

[Drake]

quote:

---

Originally posted by Zanthis:
How does this "damaged" list indicate that Quantum Engine-III #6 is damaged? The components look identical, but you have six of them.

---

Well, I don't know the data structure for how the game was programmed, or any of those details. However, when I design something, usually each object has a unique identifier so other objects can refer to it. Simply keep a separate current damaged list, and on it you have the component ID, and the points of damage taken. Only necessary for combat, and anything on the list isn't damaged.

I only proposed that method though because you brought up the point that modifying the data structure of components to add partial damage might be a problem in terms of extra memory needed to process. Since you don't need the info outside of combat, restrict it to the combat engine only. If adding partial data info isn't a big deal, then add it. Either way, problem fixed.

-Drake

[Zanthis]

Again, individual component damage would be ideal in combat. But it introduces several considerations. Suppose you have two pieces of Armor III. You get hit for 20 damage and the first piece is selected (randomly). Now you take another 20 damage. Does the program a) randomly select between the two pieces b) pick the damaged piece automatically.

If b, there are easier ways to duplicate that effect without tracking component damage.

If a, you will be changing how ships take damage. With 10 pieces of organic armor, ignoring the regeneration, you could take 1490 damage and not have lost a single component! Basically, ships will get tougher.

Also, it is quite likely that the same code that handles components outside tactical combat is used in tactical combat. Making changes to the tactical code's component class means maintaining two different pieces of code. This makes bugs more likely and is generally a hassle. The other methods involve creating an entirely separate system for tracking component damage outside of the component objects. Messy and quite a bit of work.

All in all, I don't think it is necessary. With a few fixes to the current model, we'd have something that worked exactly like we expect it to. Those changes would be:

1) Stop adding "extra damage" to weapon damage. Instead, add weapon damage to extra damage.
2) Switch to two "extra damage" values. One for "extra armor damage" and one for "extra internal damage."
3) OPTIONAL. Keep track of which armor component is currently being beat on (but not yet destroyed). Also, keep track of which internal component is being beat on.

Of course, all of this isn't very useful because, in the end, the fix will be whatever Aaron decides and will likely be based on information we have no way of knowing.

As long as everything acts like its supposed to, I'll be quite happy. I consider Crystalline Armor to be the biggest offender, followed by pulling damage out to strike shields (which is part of CA's problem anyway) and OA Last. I say OA Last only because changing it without making it worthless is going to be difficult.

[Drake]

I don't know that I'd have it randomly pick a component with each hit, since that would be a big change. I'm not sure it'd would've been a bad design to start with, but changing it now...

I don't think adding just one more damage value type would be sufficient. You have weapons which damage just shield generators, engines, weapons, etc. Wouldn't you need to remember each type separately?

I guess the real reason I favored component damage tracking is it more accurately reflects the 'common sense' approach of what would really happen in combat. The way it now works might have been considered an easier way to achieve the same results, but ended up giving us some odd behavior. I guess I view coming up with another workaround that should better approximate things to be more prone to bugs than new code would be.

quote:

---

Of course, all of this isn't very useful because, in the end, the fix will be whatever Aaron decides and will likely be based on information we have no way of knowing.

---

I couldn't have said it better. Without access to how it was originally written, it's hard to say with certainty that it would be easier to fix one method vs another, IMO.

-Drake

[Zanthis]

Drake wrote:

quote:

---

I don't think adding just one more damage value type would be sufficient. You have weapons which damage just shield generators, engines, weapons, etc. Wouldn't you need to remember each type separately?

---

Whoops. Yes, you are correct. I never use component targeting weapons, so I had forgotten about them. However, you could just use the "extra internal damage" for them. That would cause a few slightly wierd effects, but all in all, I doubt you could abuse the effect or, possible, even notice it.

[Sinapus]

quote:

---

Originally posted by Zanthis:
Again, individual component damage would be ideal in combat. But it introduces several considerations. Suppose you have two pieces of Armor III. You get hit for 20 damage and the first piece is selected (randomly). Now you take another 20 damage. Does the program a) randomly select between the two pieces b) pick the damaged piece automatically.

If b, there are easier ways to duplicate that effect without tracking component damage.

---

Since armor is supposed to be hit first until destroyed, why not line up the armors and have the damage go from left to right as the damage accumulates? Use random hit determination for damage that gets inside the armor and keep track of those components' damage.

quote:

---

If a, you will be changing how ships take damage. With 10 pieces of organic armor, ignoring the regeneration, you could take 1490 damage and not have lost a single component! Basically, ships will get tougher.

---

Actually, that was what I thought the damage rating for armor was supposed to do. Which is why I only use standard armor for protection. (I use stealth armor as a cheap cloaking device early in the game. I don't play w/organic tech.)

quote:

---

Also, it is quite likely that the same code that handles components outside tactical combat is used in tactical combat. Making changes to the tactical code's component class means maintaining two different pieces of code. This makes bugs more likely and is generally a hassle. The other methods involve creating an entirely separate system for tracking component damage outside of the component objects. Messy and quite a bit of work.

---

Would it be possible to have something in tactical that adds up damage for a component, destroying it when it takes enough damage, but when you return to the regular game it only takes note of which components were destroyed and any components that survived are presumed to be functional? Say emergency repairs by the crew patched it up and such.

Say, something hits the engine with enough damage to destroy it so it gets marked with the destroyed part. Another component, say a weapon, takes some damage, but not enough to destroy it and it stays functional when tactical ends.

quote:

---

Those changes would be:

1) Stop adding "extra damage" to weapon damage. Instead, add weapon damage to extra damage.
2) Switch to two "extra damage" values. One for "extra armor damage" and one for "extra internal damage."
3) OPTIONAL. Keep track of which armor component is currently being beat on (but not yet destroyed). Also, keep track of which internal component is being beat on.

---

Keeping track of internal components sounds better to me. Just how to apportion damage w/o making it like Starfire is something I, as someone who isn't a coder, has no idea of how to implement. IIRC, you really can't make 'random' numbers, but can 'fake' it in the code somewhat. Or maybe I have no idea what I'm talking about.

So far all I can think up is taking the damage from one weapon, picking a component to hit and recording damage from left to right. If it destroys the component w/leftover damage, that damage gets transferred to the next component, either the one immediately to the right, or randomly picking a component until the damage is used up, then the next hit picks a component to do damage to. If later hits pick an already destroyed component, it will travel to the right of the component list until it reaches an undestroyed component.

Okay, it's sort of like Starfire, but with a bit more randomness to the damage locations.

quote:

---

Of course, all of this isn't very useful because, in the end, the fix will be whatever Aaron decides and will likely be based on information we have no way of knowing.

---

True.




------------------
--
"What do -you- want?" "I'd like to live -just- long enough to be there when they cut off your head and stick it on a pike as a warning to the next ten generations that some favors come with too high a price. I would look up into your lifeless eyes and wave like this..." *waggle* "...can you and your associates arrange that for me, Mr. Morden?"

[Seawolf]

While I understand the concept here I wonder then do we want a damaged components to have any penalty assigned to them? Or are all these changes only for destruction of components?

------------------
Seawolf on the prowl