Template talk:Ability

Cargo query problems
It seems like the way we are handling talent values in this template won't work with Cargo. When storing a value, that is generated by querying another value stored by the same template, Cargo always stores  instead of that new value (it gets displayed correctly on the page though). See my idea for a solution below:

Possible fix: Setting variables for each value and accessing those variables instead of querying Cargo. This is obviously not ideal, and if anyone has a better idea, please let me know. -- Litzsch 08:56, 27 April 2018 (UTC)
 * Example:
 * Before:
 * After:
 * Advantages:
 * Good performance
 * Does not introduce any additional syntax/templates
 * Disadvantages:
 * Values can only be accessed after they are set (e.g. they can't be used in the ability description).


 * Update: It's worse that I initially thought; the problems don't seem to be limited to values stored by the same template, but also affect other values stored on the same page. I think (needs more testing) all values stored by the same template and below it are affected. -- Litzsch 09:09, 27 April 2018 (UTC)


 * Is  the same problem? --Elite stay (talk) 13:20, 30 April 2018 (UTC)


 * Yes. It's due to Module:Calculate getting  as one of it's parameters and the passing that to the #expr parser function. -- Litzsch  13:48, 30 April 2018 (UTC)

var order
Items like have error with the cooldown. --Elite stay (talk) 12:17, 23 June 2019 (UTC)
 * I don't see any issue with the page. Can you describe further? -- Sanhard 17:48, 23 June 2019 (UTC)
 * I think that it's "-1". Medok  17:56, 23 June 2019 (UTC)
 * Yeah, that's caused by "Order of Evaluation" of template parameters when variables are being initialised. Should be resolved. -- Sanhard 13:21, 24 June 2019 (UTC)