Small Changes for damageBase

[Anonymous]

posted on November 21st, 2011, 9:31 pm

Last edited by Anonymous on November 21st, 2011, 9:33 pm, edited 1 time in total.

I just got an idea on how a weapon could more easily deal damage to both hull and shields without adding a dozen new commands.

Sample Torpedo:

Code: Select all

// If true, the shield protection value will have little effect.
// If false, a shield protection value of 1 will block the torpedo (can also be used for adapted photon torpedoes)
isChronitonTorpedo = 1

// Fleet Operations may have this set to 1 by default because of the passives being range-based.
omitHullAndShieldMultipliers = 0

// damageValue hullDamageMultiplier shieldDamageMultiplier attemptedHullDamage
damageBase =        25 1.0 1.0 0.8  // Shields provide some resistance by default
  "fed_monsoon.odf" 25 1.0 0.5 0.6  // High-density shield generators provide some additional resistance
  "fed_descent.odf" 25 1.0 1.0 0.4  // Multi-layer shields are the most effective

For formula's on how this will work, I think that:

if isChronitonTorpedo=1
if target's shields are up
H = p/((d*y)*a)
S = p/((d*y)*(1-a))

if target's shields are down
H = d*x
S = 0


if isChronitonTorpedo=0 & shieldProtection=1
if target's shields are up
H = 0
S = d*y

if target's shields are down
H = d*x
S = 0

if isChronitonTorpedo=0 & shieldProtection < 1
if target's shields are up
H = p/((d*x)*a)
S = p/((d*y)*(1-a))

if target's shields are down
H = d*x
S = 0

---

H = damage done to hull
S = damage done to shields
a = percent of damage to attempt to do to deal directly to the hull
x = damage multiplier for hull
y = damage multiplier for shields

---

Well, I'm not sure if it's truly "simpler" to implement since it just adds the commands in my previous request as arguments for this command, but when programming the individual ODF files (mostly for mods since FO always has shield protection set to 100%), it would be a huge time saver over the system in my previous request.  Also, I am aware that this may not be a priority (if it's considered for implementation, or if it's even possible right now), so no pressure is intended.

EDIT:  Formula colors are now red for visibility.