UnitMakeAbilityPermanent

[Flux]

The spell section demands an ability that will stay permanent even after morphing. So how can I use this function to make an ability permanent to all units on the map? where should I put this, in initialization?

native UnitMakeAbilityPermanent takes unit whichUnit, boolean permanent, integer abilityId returns boolean

 

[Maker]

Event - Unit begins casting an ability
Condition - Ability being cast == your ability
Action -

Custom script : call UnitMakeAbilityPermanent(GetTriggerUnit(), true, GetSpellAbilityId())

 

[Flux]

Ohh, so everytime the spell is cast, I have to call that function.

 

[Xonok]

Not really. You should use it when you add the ability.

 

[Maker]

Yeah, you only need to use it once per unit. But as I do no possess the gift of clairvoyance preventing me from knowing the ins and outs of your spell, I gave you a general solution.

Notice that preplaced units in maps the already have the ability also need to be accounted for.

 

[Flux]

Not really. You should use it when you add the ability.

But it is a Hero Ability and not added by triggers. Where should I use that function?

 

[Wietlol]

Abilities defined in the Object Editor are not removed on morphs.

 

[Flux]

Abilities defined in the Object Editor are not removed on morphs.

But why did BPower said:

UnitMakeAbilityPermanent() should be used to ensure it's working with Meatmorphosis aswell.

 

[Xonok]

Abilities defined in object editor are removed by morphs if the new form doesn't have that ability.

 

[BPower]

You don't have to. Mappers will do that, if required.
However for temporary abilities added by your spell i.e
+Damage, armor, stats, ... or abilities added permanent by
a system i.e UnitIndexers defend, BonusMod bonus, ....
UnitMakeAbilityPermanent is important, so these systems
don't break when using i.e. Metamorphosis.

 

[Flux]

You don't have to. Mappers will do that, if required.
However for temporary abilities added by your spell i.e
+Damage, armor, stats, ... or abilities added permanent by
a system i.e UnitIndexers defend, BonusMod bonus, ....
UnitMakeAbilityPermanent is important, so these systems
don't break when using i.e. Metamorphosis.

Ahh I get it now.

 

[Ezekiel12]

Abilities defined in the Object Editor are not removed on morphs.

Abilities defined in object editor are removed by morphs if the new form doesn't have that ability.

Only abilities under the "Abilities - Hero" field are unchangeably set to permanent and therefore always remain when transforming, normal abilities however are lost if not set to permanent or if the new unit does not have them.

 

[Xonok]

Note that the process seems to work by readding abilities. I assume this because of a bug with spellbooks - when morphing to a unit that has the same spellbook, it gets emptied. This bug is prevented by making the alternate unit have a copy of the spellbook. Even if there are no differences between the spellbooks, it being a copy makes sure the system readds it and thus all spells within it as well.