What you want is just to enlarge the Object Editor tables of units.
However... that is not possible just like that.
What you want is specify two values for each unit type:
- Armor Type
- Damage Type
To have such data, you need an array to put them in.
To use unit type id's as indices, you need a hashtable because arrays dont reach far enough to store it... neither will they be very convenient for it.
You create a hashtable variable in the Trigger Editor.
Then you create a trigger that runs on map init that creates a new hashtable and sets the variable to that hashtable.
-
Actions
-
Hashtable - Create a hashtable
-
Set UnitTable = (Last created hashtable)
Just below that, you just do "Hashtable - Save Integer".
The unit type id is technically an integer but it doesnt work in GUI like an integer.
So we have to abuse a small trick with variables and JASS script to pass on the data from one variable to another.
-
Actions
-
Set TempUnitType = Footman
-
Custom script: set udg_TempInteger = udg_TempUnitType
-
Hashtable - Save 0 as 0 of TempInteger in UnitTable
-
Hashtable - Save 0 as 1 of TempInteger in UnitTable
Now a Footman has in row 0 and 1 the integers 0 and 0.
Ofcourse you dont want 0 and 0 but to do that properly we have to create the armor and damage types first.
(Be sure to use unique integers in the default values!)
So now, you can say:
-
Actions
-
Set TempUnitType = Footman
-
Custom script: set udg_TempInteger = udg_TempUnitType
-
Hashtable - Save DAMAGE_TYPE_BLUNT as 0 of TempInteger in UnitTable
-
Hashtable - Save ARMOR_TYPE_UNIT as 1 of TempInteger in UnitTable
You can technically change those 0 and 1 into something like "UnitTableRow_DamageType" and "UnitTableRow_ArmorType", but you wont be really needing those yet.
In any case, now you have to define the damage factors:
This table is small enough to place in a real array so we wont bother using a hashtable. You can use it but it wouldnt be worth the effort.
(DONT USE INTEGER LIKE I DID IN THIS IMAGE! USE REAL INSTEAD!)
First of all, we want to define the maximum number of either armor types or damage types that we use. For convenience (and for optimal use), we use 90.
So we have another global variable:
Now we have a table similar to what I have made in my previous post.
Then you create a "table" from an integer array.
| 1 | 2 | 3 | 4 | 5 |
6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 |
16 | 17 | 18 | 19 | 20 |
21 | 22 | 23 | 24 | 25 |
The only difference is that this table has instead of 5 rows and 5 columns, it has 90 rows and 90 columns.
To fill or read from one of the fields of such a "table", you read by (X + Y*Xmax) or (Y X*Ymax)
Simply said, you do Y multiplied by the total size of the rows (Xmax) so you have the first index of your correct row, then you add X to it so you will be having the right X value.
The other formula is exactly the opposite and works as well.
We can do (DamageType + ArmorType*DamageTableRows):
-
Actions
-
Set DamageTable[(DAMAGE_TYPE_ARROWS + (ARMOR_TYPE_NAVAL x DamageTableRows))] = 0.50
-
Set DamageTable[(DAMAGE_TYPE_ARROWS + (ARMOR_TYPE_HORSE x DamageTableRows))] = 1.00
-
Set DamageTable[(DAMAGE_TYPE_ARROWS + (ARMOR_TYPE_UNIT x DamageTableRows))] = 1.25
With this, you set the damage factor of
arrows vs naval to 0.50
arrows vs horse to 1.00
arrows vs unit to 1.25
You should do that for every single type in your array.
Now there is the exception case.
In some cases, you will not have defined the default value of your armor/damage types or you forgot to add the unit type that you just created in the init trigger to define their armor/damage types.
In those cases, your armor/damage type integer is 0.
It means that you will not fall under any of the damage factors.
You can choose to keep the resulting factor of 0.00 so you will not deal any damage vs those units and those units will not deal any damage against any other units.
It is the best for testing purpose but for prevention of those things in actual releases, you can set all values of index (0, I) and (I, 0) to 1.00 (you can do this in one single loop from 0 to 90 using the same formula of the armor/damage types).
Now all unit types have their armor and damage types.
If you want to be able to change those values per unit independent from each other, you have to create two arrays for those units and store the armor type and damage type from the hashtable in the arrays whenever a unit is created.
You will require a unit indexer to index the units in unique rows of the arrays.
But if you dont want that, then you can just continue with using the data.
To actually make use of this data, you slightly modify your onDamage triggers:
-
Damage Table Effect
-
Events
-
Game - PDD_damageEventTrigger becomes Equal to 1.00
-
Conditions
-
PDD_damageType Equal to PDD_PHYSICAL
-
Actions
-
Set PDD_amount = (PDD_amount x (Load ))
-
Actions
-
Set TempUnitType = (Unit-type of PDD_source)
-
Custom script: set udg_TempInteger = udg_TempUnitType
-
Set TempUnitType = (Unit-type of PDD_target)
-
Custom script: set udg_TempInteger2 = udg_TempUnitType
-
Set PDD_amount = (PDD_amount x DamageTable[((Load 0 of TempInteger from UnitTable) + ((Load 1 of TempInteger2 from UnitTable) x DamageTableRows))])
Now you need two integer variables to store both the target and the source...
You may want to use arrays for TempVariables but that is all your choice.
In any case, this trigger will make all damage be applied with the damage factor from the table.
There is only one butt (_._)... if your DDS doesnt have a damage amount modifier variable, then you are pretty much fcked up.
I know what DDS you use, and I know how to check if it has one, but I am too lazy for that.
The problem that you may see is that when you have your damage be modified by triggers and you increase damage by 100 for example, that damage will NOT be multiplied by this value. You require to have at least 2 values (Damage amount, Damage modifier) to deal proper damage in every case.
I personally use 3:
Damage amount: Just a value
Damage modifier: Multiplication of Damage amount.
Damage bonus: Bonus value without being modified.
Aka:
DMG = (amount * modifier) + bonus
But that is only optional.
