I'd like to know if someone can confirm this bug ?
The validator Unit Compare Ability Level seems to have a bug, in data and in triggers too. The lvl 0 or lvl 1 of an ability provide both the result 0. Then with the level 2, I get the result 1. Etc.
So there is no way to differenciate the level 0 (the ability is not learnt) from the level 1.
It seems to work fine in the requirements though, but I encounter this issue in validators and triggers.
The solution is to not level abilities but to make them scale with buffs or other means. Ability level mechanics in SC2 are extremely buggy, especially when used with a Learn type ability.
Say one makes a 3 level ability like a Warcraft III standard hero ability. Level 0 is both unlearnt and just learnt (WC3 level 1) so cannot be used to test if an ability has been learnt. Level 2 is the theoretical maximum (WC3 level 3). However there is also a level 3 if you queue up learn orders or use triggers (WC3 level 4!?, it should not exist) which can not only waste a Learn ability skill point but also bug/break triggers and ability mechanics.
Trigger events relating to learning an ability will fire each time the ability is issued to be learnt, not how many times it is learnt. If one has a Learn ability with 4 skill points and uses it to learn a 3 level ability currently unlearnt by queing up its learn orders until maximum queue count then a trigger firing in response to learning will run well over 10 times (maximum queue count times) and the ability will be level 3 (WC3 level 4).
Hello,
I'd like to know if someone can confirm this bug ?
The validator Unit Compare Ability Level seems to have a bug, in data and in triggers too.
The lvl 0 or lvl 1 of an ability provide both the result 0. Then with the level 2, I get the result 1. Etc.
So there is no way to differenciate the level 0 (the ability is not learnt) from the level 1.
It seems to work fine in the requirements though, but I encounter this issue in validators and triggers.
Interesting. At least you can use the Player Requirement validator and a requirement.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
An answer of Kelphe (Blizzard Quality Assurance) is to use the ability validator to check if the unit has the ability + check the level after.
Makes sense now, even if it is not very intuitive.
I have tested and it works fine, at least for the validators. Not tested for the triggers.
The solution is to not level abilities but to make them scale with buffs or other means. Ability level mechanics in SC2 are extremely buggy, especially when used with a Learn type ability.
Say one makes a 3 level ability like a Warcraft III standard hero ability. Level 0 is both unlearnt and just learnt (WC3 level 1) so cannot be used to test if an ability has been learnt. Level 2 is the theoretical maximum (WC3 level 3). However there is also a level 3 if you queue up learn orders or use triggers (WC3 level 4!?, it should not exist) which can not only waste a Learn ability skill point but also bug/break triggers and ability mechanics.
Trigger events relating to learning an ability will fire each time the ability is issued to be learnt, not how many times it is learnt. If one has a Learn ability with 4 skill points and uses it to learn a 3 level ability currently unlearnt by queing up its learn orders until maximum queue count then a trigger firing in response to learning will run well over 10 times (maximum queue count times) and the ability will be level 3 (WC3 level 4).