User talk:Tolkyria

From Guild Wars 2 Wiki
Jump to navigationJump to search

Skill list templates on Swiftness page[edit]

Hey, someone brought to my attention that you replaced the content of the list of skills that grant swiftness with a templated version and removed my addition of skills granting swiftness from purchasable bundles specifically (see Special:Diff/1981184/1958941 ).

I think that this devalues the page information as now  Hare's Speed.png Hare's Speed is no longer listed and it is no longer transparent for the reader which of these skills come from purchasable bundles which is - in my opinion - the most interesting information for the reader: The case of someone going to a specific location to pick up a specific item to press that specific skill to get Swiftness for 10 seconds is very unlikely. On the other hand if you were playing a swiftness starved class or you wanted to get into dungeon records you would want to know what you could do to obtain an additional source of swiftness in the entirety PvE - preferably without manually seeking through an incomplete list by yourself.

I'm not really familiar with templates but maybe you could check if there's a solution to separate purchasable consumables from common skills and inject skills with misleading tooltips like  Hare's Speed.png Hare's Speed to maximize the information value of the page? Would be greatly appreciated since I spent a good while on checking through all purchasable consumables and would be sad if this information was lost to the reader.--Endaris (talk) 23:12, 7 January 2020 (UTC)

Imo the advantages of the automated lists (immune to being out of date due to future skill balance updates) makes it worth the minor inconvenience of not highlighting purchasable consumable skills.
I expect if we look hard enough, there is probably a page along the lines of "dungeon consumables" similar to that found on metabattle. If not, we should agree the title and create one. -Chieftain AlexUser Chieftain Alex sig.png 23:23, 7 January 2020 (UTC)
Sorry, my mistake. Of course, this is some legit information, that unfortunately cannot be extracted automatically by the template, due to the missing ingame skill fact "Swiftness".
Therefore, I have readded the purchasable bundle skills as a subsection of the Swiftness#Common skills that grant swiftness. See Special:Diff/1986777/1989169. --Tolkyria (talk) 23:31, 7 January 2020 (UTC)
Picking up Alex suggestion: the section "bundles by skill effect" could be nicely placed on Purchasable bundles. E.g.
== List of purchasable bundles by skill [[effect]] ==
=== [[Swiftness]] ===
* {{item icon|Hylek Poison Pot}} — sold by [[Hunter (merchant)|Hunter]], [[Astrozintli Forelands]]
* {{item icon|Medical Kit}} — sold by [[Ash Legion Spy (vendor)|Ash Legion Spy]], [[The Granite Front]] and [[Refugee Ejint]], [[Greyfern Expanses]]
* {{item icon|Medical Pack}} — sold by [[Lionguard Haral]], [[Tromigar Valley]]
* {{item icon|MedKit}} — sold by [[Seraph Provisioner]], [[Hidden Lake]]
* {{item icon|Pact Med Kit}} — sold by [[Crusader Apaaie]], [[Signal Peak]]
* {{item icon|Pot of Hylek Poison}} — sold by [[Urais (hylek)|Urais]], [[Hunting Banks]]
* {{item icon|Pot Of Hylek Poison}} — sold by [[Mictia]], [[Quetzal Bay]]
--Tolkyria (talk) 23:53, 7 January 2020 (UTC)
Thanks for getting back to this so quickly and you made it even better than before. Great! :-) --Endaris (talk) 22:10, 10 January 2020 (UTC)

Lesser Shield of Absorption on Stalwart Defender[edit]

Must've been a cache issue, since the trait skill wasn't listed when I made those edits. Or just me editing at three in the morning... - J.P.User J.P. sigicon.png 00:21, 3 May 2020 (UTC)

Neither of those... recapping the timeline:
  1. You edited Special:Diff/1979290/2050525 (Stalwart Defender) at May 2, 0:07.
  2. BuffsEverywhere edited Special:Diff/2050527/2050549 (Lesser Shield of Absorption) at May 2, 4:36, setting the type "Shield", which made it appear in the recharge table (The recharge table asks for weapons, bundles as well as utility and trait types).
So at the point of your edit, everything was working as you intended.
A quick remark to the "old" format you used: Due to an complete code redesign recently (see Template talk:Recharge table), I decided to get rid of the recharge icons, which have been used twice in each row (excessive). If you think we should still use them, feel free to leave a short request on the template talk page (I can restore them easily). --Tolkyria (talk) 08:27, 3 May 2020 (UTC)
Ah, I see! :D - J.P.User J.P. sigicon.png 14:58, 3 May 2020 (UTC)

Plated weapons page typo?[edit]

First, thank you for all you do on the wiki!!! But (unfortunately) I got all excited to see that Plated weapons are Exotic, per that wiki page, like the Machined weapons are, so I bought several, only to find that they're only Rare, which the individual weapon pages correctly shows. Yeah, too good to be true and a harsh reality check that my memory about such things is poor. I thought I'd ask you about the population of the template information, since is looks like you added it. Is this a typo, a scripting issue, am I missing something, or... other? Thanks. :-) Jesself (talk) 05:52, 21 May 2020 (UTC)

It was a mistake from whoever put it there, I fixed it now. Thanks for pointing out! DJemba (talk) 06:31, 21 May 2020 (UTC)
That's a pity, I'm sorry. It was a copy-paste mistake, which unfortunately happens here and there, especially when doing repeatative tasks. --Tolkyria (talk) 11:40, 21 May 2020 (UTC)
A small price to pay for all the good you do. :-) Jesself (talk) 15:03, 21 May 2020 (UTC)

Collapsible reward table[edit]

First of all, thanks for this, we finally won't have to scroll through hundreds of rewards in No Quarter. However, it is currently broken (I won't pretend i undestand where.), see No Quarter (achievements). DJemba (talk) 22:22, 31 May 2020 (UTC)

Can you go a little bit more into detail? Broken in which sense? For me it works fine, otherwise I wouldn't have added it. --Tolkyria (talk) 22:28, 31 May 2020 (UTC)
I didn't immediately see the expand button on the right, I saw the three dots for Cache Hunter and the redlink and wondered if something was broken... but that's just a not-yet-created page. Seems to be working alright to me. Maybe we should add a dotted line around the collapsed content to help draw the user to the show button? -Chieftain AlexUser Chieftain Alex sig.png 22:42, 31 May 2020 (UTC)
Although I also rewrote the objective part, the show button has always been on the right to expand the objectives (since January 2020). To be honest, I prefer to have a plain format without any borders, both for the tier rewards and the objectives. Furthermore, the table width should be fixed at this large size, otherwise the show/hide button would jump around when expanding/collapsing.
This reminds me of our discussion about right-aligned edit buttons. Here, basically the same holds: in a table it's totally fine to have the show/hide button on the right (that's where the wiki users would search). However, in the plain tier rewards/objectives a show/hide button directly next to the heading "Rewards"/"Objectives" would be more visible (same as the edit link). --Tolkyria (talk) 22:57, 31 May 2020 (UTC)
Now it's working, but before i didn't see the show/hide button and it was already expanded. DJemba (talk) 07:17, 1 June 2020 (UTC)
Okay, sounds like MediaWiki:CollapsibleTables.js wasn't loading. Simply refreshing the page (F5) should fix this. --Tolkyria (talk) 14:28, 1 June 2020 (UTC)
Done for now, I added the current format also to Template:Achievement box result format... overall I hope I won't have to touch this again.
Probably the easiest way to move the show/hide button to the left would be to define a padding-right. However, repeating myself, for me it's totally fine on the top right (okay, maybe I'm a little bit biased), having the button directly next to the "Rewards" header and above the tier reward item icons feel wierd. --Tolkyria (talk) 21:59, 1 June 2020 (UTC)

Prefix display[edit]

Concerning your Prefix display revert, fine by me, but if I did change it, it is because it had a use, feel free to implement it correctly. --Abbygaëlle (talk) 14:49, 2 June 2020 (GMT)

Taking a break, please refer to an according template talk page. --Tolkyria (talk) 12:58, 6 June 2020 (UTC)

Some Template Magic Required[edit]

Hi Tolkyria, could you please help create some armour gallery template variant for Raven Ceremonial armor and Bear Ceremonial armor so we don't have to reupload duplicate images for each armour weight? I'd really appreciate it. User Incarnazeus Signature.pngtalk 09:53, 19 June 2020 (UTC)

I suspect we want the following file naming scheme: File:<armor set name without suffix> <race> <gender> <view>.jpg, e.g. File:Raven Ceremonial armor asura female front.jpg.
Then we could use {{armor galleries|set = Raven Ceremonial armor}} and {{armor galleries|set = Bear Ceremonial armor}} on all three weight pages to suppress the default value of the parameter set, namely {{BASEPAGENAME}}, which includes the weight suffix. --Tolkyria (talk) 10:27, 19 June 2020 (UTC)
Yes, thank you! I didn't anticipate it was this easy. User Incarnazeus Signature.pngtalk 11:00, 19 June 2020 (UTC)
We might want to add it also to the three subtemplates of Template:Armor overview gallery to let them show up in the race & gender galleries, e.g. Asura female light armor. Although these armors (Raven, Bear and also Corsair) have only 4 or 5 out of 6 armor pieces, they have all non-hideable parts (feet, legs, chest) and hence I would consider these three as armor sets. Some might disagree that these are armor sets, but aren't those "sets" promoted as armor sets in the trailer videos? Finally, coming to my point: even there, we can simply omit the weight suffix in the file call. --Tolkyria (talk) 11:52, 19 June 2020 (UTC)
Done! Thanks again. User Incarnazeus Signature.pngtalk 12:16, 19 June 2020 (UTC)

Another request for your magic[edit]

Sorry for bothering so shortly after Inc. Template:Skill infobox displays commas in damage number after thousands. However, it does not do it with condition damage numbers (see Burning Tide). Could you please look at it? Thanks. DJemba (talk) 11:15, 19 June 2020 (UTC)

Indeed, in-game does use a 1000 separator for damaging conditions. Done, but you saw that already :-)
The Magic word formatnum is used to format numbers. --Tolkyria (talk) 11:52, 19 June 2020 (UTC)

Mastery point unlock totals[edit]

There's a fairly frequent bug where the subobjects get corrupted, the achievement pages need blanking, and the totals mess up. Every time they get corrupted, the total goes off by one or two. [[Widget:Table row count]] is a workaround to avoid having to care.

Did you realise this when you removed it? -Chieftain AlexUser Chieftain Alex sig.png 20:47, 1 July 2020 (UTC)

Hmm looking a bit closer you're using some newfangled #rowcount with your rewrite of Template:Mastery achievement table/Template:Mastery achievement table header, and I don't know how that will behave yet when it meets the subobject duplication. -Chieftain AlexUser Chieftain Alex sig.png 20:52, 1 July 2020 (UTC)
Yes, I was aware of it while removing it. I assumed that #rowcount would not run into such problems. However, today I tried to find the rowcount code (see here, probably I should have done this before editing it) and indeed it may cause the same problems since ultimately it seems to use the same code as format = count.
On the other hand smw 3.1.X is much more stable than 2.4.X and I don't think we had any smw cache bugs yet (except the wierd one where setting a page property to <page name>#<section name> sometimes failed).
Well, if you are not comfortable with the rowcount approach then we can of course revert it.
Another approach: What about using {{#var_final:{{{table-id|}}} rowcount}} in the header and {{increment|{{{table-id|}}} rowcount}} in the result format? Note that with Variables 2.5.1 most of the cache issues should be fixed and incrementing in a result format works properly.
--Tolkyria (talk) 11:17, 2 July 2020 (UTC)

Beep Boop[edit]

Hey, saw you tagged all your pages for deletion and quit the discord... are you okay? If/When you want to talk about it, feel free to reach out. I'd really hate to see you go. User Incarnazeus Signature.pngtalk 21:17, 9 November 2020 (UTC)

Seconding this... I hope you're okay. I'm around if/when you want to talk as well. If not here, I'm in-game, and can give you my email or other means of communication. Muirellthe Moon Geode.png 21:31, 9 November 2020 (UTC)
I'm fine, thanks. Okay, I admit that I these delete edits were a little bit excessive and that some of these pages might have public interest (reverted those). The rest is outdated and can be deleted now.
In general, I currently do not like the way the wiki is going (not going to state them in public as I only have partial solutions), hence I though one step back might help. --Tolkyria (talk) 18:53, 10 November 2020 (UTC)
Hey, I'm glad you're okay. :) I know how frustrating it is to not be on board with the way something is going, especially when it's an organization or entity that has really meant a lot to you. Sometimes partial solutions are what lead to whole ones! Whatever you decide though, I'm just glad nothing super serious for your mental health was happening. If there ever is, door is open. Muirellthe Moon Geode.png 18:59, 10 November 2020 (UTC)
Echoing Moon here. That aside, feel free to mail me your thoughts — perhaps writing them down might help and we can figure out what we could do so you feel more at ease here. User Incarnazeus Signature.pngtalk 19:08, 10 November 2020 (UTC)

Deletion requestes[edit]

I have left 3 pages tagged for deletion up as they are still in use. —Kvothe (talk) 15:00, 12 November 2020 (UTC)

Thanks, I guess the easiest option is to simply removed those requests. --Tolkyria (talk) 16:02, 12 November 2020 (UTC)
Good. —Kvothe (talk) 21:57, 12 November 2020 (UTC)

Let's Talk[edit]

Hey Tolkyria, I sense some unhappiness with the admins/community stemming from you (correct me if I'm wrong), so I'll repeat my previous offer: if you want to talk, feel free to reach out. I think we'd be able to help each other out (or at the very least you get to vent). This isn't some classic admin-coddling tactic, by the way. User Incarnazeus Signature.pngtalk 19:06, 14 December 2020 (UTC)

Mount unlock table[edit]

Hello, would it be possible to add a filter to Template:Mount unlock table that would show only a specific mount, i.e. if I wanted to put it on the Skyscale page, it would just show skyscale skins? ~Sime 16:13, 3 February 2021 (UTC)

Sure, basically instead of predefining all mounts on top in the template:
<!-- Mounts -->
{{#vardefine: mounts | Raptor, Springer, Skimmer, Jackal, Griffon, Roller Beetle, Warclaw, Skyscale}}
we can instead introduce the parameter "mounts" (and take all mounts as default value if the parameter isn't set):
<!-- Mounts -->
{{#vardefine: mounts | {{{mounts|Raptor, Springer, Skimmer, Jackal, Griffon, Roller Beetle, Warclaw, Skyscale}}} }}
On the other hand, if you just want a plain list without all the filter table stuff (quite big for only one mount), we can also go with an unordered bullet list:
{{Account unlocks list|mounts|query=[[Category:Raptor skins]]|columns=2}}
{{Account unlocks list|mounts|query=[[Category:Skyscale skins]]}}
--Tolkyria (talk) 17:25, 3 February 2021 (UTC)
That second variant for the plain list without the table is great, thank you very much! ~Sime 17:31, 3 February 2021 (UTC)

Property groups[edit]

Adding the dividers makes Special:Browse a bit less annoying to look at. Thanks! -Chieftain AlexUser Chieftain Alex sig.png 21:12, 17 March 2021 (UTC)

To make e.g. Browse:Meteor Shower readable again. Unfortunately, there are two stuck properties: Has skill activation type and Modification date at the top, although they have been "correctly" categorised. For the Category we might need some smw/scheme stuff, not sure about this yet (or if we actually want to classify it). --Tolkyria (talk) 21:31, 17 March 2021 (UTC)

Outfit sorting[edit]

Hello, I have again another request (yes I have no clue how to do this myself). Would it be, please, possible to add groupings to outfit acquisition (Gem Store/Black Lion Chest + statuette/Trading Post/Festival vendor), similar to Mount#Mount skins? There are not that many outfits available outside the Gem Store, but I still think this is a better solution than just a note at the bottom of the page. Thank you. EDIT: If it indeed would be possible, it is entirely fine if you just set up the base and I can add the individual outfits there myself. ~Sime 18:18, 25 March 2021 (UTC)

The mount acquisitions are pretty straight forward. The gem store, license and pack filters are added automatically, only the filter buttons are defined manually. On the other hand, the outfits are more complicated, e.g. Cook's Outfit is contained in a container that is sold by the gem store, the overall varity of possible containers makes it harder to select the wanted ones. Last but not least the mounts distribute themselfs into the eight mount types (providing a nice split to avoid one long list) while there's only one outfit category; also I still prefer the unordered list which looks better than a table (required for filtering, we would have to fake an unordered list). But okay, while writing this, it should be doable overall. I'll look into it tomorrow. --Tolkyria (talk) 19:38, 25 March 2021 (UTC)
Added a first try on my sandbox. To be honest, it doesn't really convince me so far. I feel even with filters it's too hard to keep the overview. What do you think? --Tolkyria (talk) 21:28, 26 March 2021 (UTC)
I do not think it looks bad and I actually quite like it. Obviously there's lots of overlap (statuette vs gem store), and some outfits are labelled as "Not Gem Store" while they should be in Black Lion Chest (because the box they are in comes from the chest), but I think that could be fixed? These outfits are: Starborn, Fallen Balthazar, Ebon Vanguard. But yeah I like what you've done! ~Sime 21:39, 26 March 2021 (UTC)
I want to let you know that with Alex we moved the widget from the sandbox to the mainspace . Thank you for your work! ~Sime 19:53, 8 May 2021 (UTC)
Sorry, I never managed to finish this one; I'm glad that you ultimately got it. --Tolkyria (talk) 17:35, 16 May 2021 (UTC)

Related skills[edit]

I reordered the list because of a few reasons. It's more jumping around to go from elite skill to profession skill than it is to go from profession skill to weapon skill. And going by bar order, first should be profession skills because they are above weapon skills. And gameplay-wise, I think profession skills have more importance/relevance than any other skill. Bundle skills aren't used as much as other skills so I moved them down the list. --BuffsEverywhere (talk) 17:23, 7 June 2021 (UTC)

I wanted to point out that performing one partial edit is in my opinion not enough to change an order that is used accross the whole wiki. For example, the following pages/templates come into my mind:
  1. Your edit affected only trait pages, but not effect pages.
  2. The page Skill bar has the section order:
    1. Weapon slot skills: including weapon, bundle and transform skills
    2. Slot skills: healing, utility, elite skills
    3. Profession mechanic skills
  3. The property Has skill context sort order has the order:
    1. Weapon
    2. Bundle
    3. Transform
    4. Healing
    5. Utility
    6. Elite
    7. Profession mechanic
    8. Pet
    9. Downed
    10. Drowning
    11. Trait
    12. default
  4. Weapon/bundle/transform skills share a table on chain, channeled skill, sequence skill as those are the skills with a skill slot number (1-5) and hence are using the same template. Furthermore, the section order is again: 1. weapon/bundle/transform 2.healing/utility/elite 3. profession mechanic skills
  5. The template Template:Skill list recommends the order (and hence is still used in this particular order on several pages):
{{Skill list|Weapon}}
{{Skill list|Bundle}}
{{Skill list|Transform}}
{{Skill list|Healing}}
{{Skill list|Utility}}
{{Skill list|Elite}}
{{Skill list|Profession mechanic}}
{{Skill list|Pet}}
{{Skill list|Downed}}
{{Skill list|Drowning}}
{{Skill list|Trait}}
Not sure if any other navs or pages that are using this particular order.
It's kinda hard to argue about the importance of different skill contexts, as probably everyone has a different opinion. But keeping the skill bar slots together (e.g. weapon/bundle/transform even though the bundle/transform skills might me less important than other skill contexts), seems to be the best solution for me. It simplifies the template usage, e.g. weapon skill table (row), slot skill table (row), Profession mechanic skill table (row). Furthermore, since there aren't many bundle and transform skills, the sections are relatively short and aren't that disturbing.
Arguing about profession mechanic skills < weapon skills, I would say that weapon skills (including auto-attack skills; in general with lower cooldowns that are used more frequently) should always be listed first. So unfortunately, I'm not really fond of your proposed sort order: profession mechanic < weapon < healing < utility < elite < bundle < transform < pet < downed < drowning. You are also splitting profession mechanic and pet skills (especially beast skills - F2 - which are listed in the profession mechanic bar but are performed by the pet), keeping them together in front of the weapon skills feels kinda awkward.
P.S. Okay, this got a bit lenghtly, probably confusioning, but I'm somehow trying to explain why the current should make sense. And sure, the examples above are kinda biased, as most of them are a result of my edits. --Tolkyria (talk) 18:27, 7 June 2021 (UTC)
Oh yeah, I hadn't realized there were so many templates that use that ordering! Now I think it's not so worth it to move it around. I can see your reasoning for the order and I'm okay with it.
Also, somewhat unrelated, I was looking at Aegis#Profession mechanic skills that grant aegis and I saw that Tome of Courage wasn't listed even though its passive & active grants aegis. --BuffsEverywhere (talk) 06:25, 8 June 2021 (UTC)
For boons and conditions the query has the restriction [[Has fact number::>>0]] (read as greater than 0, while >0 stands for greater equal than 0), in order to avoid skills that only list boons/conditions as additional tooltip information but does not apply them. E.g. the three movement-impairing conditions from Rampage or stability and swiftness from Object in Motion (trait although).
However, for the combination skills and boons (not for any other combination of skill/trait and boon/condition) we could argue that currently this restriction doesn't make sense, as the only skills having boons with 0 seconds durations are Heat Sync and your mentioned Tome of Courage, which could be actually seen as boon applications. On the other hand, if they add a 0 duration boon as pure tooltip information (but not application) in the future...
{{#ask: [[Has fact type::Boon]][[Has fact number::0]][[Is for skill.Has availability::Current]]
| ?Is for skill.Has context
| ?Has fact
| ?Has game description
| sort = Is for skill.Has profession sort order, Is for skill.Has specialization sort order, Is for skill.Has page name
In the meanwhile, you can always add number=>0 to the template in order to include all durations. --Tolkyria (talk) 08:09, 8 June 2021 (UTC)
Edit: Oh wait, it actually grants 20 seconds aegis on use but doesn't list it. Then one can use also the missing facts parameter instead to show it the list. --Tolkyria (talk) 08:51, 8 June 2021 (UTC)

Re: Superspeed page revert[edit] - Whoops, I didn't mean to make any of the changes you reverted, not sure what happened there! Thanks for the fix! - Marcustyphoon (talk) 07:45, 14 June 2021 (UTC)

Don't worry, it's a normal wiki procedure. The only problem that can appear here it that the reverter doesn't provide enough information why they performed the revert.
I somehow understand the reason behind your edit, we are listing the maximum duration three times which may sound like an overkill (see: r/Guildwars2: What a descriptive wiki).
However, I think each occurence is there for good reason
  1. Description: Well, nothing we can do here, we have to copy the in-game text. Still odd though that they list the duration in the effect description, that's new.
  2. Infobox: I added this parameter recently, see this edit, as a result of the May 11, 2021 game update introducing a new maximum duration for boons and conditions. We can discuss if we really need it though.
  3. Intro text: It's always nice to have some basic facts written out in full detail.
P.S. There are the special pages [[Special:PermanentLink/<id>|<display name>]] and [[Special:Diff/<old id>/<new id>|<display name>]] if you want to refer to older version of a wiki page. --Tolkyria (talk) 08:02, 14 June 2021 (UTC)
Not quite what I mean! The only intended change in my edit was re-adding the "only the highest increase in movement speed will be applied" phrase, so the other reverts must have been from me hitting the wrong button :D Learned my lesson - from now on I'll check "show changes" as well as "show preview" before saving edits! -- Marcustyphoon (talk) 08:07, 14 June 2021 (UTC)
Oh okay, seems like I was interpreting too much into your edit. Indeed, these two editing buttons helps a lot. Still sometimes I'm 100% sure that everything is correct and I don't need to check anyways... guess what, there's a mistake and I need to edit again. --Tolkyria (talk) 08:14, 14 June 2021 (UTC)

Legendary Armory unlock template[edit]

Hi. I just wanted to let you know that the template that you made for the lore of Legendary Armory unlocks is very pretty. Kudos! --Warming Hearth (talk) 16:46, 15 July 2021 (UTC)

Thanks, glad you like it! --Tolkyria (talk) 17:03, 15 July 2021 (UTC)

Duplicate file ids[edit]

Not sure where to put this exactly, community portal feels to official for this. Currently, we are documenting more than 11000 file ids, thus we can start using them. For example now we can track possible duplicates by file id (note that also the file id could be wrong) and not only by Special:ListDuplicatedFiles.

For those who are interested:

--Tolkyria (talk) 13:11, 27 July 2021 (UTC)

Control effect / Interrupt[edit]

Special:Diff/2300994/2301021 - The reason I added control effects, is to get the trait to show up in the related traits for skills such as Head Shot. Interrupt traits can only be triggered by control effects, so I think they can be considered improving the control effect (if it lands while the target is casting). --BuffsEverywhere (talk) 08:54, 4 August 2021 (UTC)

The keyword "improves control effect" stands for traits that activate any bonus on disable, i.e. on casting an control effect. Sure, as you said, interrupt can only be triggered by disabling a foe but it also requires an active behaviour of the foes that can't be influenced by the control effect caster. So I wouldn't mix up those two different terms and keep traits that improves interrupt clearly split from traits that improves disabling. See also Control effect#Related traits and Interrupt#Related traits that for me are totally fine in their current state, combining them in one list just will just clutter and decrease readability/value of the pages in my opinion.
So, to achieve your goal, namely to obtain the applying-control-effect-skills for "improves interrupt" traits and ultimately show them in the related traits section on skill pages, I would suggest to go one level deeper and modifiy the trait infobox such that "improves interrupt" traits will also query for control effect skills. This avoids any confusion between disable foes (aka Control effect) and interrupt foes while providing the traits in the related trait sections.
Conclusion: In my understanding the keywords help to get the related improved skills but not at all cost, they should still be technically correct. If they aren't, I suggest then either set the improved skills directly or try to modify the keyword query in the infobox. --Tolkyria (talk) 09:39, 4 August 2021 (UTC)
"improves property = Interrupt" now queries for control effect skills in the trait infobox and marks them as improved skills. --Tolkyria (talk) 07:59, 5 August 2021 (UTC)
Thank you! --BuffsEverywhere (talk) 08:21, 5 August 2021 (UTC)


Hi. Would it be possible to get a template similar to Achievement categories table for achievements at the main page but showing only hidden achievements ? With every new update we are getting more and more achievements. Looking over every category to find all the hidden achievements takes a lot of time. Having a template that would automaticly take them from those achievement pages would help a lot. Thank you for your time and the answer --DiegoDeLaHouska (talk) 21:22, 9 October 2021 (UTC)

Are you looking for List of hidden achievements? --BuffsEverywhere (talk) 00:55, 10 October 2021 (UTC)
BuffsEverywhere, Diego edited this page before even you did, so he should be aware of it. Furthermore, his idea was to exploit the already defined sort orders that are for example used on Achievement categories table to get the full list automatically, rather than specifying each subsection per hand.
Diego, yes, since we already have all the required stuff set in the silent infoboxes, it should be theoretically possible. The only practical problem is that SMW has some serious issues when trying to sort two different objects at the same time, here the achievement category pages itself and the achievement subobjects.
{{#ask: [[Is hidden achievement::Y]]
| ?Has canonical name
| ?Has achievement category
| ?Has achievement category.Has achievement subgroup
| ?Has achievement category.Has achievement group
| ?Has achievement category.Has achievement group sort order 
| ?Has achievement category.Has achievement category sort order
| ?Has achievement category.Has achievement group sort order 
| ?Has achievement category.Has achievement category sort order
| sort=Has achievement category.Has achievement group sort order,Has achievement category.Has achievement category sort order<! -- ADD THE TERM: ,Has canonical name AND SEE HOW IT MESSES UP THE SEARCH -->
| limit = 500
So (without any further edit) it would be only possible at the cost of being able to sort the achievements alphabetically, which is a huge disadvantage especially for large list like All or Nothing achievements or collection lists. --Tolkyria (talk) 08:47, 11 October 2021 (UTC)
Yeah I only checked the edit history after I posted my comment. Anyway, I think my edits have automated most of it; the only things that would need to be added are new achievement groups or subsections to the story journal or maps. And I very much like the current layout instead of a single long list or table. SMW's sorting behavior is very unfortunate though. --BuffsEverywhere (talk) 10:11, 11 October 2021 (UTC)
Just outline 1. Has achievement category.Has achievement group, 2. Has achievement category.Has achievement subgroup (if set) and 3. Has achievement category and we would get the identical format. The currently used two arraymaps, the query for the achievement categories and then finally the query in the template for the hidden achievements based on these achievement categories is kinda complicated (so brain twisting), the outline let the already defined sort properites do the job with one query in total and three (actually six due to white space requirements) more lines in the result format. Just need to fix the alphabetical achievement order. See here for the code. --Tolkyria (talk) 11:18, 11 October 2021 (UTC)
Dont really know the best way to do it but whatever works for automation is fine by me. Another page that we dont need to take care of with every update is a job well done in my eyes . Thank you <3 --DiegoDeLaHouska (talk) 17:44, 11 October 2021 (UTC)
Nice work with the outline code. I think we need to split it into 2 queries to get the alphabetical sorting to work at the moment; one query to sort by the categories and the other to sort by name. I've modified the code to work with the existing templates to do this, see here. The duplicate headings under festivals looks a bit ugly though. --BuffsEverywhere (talk) 18:20, 11 October 2021 (UTC)
Looks good, that's one way to ensure alphabetically sorted achievements. The other would be to introduce the self-referencing property Has page name such that we can stack property chain levels to get the same sort property chain length of the others:
  • Has achievement category.Has achievement group sort order, Has achievement category.Has achievement category sort order, Has page name.Has canonical name
We are kinda unlucky with the duplicate festival heading, it's the only one and it happens immediately at the top. That's the price of the automatization, we can't influence the particular case. --Tolkyria (talk) 19:27, 11 October 2021 (UTC)
I added the property Has page name to the achievement subobjects so now they can be sorted by name and the hidden achievements list is fully automated. --BuffsEverywhere (talk) 04:43, 18 October 2021 (UTC)
You can now also apply it to Achievement list to sort 1. by availability, 2. by achievment category (i.e. by group and/or subgroup), 3. by canonical name; which you tried to edit recently and didn't work for the same reason. --Tolkyria (talk) 08:06, 18 October 2021 (UTC)

Move to game update sub page[edit]

Game updates/2021-11-30/End of Dragons Elite Specialization Updates breaks the Main page dpl request. Any idea how to fix it? —Kvothe (talk) 21:09, 30 November 2021 (UTC)

Add | nottitlematch = Game updates/2%/% to exclude sub-sub-pages. --Tolkyria (talk) 21:13, 30 November 2021 (UTC)
Thank you for the quick help. —Kvothe (talk) 21:21, 30 November 2021 (UTC)


Hello Tolkyria, it has been brought to my attention that the tone of many of your replies is bordering between passive aggressive and just plain hostile.

Can you please make every effort to read your replies before posting, as whilst I am sure you have the best intentions, please consider the basic question "How does my reply make me appear to other editors?". -Chieftain AlexUser Chieftain Alex sig.png 15:08, 6 July 2022 (UTC)

Noted, however I'm totally aware how my replys sound in these cases, that in my opinion are always related to the edit itself and never against the person. In these situations I might be mercyless by pointing out problems that I think decrease the wiki user experience.
Warning understood and I also noticed it myself, therefore I'll draw the consequences and reduce my edits to a minimum as I'm either 100% or 0% in. --Tolkyria (talk) 21:05, 6 July 2022 (UTC)