That's alright, just throwing them out there.
Thanks!
On 4/25/15, Craig Brett <dmarc-noreply@xxxxxxxxxxxxx> wrote:
The first 2 look like ones that could be handled in script. I'll have a
look at that if ever I get time. Not priority though.
Individual flags don't inherit from each other. Not really. Not unless
we want to explicitly throw an error if the user was to put passable
terrain before terrain limit. Otherwise how do we know which to use? I
could store both on the units, but then the code to see whether a unit
could move or whether the AI can move will get messy if I have to check
3 lists rather than 2. I'll think about it. I'm making no promises.
On 25/04/2015 06:23, Monkey wrote:
Hello,
Reposting this list of ideas that were in two different emails.
Is it possible to form a direct link between an effect and a skill? So
if a skill inflicts a damage of say 4r8 on a unit and the skill is
supposed to restore that range of health to the user...is that doable?
Because just putting in the same range for damage inflict on the skill
and then health restore on the self effect doesn't work like that.
This one might be one for scripters, is it possible to make it so that
a unit can literally absorb damage from attacks? I was thinking of two
possibilities. Absorb and then convert the damage into health regained
if a certain damage type is used on it, or absorb a certain percentage
of the damage to reduce the overall damage taken without making the
skill do nothing at all to the target in question.
Why not have the terrain_limit= flag do the same thing as it does, but
change the passable_terrain= flag to something similar to
impassable_terrain=, where any terrain added to the passable list can
be passed in adition to what units can normally move over? So if I
have an aligator, the aligator can move on terrain that everything
else can, but the passable_terrain= will add water to the list. And
perhaps it could combine with the terrain_limit= flag, through
inheritance? Just a thought.
