Here is 2.0 dev 1.
I changed the way I'm labelling dev versions.
Usually 2.0 dev 1 would be the dev version before 2.0 stable got
released and we would now be using 2.1 dev 1.
But I'm not exactly sure how releases will proceed. Some of the
changes in this dev version might become 2.0 patch 1 instead of being
part of 2.1.
So I thought I'd try this new way of numbering.
For anyone familiar with source control management, a good way to
think of it is that dev 1 is a branch off the 2.0 master branch.
I only made one change:
1. Added an apply_ordinal flag to point files. This allows you to
control the order in which point causers are applied. Useful in some
advanced situations where a unit who runs out of shields transforms
into a new unit without shields and you don't want another point
causer to be applied to it.
So this is to fix the problem Allan is hitting with splash damage.
Allan, to fix your problem put this line:
apply_ordinal 10
in your dragoon shield point file.
The behavior we saw on your map is because Bio health point causers
would inflict their damage first, then dragoon shields, then mech
health, then zealot shields.
These are alphabetical.
Bio health would do 0 damage to a zealot with shields up.
dragoon shields would deal damage to the dragoons and transform them
into unshielded dragoons.
Mech health would then deal more damage to the newly transformed
dragoons.
And finally zealot shield damage would be dealt to the shielded zealots.
So, by setting apply_ordinal to 10 on dragoon shields, we make it so
that point causer will deal its damage last.
Which means mech health will have already been dealt and so the newly
created unshielded dragoons won't take additional damage.
apply_ordinal is 0 by default and causers are now applied in order of
the apply_order flag and then alphabetically if they have the same
apply_order number.
HTH,
~ Ian Reed
