GetMultiDamage¶
A method that allows to precalculate the sum of all damages that could happen from CalculateBaseDamage had multiple player party members combined their attacks and damage influence. The method simulates damage effects as if it was done with a player attacker for each player party members involved and adds them together before returning the result.
The intent with this method is to use the precalculated number in DoDamage as the damageammount, but without an attacker. This allows to have every effects from the target's side apply, but to not reapply the effects the attacker side would have because DoDamage no longer has an attacker. It acts as a stopgap to have multiple player party members be the "attackers" which isn't possible with DoDamage alone. This method has some caveats, see the details below.
private int GetMultiDamage(int[] ids)
Parameters¶
ids: The trueid arrays of the player party members that will be involved in the multi damage simulation. Due to this only working for the player party, only 0, 1 or 2 are valid elements (Bee,BeetleandMothrespectively)
Procedure¶
The following is a table of all the effects applied to the result in order for each player party members whose trueid is in ids and the conditions for the effect to apply. The result is a local value starting at 0 and the effect column describes what happens relative to the player party member involved in the calculation. The sum of this table for all involved player party members is what will be returned as the result clamped from 1 to 99.
NOTE: This clamp at the end can skew the results because it negates the influence of having all involved player party members with 0 or negative
atkvalue with no bonuses. However, it should be noted that unlike most player actions, this precalculates the EFFECTIVE damage instead of the base one that is typically sent to DoDamage in a player to enemy flow. Due to this, the bad influence of this clamp is close enough to what would have happened if DoDamage was called withAtLeast1orAtLeast1Pierceas the property which is well defined.
| Conditions | Result effect |
|---|---|
| None | + atk |
| None | + charge |
| The player party member has the AttackUp condition | + 1 |
| The player party member has the AttackDown condition | - 1 |
| The player party member has the Poison condition | + (amount of PoisonAttacker medals equipped - amount of ReversePoison medals equipped) NOTE: The ReversePoison influence here is incorrect, see the caveats section below for details |
The player party member's hp is 4 or less |
+ amount of AttackUp medals equipped |
| None | - tired |
Known caveats¶
There are a few known problems with this precalculation scheme when calling DoDamage without an attacker where the logic differs than the regular damage pipeline:
- The
ReversePoisonmedals should normally have removed 1 defense, but here, it penalises the raw damages done from the player party side which is the same then removing 1 attack which isn't what the medal was supposed to do - This method doesn't account for the front bonus CalculateBaseDamage normally accounts for and it cannot be accounted for because DoDamage has to be called without an attacker while a player attacker is required to process the front bonus
- This method doesn't manage the logic related to the
LifeStealmedal and it cannot be accounted for because DoDamage has to be called without an attacker while a player attacker is required to process the effects of this medal