I've created a spreadsheet (so has amish) to take account increasing and decreasing mitigation, hull and shield regen between fire, and damage  decrease due to armor and shield mitigation (and combo of) and still can not get it to follow actual results. 

Spreadsheets say that assailants should win in 1v1.  Theres a missing factor that I'm not getting that allows a lum to win with 200+ hp

The previous thread is found here:

https://forums.sinsofasolarempire.com/365992

Amish's spreadsheet takes into account shield regen, hull repair, armor, and shield mitigation.  I found it hard to play with, because it appears to be hand calculated, but maybe it's just because OO Calc can't open the file correctly.  I don't think JJ posted his spreadsheet yet, but his post seem to indicate that it was the case.

Not sure what the conclusions are exactly, but here are the problems encountered thus far:

1. Neglecting all reduction and regeneration, assailant should win by ~20s. (JJ, opening post).  Does not predict the right winner.

2. Taking into account hull repair, shield regen, armor, and shield mitigation; and adding a 2s delay to mitigation decrease, illum wins by ~150 health (Amish, reply #7).  Does not predict the winner shield mitigation numbers.

3. Taking into account hull repair, shield regen, and shield mitigation only, assailant should win by ~20s (with_an_e, reply #9).  Does not predict the right winner.

The test appear to indicate that shield mitigation is based on damage prior to shield mitigation and armor rather than the reduced number.

It's possible that the developers don't really want the players to know the precise game mechanics, possibly to discourage long theorycraft discussions or to reserve the ability to make tweaks to the system without making large chunks of user knowledge obsolete.

Me and my calculator still do not make sense of what it being noticed ingame. I too predic the assailant winnig in a 1v1.

herm... what if armor is applied to damage before shield mitigation? i know that makes no sence... but were running out of combinations, right?  (in other words... reduce the damage by 5%, and THEN do the shield mitigation up by 10 damage, down by 1.25% thing.

or... mabye armor does not apply while the shields are still up? would make more sence...

Are you guys testing with stock ships, or with some upgrades? Maybe Assailants just suck w/o the phase-missile upgrades... could be design. Are you adjusting for who gets the first shot? Is rate of fire equal? What about the side beams, does the AI utilize them at all (to fire between forward beam recharges)? Are you testing in game or just going by statistics from a file (maybe stats don't tell the whole formula)? Maybe there's a bug in the code that determines how dmg is applied?

Sorry that I can't really help you guys math things out, but mebbe if I throw bulk comments at you it will make something click in your brains. If you want me to stop, just say the word.

-Itharus

Dont try to understand it, just disable it  

I have done so (also increased ship HPs a little bit to compensate) and I think the game is better without it, more action packed and less complicated and unrealistic, and and most importantly the battles dont take eons like before ( I actually see more than one explosion at a time ), but still you are able to retreat or call reinforcements in time ( without mitigation its just a matter of dmg/hp ratio)...

Yet another shameless plug for MP by Dirty!!!!!

Of what Ive seen look at the increase it seems to happen after based on the infocard. But Im not sure how reliable that is. 

Actually, I've always thought that the way mitigation works sounds far more realistic than having a big impenetrable energy bubble blocking physical objects.

It's quite possible to run a charge through the hull of a ship (or any material), we do it now. It can help shield from certain types of radiation/other charges. It's kinda like polarizing a thing. Shield Mitigation as we know it is just some charge they've discovered that they can tweak the harmonics of to essentially reorganize the material a bit (or just fill the empty spaces) at a subatomic level that strengthens the armor so long as the current is in place... they alter that current to fit the weapon impacts and blah blah to increase the dmg resistance.

Anyhoo... /sidetrack

Actually, I would predict that removing mitigation would put vasari at the greatest disadvantage.  Shield mitigation applies equally to damage done to shields and to hull.  Removing it will make both shields and hull deplete at a faster rate.  The only advantages Advent would lose are 1. a late game research that increases their max shield mitigation by 4%, which is about a 10% damage reduction for frigates and structures and around 12% for capital ships. 2. marginally total shields regenerated because battles are now shorter.  Compare this to what the Vasari would lose.  Currently, they can have phase missiles that give up to 30% penetration, which increases their damage output by over 30% because it also ignores mitigation.  Removing shield mitigation means the first 6 phase missiles research are worthless against any ship that has less than a 7:3 shield:hull ratio, i.e. they're worthless against anything except guardians.

I think that the damage is calculated at the time the burst is fired, but then the damage is applied in one of two ways-

BACKLOADED and OVERTIME. BACKLOADED damage types will apply damage after all particle effects for a weapon burst have hit the target, OVERTIME will apply the damage incrementally as the particles hit the target. OVERTIME is usually used on beam weaponry in the game, though the Advent SB's laser batteries have OVERTIME damage, so do the Orky's Disintegrators.

Ok, here is how it works in the most detail you could possibly ask for - the actual code.

First, everytime there is a damage application, the following is called:

void IDamage::UpdateShieldBonusGrowth(float totalDamage)
{
 if((IPlayerOwned::GetEntityPlayerOwnerIndex(thisEntity) != -1) && (thisEntity->GetIDamagePtr()->GetMaxShieldPoints() > 0.f))
 {
  const PlayerShieldData& playerShieldData = thisEntity->GetIPlayerOwnedPtr()->GetPlayer()->GetIPlayerPtr()->GetDef()->shieldData;
  m_shieldBonus += playerShieldData.shieldAbsorbGrowthPerDamage * shieldDamage;
  float max = this->GetPreBuffMaxShieldMitigation();
  assert(max < 1.f);
  m_shieldBonus = Math::Min(m_shieldBonus, max);
  assert(Math::IsFinite(m_shieldBonus));
 }
}

Then on a regular schedule, the following is called:

void IDamage::UpdateShieldBonusDecay(float timeElapsed)
{
 startProfiler(_T("UpdateShieldBonusDecay"));
 if(IPlayerOwned::GetEntityPlayerOwnerIndex(thisEntity) != -1)
 {
  const PlayerShieldData& playerShieldData = thisEntity->GetIPlayerOwnedPtr()->GetPlayer()->GetIPlayerPtr()->GetDef()->shieldData;
  m_shieldBonus -= playerShieldData.shieldAbsorbDecayRate * timeElapsed;
  float min = playerShieldData.shieldAbsorbBaseMin;
  m_shieldBonus = Math::Max(m_shieldBonus, min);
 }
 stopProfiler();
}

We you blair!!!

edit... now... what are the values of those constants... and what are those functions called do...