Template talk:Recharge table

Is there any way to use this template to show reduced recharge from traits for Transform skills like Rampage's and bundle skills like Bomb Kit's? Mith🌟Talk 22:48, 22 October 2019 (UTC)

Added skill context "transform". However, the bomb kit cannot be added easily due to several reasons. Currently this template works with the property "Has skill type" and runs through all possible skill contexts, e.g. weapon, healing, utility, elite, and now also transform. Unfortunately, bomb kit skills don't have a skill type, the template maybe could work with "Has parent skill" but I haven't tested this yet.

Furthermore, Short Fuse table is rather complex with additional columns, which cannot be created automatically at all. Hence, should I even try to implement it for bundle skills without a skill type? --Tolkyria (talk) 23:13, 22 October 2019 (UTC)

Add suffixes to show the game mode

Please add suffixes to the skills to show the game mode for skills that are split. --BuffsEverywhere (talk) 09:06, 22 April 2020 (UTC)

Template:Recharge table result format - updated with new template "Template:Game mode". Didn't quite work as intended since if the fact is the same between split modes (e.g. Gale in the first table on Template:Recharge table#Example) then it'll only display (PvE, WvW) when in reality the recharge fact is the same for PvP. Might consider self reverting.

Template:Recharge table result format/Count recharge - currently this template only displays Default/PvE facts for Count Recharge, no idea if that is intentional. Not updated. -Chieftain Alex 09:40, 22 April 2020 (UTC)

Please note that this template didn't show the WvW and PvP version of the skills until this edit was made: Special:Diff/2008822/2036882, suddenly setting the property "Is historical" for split skill subobjects. These skills have been excluded with [[Is historical::false]] here. Whether the missing subobject property "Is historical" was intended or not, many templates relied on it and used it to exclude the split skill subobjects. Furthermore, please note that this template, and several others have been written at a time where the "Is for game mode" property had three values: PvE, PvP and WvW; hence there was no other way than using the "Is historical" property to exclude split skill subobjects (or e.g. we couldn't select all PvE and all unsplit skills). Now it has four allowed values: Default, PvE, PvP and WvW, allowing to search for [[Is for game mode::Default||PvE]].

Might be the best to burn this template and rewrite it completely. --Tolkyria (talk) 10:36, 22 April 2020 (UTC)

LOL that behavior wasn't documented so I thought it was a bug that the property wasn't set. I think I made that change so Template: Trait skill table would show the split. --BuffsEverywhere (talk) 12:36, 22 April 2020 (UTC)

It was at least partially a bug: | current | #default = = {{#subobject:[..]}}, this double "= ="; not sure what the initial intended behaviour should be, namely: {{#if:{{{status|}}}|[..]}}, which in general is never set (hence it was used as the workaround I described above). But as I already mentioned, now with [[Is for game mode::Default||PvE]] it's fine to set the status also for split skill subobjects in general.

My first recharge table redesign tests looks quite promising, introducing a lookahead game mode suffix with the following rules:

1. split skill with the same recharge: display the skill only once, append the previous game mode suffix with the current game mode.
2. game mode suffix containing all three game modes: clear the suffix, no need to have (PvE, PvP, WvW) as suffix

--Tolkyria (talk) 13:11, 22 April 2020 (UTC)

Redesigned the template with the two rules I mentioned above. --Tolkyria (talk) 13:17, 1 May 2020 (UTC)

Thank you! --BuffsEverywhere (talk) 03:59, 13 May 2020 (UTC)

Skills with charges

This template incorrectly states that it reduces the recharge of skills that have charges. Specifically, the recharge between casts, not the count recharge. For example, on Spiteful Talisman, it shows Soul Grasp recharge as "3 → 2.4" which is incorrect. The trait (and I think all similar traits) only reduces count recharge. --BuffsEverywhere (talk) 16:21, 15 May 2020 (UTC)

The parameter "type = count recharge" is currently used on the following pages:

• 1 Ambidexterity
• 1 Axe Mastery
• 1 Brawler's Tenacity
• 1 Crack Shot
• 1 Elemental Surge
• 0 Eternal Armory
• 0 Mirrored Axes
• 1 Peak Performance
• 0 Spiteful Talisman
• 1 Vigorous Shouts
• 1 Weighty Terms

where the checkmark in front states:

• 1 green = this trait reduces the recharge and the count recharge
• 0 red = this trait does not reduce the recharge, it only reduces the count recharge
• 0 gray = not sure what this trait does due to a recharge of 0.25 seconds.

--Tolkyria (talk) 18:20, 15 May 2020 (UTC)

I have added the "hide count recharge skills" parameter, see here. --Tolkyria (talk) 18:38, 15 May 2020 (UTC)

Thank you. And also thanks for checking the other traits as well. --BuffsEverywhere (talk) 20:39, 15 May 2020 (UTC)

Right-Hand Strength

Anet had to be inconsistent again and made Right-Hand Strength only reduce recharge in the main hand. This template needs a parameter to ignore specific skills. --BuffsEverywhere (talk) 18:00, 19 August 2021 (UTC)

Added the parameter "weapon slot", usual number property SMW-syntax. --Tolkyria (talk) 14:06, 24 August 2021 (UTC)

Recharge table for Elixirs incomplete

The recharge table both on the page for HGH as well as this page is missing cooldown reductions for skills hidden inside Kits, namely Acid Bomb, Super Elixir and Elixir Shell that are correctly tagged as Elixirs. I tried to add this by additionally querying for Engineering Kits but without success. Endaris (talk) 23:40, 7 March 2022 (UTC)

The query was only asking for bundles equal to unnamed parameter 1, i.e. [[Has skill context::Bundle]] [[Is for bundle::{{{1|}}}]]. But we don't have a "Elixir" bundle, what we actually want are bundle skills that have the skill type "Elixir". I added the additional query [[Has skill context::Bundle]] [[Has skill type::{{{1|}}}]] which grabs your wanted skills. However, this solution requires that the two listed queries do not yield results both at the same time, as it would break the rowspan. So far I can't think of any but it's kinda late for me already. I might want to add some unique id to the rowspan nevertheless. --Tolkyria (talk) 00:38, 8 March 2022 (UTC)