Template talk:Achievement table row

property names

I improved a few of your property names (Has title -> Gives title) and changed Has description to use the existing Property:Has game description. (Hope you don't mind, I know you're not a native speaker, although you're really good.)

I wasn't sure what a couple of the properties mean, though: Has meta and Has counter. I think your intent is to link achievements to the meta achievement that they contribute to. I would think a single property would work for that, Counts for meta achievement. If you need a property to identify meta achievements, then it would either be a boolean Is meta achievement (values Y/N) or Has achievement type (values "normal"/"meta") and would be populated for all achievements. —Dr Ishmael 23:13, 19 July 2013 (UTC)

I don't mind; it is a conflict of logics "most of the properties I saw has 'Has ...' in it's name" and "properties should be named after their destination".

Has meta is intended to serve as a flag if this achievement does count towards meta (default value - empty value), does not count (no) or is meta itself (self). Since it's kinda ternary, I thought we can go away with just one property, however, I didn't think much about the name and will appreciate any ideas. Has counter currently has no use, but can be possibly used in achievement trackers, so that achievements-counters automatically increases when a corresponding achievements are set as completed. MalGalad 23:23, 19 July 2013 (UTC)

Should be Is part of meta achievement to match Is part of meta event--Relyk ~ talk < 19:23, 20 July 2013 (UTC)

Tiers

I used :: as a separator for desc./AP because some achievements has semicolon in it, e.g. Traders Met: 5, and comma as a separator for tiers because it doesn't seem like semantic properties like line-breaks. MalGalad 23:23, 19 July 2013 (UTC)

Double colon is completely confusing with semantic annotation--Relyk ~ talk < 19:25, 20 July 2013 (UTC)

Well... any ideas on another separator? :D MalGalad 19:29, 20 July 2013 (UTC)

- § $ % & are classical seperators. The paragraph is used seldom so the propability is high that is is in fact not a seperator used in any mediawiki extention. - Yandere 10:16, 21 July 2013 (UTC)

I just put in the § as delimiter, It shouldn't be used anywhere in mediawiki or in the text from arenanet. Works well on Bazarr and Hero archivement page. - Yandere 10:35, 21 July 2013 (UTC)

I'd prefer another separator, since paragraph mark is not so easy to type, or needed to be copypasted from somewhere (and this will not solve triangle marks on the Hero achivements). MalGalad 10:50, 21 July 2013 (UTC)

Sorry, I use a german keybord layout. The German layout types paragraph as shift and 3, so is very easy to type. (Says a lot about the Germans that they have a clearley law related character always at hand, doesn't it?)

Anyhow I just opened a qwerty layout and I am searching for a better replacement character. But finally I understand, why the paragraph is seldem used in programming, never thougth about this before. ^^ - Yandere 13:04, 21 July 2013 (UTC)

Well, you can use Alt+21 on Windows... I vote for &, it's used for separating arguments in URL's already. Question mark can possibly be used in tier description text, and percentage mark is almost as nice an ampersand, but looks out-of-context. MalGalad 13:10, 21 July 2013 (UTC)

A simple & or a % can be used in text so these delimiter are problematic. Therfore it should be a doubled character. I would use a double ampersand like this &&, this will never show up in a text, therfore is easy to parse. - Yandere 13:19, 21 July 2013 (UTC)

Just searched throw the achievements. I'd define possible characters as [\w\d :,-.()%'], but wiki also uses ? for some WvW achievements and {{|}} for Gold Hoarder. This means that we can use & and can not use ,. MalGalad 13:30, 21 July 2013 (UTC)

Why can't we use a semicolon (;), your example uses a colon--Relyk ~ talk < 13:34, 21 July 2013 (UTC)

My point was that an ampersand is nothing unusually to a normal text, so we might face on in the future. Comma and full stop are also common. So we probably should do something which isn't common in normal text like a repeated character (--). Semicolon doesn't work because it has a special meaning in the mediawiki parser language similar to the colon. - Yandere 13:39, 21 July 2013 (UTC)

It's not a special character for #explode and #arraymap, so I'm not following your reasoning.--Relyk ~ talk < 13:55, 21 July 2013 (UTC)

(Reset indent) Meanwhile, in reality: I replaced separators with & and ;. If we encounter ampersand in "normal text" - we will change it, but now it's overprecautioning (if such word exists). MalGalad 14:04, 21 July 2013 (UTC)

Why did you replace the comma with a semicolon? That was just fine...--Relyk ~ talk < 14:41, 21 July 2013 (UTC)

Comma is used in the tier descriptions, e.g. 20,000 Damage in One Hit, 2,000 Influence Earned or 200,000 Exp without Death. Of course, we can replace it with ,, but is it worth it? MalGalad 14:57, 21 July 2013 (UTC)

We can wrap the pre-text portion in formatnum, but that's not necessarily obvious and might be unwanted. If anything, using a new line for the delimiter like with poke's example would be more readable and intuitive.--Relyk ~ talk < 15:19, 21 July 2013 (UTC)

I guess, break-lines breaking the property is not a case if property's type is defined... That was the main reason for having other separator. Lets try. MalGalad 15:29, 21 July 2013 (UTC)

And now you can switch to using ; as the separator between tier description and AP, which will let me set up Property:Has tiers as a record property. —Dr Ishmael 15:53, 21 July 2013 (UTC)

Stop-stop-stop, this is getting out of control! What are all these properties for? It's ok in just one... MalGalad 16:24, 21 July 2013 (UTC)

Look at the Has tiers, there're tiers from all previous achievements of that category! A great bookah! MalGalad 16:29, 21 July 2013 (UTC)

I fixed all that. But damn me, I dug myself into a hole I've been in before: there's no way to sort record properties. F*$K! >.< I'll just revert everything..... —Dr Ishmael 16:43, 21 July 2013 (UTC)

Semicolon is still better than ampersand. —Dr Ishmael 17:11, 21 July 2013 (UTC)

Semicolon is ideal, we've been using semicolons as a standard replacement for commas in code for other templates.--Relyk ~ talk < 17:16, 21 July 2013 (UTC)

Added repeatable

Than I realized the 'tier count' property. What is the tier count? and why can it be infinite? does this does the same as repeatable? - Yandere 17:24, 20 July 2013 (UTC)

Tier count is how many tiers does achievement has - to fill in rowspan property of the table cell with description etc. If it is infinite - well, yes, I meant repeatable. Well, better to have your property, I'll clean up. MalGalad 17:27, 20 July 2013 (UTC)

Ah that makes sense, but isn't the tier count something that could be calculated automaticlly? - Yandere 17:32, 20 July 2013 (UTC)

Technically, it can be. Just a remnant of proof-of-concept templates, probably. Lets give it a try! MalGalad 17:53, 20 July 2013 (UTC)

flavor

I feel left out in having no idea what that means.--Relyk ~ talk < 19:19, 20 July 2013 (UTC)

On some achievements there's a text in italics below the description, kind of lore. I personally have no idea why it's called "flavor", but poke first included it. MalGalad 19:26, 20 July 2013 (UTC)

Ahh the new text, I think it matches the flavor text in items (which is in the API or something). I'd rather include it in the description like we do with items though.--Relyk ~ talk < 19:31, 20 July 2013 (UTC)

Hero archivments

Updated the Hero (achievements) page. I noticed two problems:

1. If the category has no meta archivments there should be some kind of header, which is usually covered by the meta archivments.
2. The other one is the strange yellow exclamtion mark which shows up in the story archivements.

Any ideas how to fix that. I will go off now, perhaps I have an idea later this evening. - Yandere 19:42, 20 July 2013 (UTC)

1. Currently being discussed (last 2 edits).

2. This yellow exclamation mark can be fixed by a) using some other separator instead of :: (discussed above), b) creating property name and give it [[Has type::text]], see Dr ishmael. MalGalad 19:55, 20 July 2013 (UTC)

Draft and suggestions

• User:Relyk/SMW/achievement table header
• User:Relyk/SMW/achievement table row

The header sets two properties: the canonical name of the achievement category and the icon. This replaces all the work done in the row template to get the name without the qualifier (Same exact approach as infobox). The icon is the achievement category icon, which will be used for the meta achievement icon. This moves a lot of code related to the achievement category to the page.

We have a page parameter that sets the Property:Has canonical name for the link to the article. This is only needed if the achievement has a qualifier, so we can check if a page exists for the name and link to that. We won't have a page for every achievement and its simply working backwards. Changing countsfor to parent as a better term for the umbrella achievement. We can probably assume that parent achievements and repeatable achievements will never count towards a meta achievement. We also display the parent achievement in brackets after the achievement, that should be fine compared to another line in the cell. There's also some code formatting. I also put all the icons before the achievement name. It keeps them group together and I think it looks just as good; we also might want a star mark for title. May decide to list the after the title, which will look weird if we still include the parent after.

The tier count and total can be calculated with #arraymap and don't need parameters. I changed the logic around to a more standard approach, concatenating a string to feed into the expr function was weird (sorry). We also need a suggestion parameter which looks to be for listing locations to start. We don't need the Has tier count property, that can be calculated. you also don't need the Has achievement category, you can pull that from the subobject, see {{recipe}}.--Relyk ~ talk < 17:14, 21 July 2013 (UTC)

A few things I would want to add. When a category has no meta archivement it would be nice when the 'achievement table header' could create a first row, when a parameter is set. May of the general archivements are missing a meta archivement and one of the archivements will get the first row ans therefor a special highlight without reason.

Where do I write down what the actual prerequisite for the archivement is?

Repeatable is also a bit strange the wiki dokuments a few archivents repeatable with 250 repeats for example. Ingame the archivement is listed a s infinite. What is true? It would make sense that there is a maximum on repeats. MAX_INTEGER immediately springs to mind. I am actually quite confused on this one. - Yandere 17:28, 21 July 2013 (UTC)

Ah just realized it is only the documentation which is a bit missleading on prerequisite. - Yandere 17:35, 21 July 2013 (UTC)

We don't need the meta achievement tracker like it does in the achievement panel. The current code for repeatable didn't make sense because you can repeat it as much as you want, I changed that text in the draft.--Relyk ~ talk < 17:36, 21 July 2013 (UTC)

That is not the problem I have. I think it is strange, that the first archivement is always highlighted. It is ok for meta archivements, but there are a few categories which do not have meta archivements. I don't want any tracker build in. O_o - Yandere 17:45, 21 July 2013 (UTC)

That's just how the CSS is set up I guess, a row would be useful to display the total points available anyways.--Relyk ~ talk < 17:56, 21 July 2013 (UTC)

You set two properties Is part of achievement and Is part of meta achievement with the same value {{{meta}}}. That seems redundant?

Also, I would really like it if we did not link the achievement name unless there is a page for it. —Dr Ishmael 18:17, 21 July 2013 (UTC)

There was a code with functionality to check if the page exists and then make a link, but I removed it since eventually all achievements will have pages with at least redirects.

Relyk, I'd ask you to add it all yourself, since it's mainspace and I'm afraid to break something before I understand new code. MalGalad 18:26, 21 July 2013 (UTC)

Linking to a redirect that points back to the same page is pointless and confusing, I meant only if an actual non-redirect article exists. —Dr Ishmael 18:32, 21 July 2013 (UTC)

And that's why I asked you if there's a way to detect redirect pages :D

So, we need to add a new flag, that shows if the achievements is trivial or not. MalGalad 18:35, 21 July 2013 (UTC)

The page parameter will be the flag.--Relyk ~ talk < 19:14, 21 July 2013 (UTC)

One for the meta achievement, one for any parent achievement i.e. Kites of Caledon contributing to Bazaar Ambassador meta achievement and Learn to Kite umbrella achievement. I think we need the achievement type and have a generic Is part of achievement property. If it's a meta achievement or repeatable and therefore doesn't contribute to a meta achievement, we can code that into it instead of an explicit parameter. We aren't going to display the meta achievement after every achievement in the category, but displaying a parent/umbrella achievement is desirable. We may still need the parameter for special cases? Repeatable may also be considered a type of achievement exclusive from meta, umbrella, or standard achievements.--Relyk ~ talk < 19:07, 21 July 2013 (UTC)

I modified the Relyk's header a bit I think it looks fine: User:Yandere/Template Sandbox

What do you think? - Yandere 23:18, 21 July 2013 (UTC)

I really want to overlay the category icon on the top left corner of the table, something like {{conjure nav}}--Relyk ~ talk < 02:53, 22 July 2013 (UTC)

I changed the thing you describe in your Sandbox. - Yandere 09:53, 22 July 2013 (UTC)

Draft includes changes up to now, I'd like to implement it.--Relyk ~ talk < 00:48, 24 July 2013 (UTC)

Well, feel free to edit and being bold, it's a mainspace template ;) But header is a bit too large imo, probably smth like that?

And also, I remember I saw somewhere in your sandboxes a template for achievement row, the one that had an expandable description/guidance/tips/whatsoever. I looked at all these huge tables, and thought - if we already have achievement name[+link] and AP, probably we can collapse all tiers and descriptions, and expand it on click on the [th]? MalGalad 00:56, 24 July 2013 (UTC)

We don't need hide the description portion, it's the tier list that will generate a huge amount of whitespace (and can be rather trivial).--Relyk ~ talk < 01:36, 24 July 2013 (UTC)

Ugh, looks not so good. MalGalad 01:54, 24 July 2013 (UTC)

Only need to collapse it if there are more than 5 tiers.--Relyk ~ talk < 03:25, 24 July 2013 (UTC)

Please go ahad I think most of your suggestion is an improvement. We can work out the kinks later. - Yandere 10:02, 25 July 2013 (UTC)

Oh yeah, I've made it! Please revise an example of template, that hides high tier count numbers. It works as intended (which I am truly wondered of, maybe I'm getting the wiki magic?), but, while the code can be optimized by guru of syntaxes, the obvious improvement is to prevent [hide]/[show] link from jumping from left to right on the header line of the expandable table nvm, that was obvious after the css inspector. MalGalad 22:42, 27 July 2013 (UTC)

Also, Property:Has achievement type does not respect whitespaces before the property's value... MalGalad 13:15, 28 July 2013 (UTC)

That happens with text properties. I just removed the whitespace between the = signs and the values. —Dr Ishmael 14:16, 28 July 2013 (UTC)

Thank you, was not sure where spaces aren't trimmed.

As no resistance appeared, I've implemented that tier spoiler thing; also, from Aquadrizzt feeding grow up a brand new! location parameter. You can set it manually or, if the achievement already has location set throw {{Location infobox}}, it pulls it and throws to the resulting table. This is mainly for JPs, but who knows? MalGalad 00:10, 29 July 2013 (UTC)

One tweak that is necessary is that repeatable should not also throw the "does not count towards meta" tag. I believe the only achievement so affected right now is Agent of Entropy, but the table row should accommodate this. Aqua (talk) 15:35, 29 July 2013 (UTC)

Meta icon

I used this icon as universal meta archivement icon:

I think it is fitting and has this sense to achievement to it. Of course I know that the ingame thing is something totally diffrent, so suggest a better one, if you think there is a better one. The category icon is redundant and not really readable when scalled to 18px. So any item that gets the point across and is readable on 18px. would do. - Yandere 21:29, 22 July 2013 (UTC)

reward/title icons

I don't find them redundant as they serve as quick reference. The actual listing for reward/title don't need icons.--Relyk ~ talk < 14:20, 24 July 2013 (UTC)

When I'm scanning the page, the icon with bolded "Reward" or "Title" on white background is a better quick reference for me than a stand-alone icon on blue background (the darker background lessens the visual impact of the icon). I'd think that would be even more applicable to people who aren't familiar with the icons. —Dr Ishmael 14:26, 24 July 2013 (UTC)

It's a very light blue. Nothing says "Look at me I do weird shit" like icons next to the name of the title. Moreover, the way the icons preface the bolded title/reward text look strange to me. If it looked better, I'd be more agreeable.--Relyk ~ talk < 14:42, 24 July 2013 (UTC)

They probably should be cropped. —Dr Ishmael 14:50, 24 July 2013 (UTC)

Location

So, location. In appears in Explorer, Bosses, Fashion and Jumping Puzzles categories. Should we keep it consistent with the in-game linkings, or provide our own info? The point is, in-game it frequently links to waypoint (which currently has no representation in the wiki, except for IDs). Until now, I replace waypoints with corresponding areas and leave PoIs as is. MalGalad 00:56, 29 July 2013 (UTC)

Technically, the game circles a WP or PoI and then says "somewhere near this." I wouldn't mind doing the region that the WP/PoI is in at that point, as that is both defined on the wiki and is actually a good descriptor of where the achievement might actually be. Aqua (talk) 14:57, 29 July 2013 (UTC)

The listed "Suggested Locations" is always a zone. When you click it, it does what Aqua says and indicates a specific PoI/WP within that zone. Why can't we just list the zone in the achievement table? Do we need to list the point as well? We already have detailed "walkthroughs" on how to obtain these achievements (except for Fashion), which are much more useful than a simple point name. —Dr Ishmael 15:04, 29 July 2013 (UTC)

OK, I changed locations so that they link to the areas (except for the Troll's End, which is hard to determine). MalGalad 17:10, 29 July 2013 (UTC)

But that's not what's shown in-game. The achievement details only list the zone, not the area, for suggested locations - e.g. Caledon Forest, not Morgan's Spiral, for the Morgan's Leap achievement. Annotating that Morgan's Leap has suggested locations of "Morgan's Spiral" is incorrect, because that is not what is suggested in-game. —Dr Ishmael 20:23, 29 July 2013 (UTC)

But if you want to provide link "as in game", it should point to closest waypoint or PoIs, with an alias of zone name, and I thought you said we already have walkthroughs for that. In other words, if we don't link to PoI or WP, we already break the conformity with the game client, so there's no point in keeping exact names. MalGalad 23:02, 29 July 2013 (UTC)

After thinking deeply into that problem, I realised that I accept only binary solutions, i.e. "we do exactly as in the game client" or "we don't do as in game client". But if we don't do as in the client, then why do we have to have these links at all? Oh, well, that put me on the knees.

So, what if have something like that:

Manor Magnate
Suggestion locations: Queensdale ()

Link to an area aliased as a zone, with a map link to the suggestion map mark. 23:18, 29 July 2013 (UTC)

Order matters

So in-game, we're provided two options for achievement ordering: alphabetical and completion. "Completion" is useless to determine achievement order unless you haven't begun progress on any achievements in that category while "alphabetical" ruins some intentional ordering (such as the fact that Master Crafter comes before the 8 crafting discipline achievements). I've noticed that for some achievement categories (notably Jumping Puzzles), even when I've done all jumping puzzles, the in-game order is kind of random and not particularly searchable. My thoughts are that we do as follows:

1. First achievement is the meta-achievement (if applicable)
2. All remaining achievements are grouped into related groups (i.e. Sanctum Sprint achievements are a group), attributed to related parents (Learn to Kite as the parent of the 7 kite achievements) and/or grouped from being prerequisites (i.e. Kiel: Direct Support is a prereq for Kiel: Advanced Support so they should be grouped together). Standalone achievements are left as they are.
3. From there we alphabetize by group (or by individual achievements, if possible; for example, Jumping Puzzles should be simply alphabetized IMO).

The game kind of does this with the newer achievement categories, but the older categories rarely follow this. Thoughts? Aqua (talk) 15:31, 29 July 2013 (UTC)

Suggested Locations is wrong

"Suggested Locations" is wrong for most of the achievements. In dungeons, fractals, explorer, jumping, and many other achievements, there is only one location. "Suggested" implies that there are others. What is wrong with the simpler phrase, "Locations" ? It is self-explanatory that weapon master achievements can be gained anywhere and that slayer achievements can be gained anywhere the relevant foes can be found. Thus "locations" by itself is rarely misleading while "suggested locations" is often incorrect. Otherwise, I'd "suggest" using two parameters: one for the locations and another for whether there is only one possible location versus whether there are too many to list.75.37.16.226 22:38, 4 August 2013 (UTC)

These are taken directly from in-game, both the term "Suggested Locations" and the locations themselves. Slayer achievements don't list any suggested locations in-game, so they shouldn't have any listed on the wiki, either. —Dr Ishmael 22:44, 4 August 2013 (UTC)

Repeatable achievements point cap

There are currently 5 infinite achievements that award AP in the game (Agent of Entropy, Hobby Dungeon Explorer and three in the new Activities categories) and they all seem to have a limit on the amount of points you can get from them. Would it be possible to add a parameter for this point cap, either saying the amount of points or repetitions that award points, and use it to calculate the total point count correctly? 10:37, 8 August 2013 (UTC)

Subobject naming scheme

{{#subobject:{{{page|{{{name}}}{{{index|}}}}}}

I can understand the logic of the index bit. (I think that I added that?..) But why is it using page instead of the name parameter, when it could be doing {{{page|}}}{{{name|}}}{{{index|}}}?

(The query that highlighted this to me was

{{#ask: [[Has canonical name::Maguuman Veteran Killer]] | ?Has canonical name | ?Has achievement page | ?Has achievement tiers | ?Has game description | link = none }}

which combined all the descriptions of items on a page where the | {{{page}}} = parameter has been set twice to the same target article. -Chieftain Alex 14:12, 16 March 2014 (UTC)

Offending edit -Chieftain Alex 14:25, 16 March 2014 (UTC)

Given the manner in which we use subobjects, the name is completely irrelevant and arbitrary anyway, so I see no reason not to include a unique sequence ID in all subobject names. You wouldn't even need the 'index' parameter. —Dr Ishmael 14:27, 16 March 2014 (UTC)

I did some more digging. looks like we had some events with the same canonical name. [1]

So yeah a number would work. If we wanted the subobjects to be browsable, then they should have the name as part of it, perhaps something like {{{name}}}{{#var:achievement_count}} -Chieftain Alex 14:32, 16 March 2014 (UTC)

Haven't found anything broken yet. -Chieftain Alex 14:54, 16 March 2014 (UTC)

found something that I broke. When I changed the category naming scheme, {{Achievement}}'s icon on pages with categories with qualifiers "..._(achievements)" are now missing. >.> not got time for investigative template fixing. -Chieftain Alex 17:47, 7 April 2014 (UTC)

easier to fix than I thought. Something else will be broken somewhere.. there is probably a reason for it previously targeting BASEPAGENAME :/ -Chieftain Alex 18:01, 7 April 2014 (UTC)

Property:Has achievement category is a page, you can't set it as the canonical name of the category Alex.--Relyk ~ talk < 03:29, 8 April 2014 (UTC)

Reward quantities

In the upcoming patch some achievements will give more than one of an item. I'm not sure how to put this info in, if it is possible. Maybe someone could implement a way to give quantities a place. Tyndel (talk) 22:35, 8 September 2014 (UTC)

Added a quantity parameter that will do so if the quantity is greater than 1.--Relyk ~ talk < 22:41, 8 September 2014 (UTC)

That'll do. Thanks! Tyndel (talk) 22:45, 8 September 2014 (UTC)

icon override

Some achievements don't use the same icon as the category. e.g. Daily League Participator—Recruit of Year of the Ascension Part I uses File:Daily PvP Achievement.png. --BryghtShadow (talk) 04:47, 3 December 2015 (UTC)

Are there any other categories besides that? Otherwise I wouldn't bother.--Relyk ~ talk < 05:57, 3 December 2015 (UTC)

"The achievement icons are overrides for the achievement group icon, which in turn are overrides for the achievement category icon." forum/community/api/New-endpoints-achievements

Daily Fractal Adept, Journeyman, and Master each use a different one compared to Daily Fractal. Daily WvW ___ and Daily PvP ___ uses a different icon to Daily. Daily League Participator—Recruit, Veteran, Elite and Champion in the new Year of the Ascension. --BryghtShadow (talk) 07:41, 3 December 2015 (UTC)

I've made the updates necessary. Specify the icon in achievement table row using the icon parameter. We're now storing the icon in the subobject, and it shows that result when you use {{Achievement box}} or {{Achievement list}}. -Chieftain Alex 15:37, 3 December 2015 (UTC)

Suggestion: Adding a semantic property to track mastery point

Rather than having to go through each achievement page, I would like to have a way to query all achievements that give Central Tyria and Maguuma masteries. | Has mastery region = {{mastery|}}}? --BryghtShadow (talk) 17:29, 8 December 2015 (UTC)

Sounds like a good idea. All achievements only provide 1 point right? (otherwise I'd suggest using Record type).

I'd suggest "Property:Provides mastery point" of type text, but yours would be fine. -Chieftain Alex 18:17, 8 December 2015 (UTC)

Yes, so far it's 1 mastery point per relevant achievement. "Has mastery region" vs "Provides mastery point" (implied, for region), either is fine by me. As long as I can get the list of achievements that provide points for a region. --BryghtShadow (talk) 18:43, 8 December 2015 (UTC)

Flag to determine if the chapter has already been tallied

Hero achievements are a tricky bunch. Only the first achievement your account completes per PS chapter counts. Currently the template indiscriminately adds every mastery point. A flag would make it work for the overall list as well as custom lists that exclude a particular chapter. My attempt at grouping chapter achievements won't work if a particular name is not in the list.

Pseudo-code

ps1_names := ["Crime and Punishment", "For the Legion!", "Graduation Day", "Rising to the Challenge", "Waking from the Nightmare"]
ps1_flag  := False
foreach obj in achievements {
 if mastery {
   if not ps1_flag && obj.name in ["Crime and Punishment", "For the Legion!", "Graduation Day", "Rising to the Challenge", "Waking from the Nightmare"] {
    mastery_total := (mastery_total or 0) + 1
    ps1_flag := True
  }
 }
}

--BryghtShadow (talk) 22:37, 10 December 2015 (UTC)

Flag has now been implemented. So far, so good. Hero (achievements) is showing 11 for the mastery point count. --BryghtShadow (talk) 12:11, 11 December 2015 (UTC)

The correct way to implement would be to look up [[Property:Has personal story chapter number]] and create a flag for that chapter. Unfortunate for us, Alex implemented the properties before I did so the properties are in records with silly names.--Relyk ~ talk < 13:43, 11 December 2015 (UTC)

Uh... care to elaborate on the property flag, like where to do the lookup? --BryghtShadow (talk) 08:32, 12 December 2015 (UTC)

Well if you aren't familiar with properties and Semantic Wiki, you can look at Guild Wars 2 Wiki:Semantic MediaWiki. Ultimately, it's just:

{{#vardefine:chapter|{{#show:<person story instance>|?Has personal story number|+index=2|link=none}}}}
{{#varexists:personal_story_chapter{{#var:chapter}}|<-- Skip if exists -->|
  {{#vardefine:personal_story_chapter{{#var:chapter}}|true}}
  {{#vardefine:mastery_point_count|{{#expr:{{#var:mastery_point_count|0}}+1}}}}
}}

--Relyk ~ talk < 09:03, 12 December 2015 (UTC)

My attempt at implementing your suggestion To obtain <person story instance>, I took a substring of the description without brackets, quotations or link destination. Is there an easier way? --BryghtShadow (talk) 13:16, 12 December 2015 (UTC)

No, I lied. Trying to parse out the chapter isn't any better. I would add a chapter parameter that identifies the numbered chapter and create the flag variables that way. We can assume it refers to personal story. The point is that we don't hardcode the logic in a switch statement of names.--Relyk ~ talk < 13:52, 12 December 2015 (UTC)

Semantic mastery point revisited: Using mastery point reward id

I just discovered the API has an ID for all the mastery points. Rather than using the chapter parameter (which is very niche), we could instead specify the mastery point reward ID. So far the personal story racial and Order achievements are the ones that share IDs: API talk:2/achievements#2016-09-13. --BryghtShadow (talk) 09:16, 21 September 2016 (UTC)

Multiple rewards

This is primarily for festivals, but sometimes an achievement gives more than 1 reward. For example, currently all daily achievements give a bonus Homemade Lucky Envelope. The reward parameter only allows 1 reward, AFAIK. Is there any way we can allow multiple rewards? Even reward1, reward2, reward3, etc would be useful. The current bonus setup means it's relatively easy to just say "all dailies also give this", but other achievements may benefit from listing multiple rewards. Vahkris (talk) 17:02, 27 January 2016 (UTC)

Support "Hidden" flag

I'd like to support the flagging of "Hidden" achievements. --BryghtShadow (talk) 10:53, 21 September 2016 (UTC)

Tier rewards

With the recent game update, multiple tier rewards instead of one final rewards for achievements become more and more relevant, currently listed outside in one or another way, e.g.

1. Collection
2. Collection #2
3. Box

So, I would suggest to add an additional parameter tier rewards which takes the tiers, the items and the quantities, separated by ";" and new line, having the following format:

<tier 1>;<item 1>;<quantity1>
<tier2>;<item2>;<quantity2>
...

This parameter will be displayed at the same position where the reward parameter is displayed (white box on the left) and will be stored in Has tier rewards text with "~" instead of new line, comparable with Property:Has achievement tiers and can be easily created into a readable text with:

{{#arraymap: <tier rewards> |\n OR ~|@@@|Tier {{#explode: @@@|;|0}}: {{item icon|{{#explode: @@@|;|1}}}} {{plural: {{#explode: @@@|;|2}} ||({{#explode: @@@|;|2}})}}|<br>}}

Please note that the reward parameter lists the quantity before the item, but different quantitiesv here would not align the item icons. Hence, alternatively we could also use a table to align them, e.g.

{| 
{{#arraymap: <tier rewards> |\n OR ~|@@@|{{!}} Tier {{#explode: @@@|;|0}}: {{!!}} style="text-align:right" {{!}} {{#explode: @@@|;|2}} {{!!}} {{item icon|{{#explode: @@@|;|1}}}}|\n}}
|}

But still the tier numbers interfere with the quantity numbers visually, so quantities as suffixs seems to be better here.

The Has tier rewards text is a text property and doesn't really allow to track for rewarded items. Currently, in order to track achievement by rewards, the property Gives item is used (note that it is used in combination with Gives item quantity).
There are several possiblities to track for tier rewards:

1. Overload Gives item property and set it to all of the tier rewards. This will clash with Gives item quantity and hence should be avoided.
2. Create a new property Has tier reward and set it to all tier rewards. However, tracking for rewards will be complicated:
   • Either the user has to specify if he/she wants (a) rewards and ask for [[Gives item::<item>]] or (b) tier rewards and ask for [[Has tier reward::<item>]], which would be inconvenient for the wiki user and would sometimes require to template calls,
   • or internally we ask for [[Gives item::<item>]] OR [[Has tier reward::<item>]], which might become to expensive if further queries restrictions, e.g. category, etc.. are added.
3. Create a new property Has reward (or similar) and set both the reward and the tier reward (i.e. {{#explode: @@@|;|1}}) parameter to it. Then asking for an item returns all achievement that have gives the item either as final or as tier reward and the properties Gives item and Gives item quantity as well as Has tier reward text can be used without any restrictions and interferences; making it my favourite option. --Tolkyria (talk) 10:54, 24 November 2019 (UTC)

Added parameter tier rewards which sets the Property:Has achievement tier rewards.

However, asking for the individual tier items is not possible yet, see also above. --Tolkyria (talk) 19:39, 24 November 2019 (UTC)

Another option, combining 1. and 3. from above:

4. Using Gives item to track for rewarded items, either final reward or tier reward and move the functionality from the parameter reward (set to Gives item) and quantity (set to Gives item quantity) to Has achievement reward and Has achievement reward quantity respectively. --Tolkyria (talk) 14:06, 26 November 2019 (UTC)

More tier rewards incoming today, it would be nice to be able to ask for the tier reward items.

Option 1) would be quick and dirty, but would break if "reward" and "tier rewards" is used, which however might never be the case.

Option 4) would be cleaner but requires lots of page purging and property re-adjustments, something might get smw cache bugged in this process.

--Tolkyria (talk) 17:13, 17 December 2019 (UTC)

Implemented: Option 1). --Tolkyria (talk) 13:02, 6 January 2020 (UTC)

Fixing row colours

Currently, the tier row colours on the right are either white or blue ("even" or "odd" row), depending on the whole previous table. What about fixing the right tier row colours, starting with blue then alternate with white, to achieve a consistent layout? Example see below:

Header — currently used: dynamical tier row colours
Achievement subheader
Achievement text always white	blue
	white
Achievement subheader
Achievement text always white	white
	blue
	white
	blue
Additional heading
Achievement subheader
Achievement text always white	white
	blue
	white
Achievement subheader
Achievement text always white	white
Achievement subheader
Achievement text always white	white
	blue
Achievement subheader
Achievement text always white	blue
	white
Achievement subheader
Achievement text always white	white
Achievement subheader
Achievement text always white	white

Header — suggestion: fixed tier row colours
Achievement subheader
Achievement text always white	blue
	white
Achievement subheader
Achievement text always white	blue
	white
	blue
	white
Additional heading
Achievement subheader
Achievement text always white	blue
	white
	blue
Achievement subheader
Achievement text always white	blue
Achievement subheader
Achievement text always white	blue
	white
Achievement subheader
Achievement text always white	blue
	white
Achievement subheader
Achievement text always white	blue
Achievement subheader
Achievement text always white	blue

--Tolkyria (talk) 16:22, 20 December 2019 (UTC)

I support the change. I added single row achievements to show how they would look. —Kvothe (talk) 14:31, 21 December 2019 (UTC)

Added the "current" counterpart (last two rows) to Kvothe's added rows, they would be white. --Tolkyria (talk) 14:58, 21 December 2019 (UTC)

Implemented. --Tolkyria (talk) 13:02, 6 January 2020 (UTC)

Include Meta achievement "objectives"

For Example on Heart of Thorns: Act 1 I would like to include the possible contributing achievements you need specific 18 out of the total 19 (since "Sylvari Solidartiy" is excluded). I tried using the tier description with line breaks, but it looks ugly. Any thoughts? —Kvothe (talk) 14:31, 21 December 2019 (UTC)

What about an optional "objective" parameter listing the objectives in the left white box? But I fear that 18 tasks might look out of place, maybe it could work with a collapsible section. E.g.

Heart of Thorns: Act 1 (Story Journal)
Heart of Thorns Act I Mastery
Complete all 18 Heart of Thorns Act I achievements. Reward: Abaddon's Cowl Objectives: <objective1>             [Show] <!--show the rest--> <objective2> <objective3>	Completed 18 Achievements	10

--Tolkyria (talk) 14:58, 21 December 2019 (UTC)

Since we have tiered rewards now I would argue to display the objectives to the right of the rewards (below the description). —Kvothe (talk) 20:27, 21 December 2019 (UTC)

Implemented: parameter "objectives" taking as input plain wiki text (separated by new line) and looks similar to my suggestion above (on the right it would look out of place for empty rewards and co).

For an example, see Whisper in the Dark (achievements).

Remark: the "objectives" parameter is quite straight forward, e.g. see this edit from 2016 already using it in the correct way. --Tolkyria (talk) 13:02, 6 January 2020 (UTC)

Collection items

In the last days of working on achievements I came across another possible improvement: Including the collection items that contribute to the achievement similar to the "objectives". That would also make the collection pages easier to create in a more consistent fashion. —Kvothe (talk) 20:11, 26 December 2019 (UTC)

Same reason as above, this will get quite lengthy... not sure if this is wanted and/or if this should only be specified on the individual achievement page (as we currently do). Maybe someone else can comment on these topics that have some insight (e.g. historical insight, initial intention of this template and why the objectives and collection items haven't been added to this template yet). --Tolkyria (talk) 21:21, 26 December 2019 (UTC)

Implemented: parameter "collection" taking as input item pages and mirroring ingame design. Can be set to "y" to automatically gain the collection items in alphabetically order; however, if the displayed ingame order isn't alphabetically then it's better to specify it by hand. Note that if the item has a corresponding skin (e.g. weapons, armoe pieces), then the image links to the skin instead (because it's the skin that unlocks it).

Again, for an example, see Whisper in the Dark (achievements). --Tolkyria (talk) 13:02, 6 January 2020 (UTC)

Collection skins

I'm a little confused on how we're currently handling collections that contain skins. From what I've gathered by looking at existing examples we put an item instead of the skin there - for example in the collection Master of the Ancestral Forge which requires, among others, the Skin Restored Boreal Axe (skin):

| collection = Restored Boreal Axe
...

Also the item Restored Boreal Axe has the collection set in its infobox, not the skin. But the icon in the achievement box automatically links to the skin, not the item. Is that correct so far?

If it is, how are cases handled were a skin can be acquired through multiple items like most crafted equipment or something like Sunspear Cutlass (skin)? If the collection specifically asks for an item instead of the skin (PoF elite specialization collections for example), how can it be linked? If only the skin is required, which item gets put in? --Alcahata (talk) 16:02, 14 March 2020 (UTC)

The facts first. As soon as a collection piece (avoiding the term item here) has a skin, i.e. weapon or armor piece or back item, then it's always the skin that corresponds with it (at least I'm not aware of any case where this doesn't hold). E.g. see the API for the achievement The Cutting Edge (achievement): API (The Cutting Edge), you can see that for the equipment items the skin is used.

But yes, I have to admit that overall the collection topic is a little bit messy on the wiki. As far as I know there is no real guideline where to set the collection parameter, in the item infobox (Edit: armor infobox, weapon infobox), in the skin infobox or both. In the end it developed this way over all the years and would require an enormous amount of work to fix this.

While technically, as explained above it's always the skin that unlocks the achievement, it somehow makes sense to visually display the collection also on the equipment item page, to indicate that this item corresponds to a collection (to give the wiki user this information as soon as possible).

That's about the infobox collection parameter (I hope this is somehow understandable), but what about the achievement table row collection parameter?

As you can read a few topics above, I introduced the parameter collection this year to not only display the collection items on the individiual collection pages but also on the overview pages (together with the parameter objectives, which haven't been documented at all up to this point).

Edit: Please note that the infobox collection parameter and achievement collection parameter are two different concepts although they do the same. The problem is, that the items with a certain infobox collection parameter can be only obtained alphabetically sorted, which however is most of the time not the ingame order in the achievement tab. Hence to get the collection items in the correct order, I had to reintroduce the parameter again, allowing to add the items in the correct ingame order.

In order to be correct and match ingame, I went with the following: "If an item has a related skin, then it will link to the skin instead." (see documentation). This means:

1. If the specified collection parameter is a normal item (i.e. neither a weapon nor an armor nor a backpiece, hence it has no skin), then it simply displays the item.
2. If the specified collection parameter is an equipment item (i.e. a weapon, an armor or a backpiece, hence it has a skin), then it takes the skin (again, so far I'm not aware of any collection that uses the equipment item instead the skin).
3. If the specified collection parameter is a skin, then it takes the skin itself.

Hence, specifying the item is only a shortcut to get the skin, you can always specify the skin instead (i.e. what really unlocks the collection). However, if there is actually an achievement collection that uses the item and not the skin, then I can add a way to explicitly take the item instead.

I hope this gives at least some answers to your questions. --Tolkyria (talk) 18:31, 14 March 2020 (UTC)

A very helpful reply, thanks a lot! The important part to me was that it's fine to simply use the skin pages in the paramter for {{achievement table row}}.

And yes, usually collections require skins instead of the corresponding items. The only case I am aware of where the actual items are required instead of their skins are the named exotics in the mentioned PoF elite specialization collections.

To stay with your example of the collection for The Cutting Edge (API), you will notice that the 8th bit (index 7) is in fact an item:

{"type": "Item", "id": 82115},

which is Libeh's Truthteller(API) and not its skin. The skin is shared with the crafted Sunspear Cutlass, but obtaining that does not fulfill the requirement of the collection. --Alcahata (talk) 19:59, 14 March 2020 (UTC)

Ooops, wasn't aware of this one, although I checked the example api "carefully".

Adding ;item as suffix will link to the item instead of the skin now, see here.

Not sure if this is the best option, I can also remove the skin redirect, but then we would have to go through all collections and probably adjust the collection parameters. Would be some work but overall more consistent. --Tolkyria (talk) 20:34, 14 March 2020 (UTC)

The pages which are using the collection parameter could be found with copying {{parameter check|achievement table row|collection}} in a sandbox. --Tolkyria (talk) 20:38, 14 March 2020 (UTC)

I didn't know about that parameter check template. That seems very useful, thanks!

I agree that linking to the skins would be more consistent. I'm not sure how the wiki-bots work and if replacing pages in that collection parameter with their Has skin property (if present) is easy enough to do with them. I'm not convinced it's worth doing manually.

For now I've added the ;item suffix in the other places I know it's actually used (a grand total of 8 - on the same page) and it's working fine. Thanks for adding that! --Alcahata (talk) 23:23, 14 March 2020 (UTC)

Based on the discussion above I'm tempted to remove any shortcuts from the collection parameter, i.e. collection = y and the automatic skin redirect. However, I think that's not really a bot task, it's somehow too special.

My motivation of this intended change is that e.g. Basic Collections cannot use the collection parameter in all templates due to template timeout and simply being too many icons. Hence, adding the ";item" suffix makes the even code more expensive, for a grand total of 8 items!

Tools that help achieving this in general:

1. collection = y can be obtained via {{#ask: [[Is part of collection::<achievement>]]|format=array|limit=250|sep=<br>|default=''No results.''}} which then should be regexed, see 2).
2. Using the following regex, replacing (.*) with \{\{subst:#ifexist:\{\{subst:#show:\1\|\?Has skin#\}\}\|\{\{subst:#show:\1\|\?Has skin#\}\}\|\1\}\} in a better text editor (not more than 100 at once, due to #ifexist limits), replaces the item with the skin if there is one.

--Tolkyria (talk) 11:31, 15 March 2020 (UTC)

I adjusted all template calls as well as the template itself and removed any shortcut for the collection parameter. Now the output is exactly what the input is, no more redirecting to a skin: equipment item gives equipment item link, skin gives skin link.

Thanks for raising this discussion and granting me the possibility to reflect and hopefully implement a cleaner and more consistent way. --Tolkyria (talk) 20:29, 15 March 2020 (UTC)

While my original intention was just to understand the usage, I'm glad you found some improvements from that. By the way, the new implementation seems to be improved enough that the basic collections could be implemented without resorting to hiding collections. At least the preview generated from my script shows without timeout. Well with about 9s CPU time usage, but at least it shows. --Alcahata (talk) 23:08, 15 March 2020 (UTC)

Well the last three rows of the table with unlock items don't make it over the timeout limit. So close and yet so far. I guess when they add the next collection we would've had that problem anyway. I guess we'll have to pick collections to hide. --Alcahata (talk) 23:41, 15 March 2020 (UTC)

New parameter section

I would like to propose a new parameter "section" because the page parameter breaks on use of <page name>#<section>. —Kvothe (talk) 10:38, 8 June 2020 (UTC)

Wow, again, what's wrong with the page property? Not related to fixing this problem, but recapping the smw versions:

• Guild Wars 2 Wiki:Changelog (March 25, 2020): Upgraded Semantic MediaWiki from version 2.5.6 to version 3.1.5.
• smw:Semantic MediaWiki 3.1.6 (April 19, 2020): However, doesn't mention any page property related adjustments
• Special:Version (May/June ??, 2020): Semantic MediaWiki 3.1.6

I suspect that this might has something to do with the smw 3.1.6 as this bug doesn't occured before (at least I'm not aware of).

I'm not very fond of your suggestion about an additional parameter. What about internally splitting the the parameter page = <page name>#<section> into the page property: Has achievement page = <page name> and introduce the new text property Has achievment page section = <section>? This should fix the problem (if the actual problem is that we are to setting a page + section to a page property).--Tolkyria (talk) 11:35, 8 June 2020 (UTC)

Done as I described above, see also Property:Has achievement page section. --Tolkyria (talk) 12:32, 8 June 2020 (UTC)

The request was made in regards as far as I understood the problem. As you pointed out there is no need to introduce an extra parameter if this fixes the problem. —Kvothe (talk) 13:12, 8 June 2020 (UTC)

The current approach, using "#" as separator, will fail if someone starts using hmtl number entities in the page parameter, e.g.   (space). Then your suggestion would definitely be better. But so far we are fine. --Tolkyria (talk) 18:00, 8 June 2020 (UTC)

Parameter type

I wrote to User:Tolkyria first, here are some of our thoughts summarized.

1. As we now have repeatable meta achievements on Fractals of the Mists (achievements), I would like to request the addition of | type = repeatable meta which then places the "meta" and "repeatable" icons for the achievement.
2. We looked at type and its possible values:
   • The current type usage numbers are (See):
     • type = repeatable: 110
     • type = parent: 6
     • type = meta: 117
   • Proposals for icons and functionality:
     • standard (default, empty parameter) - no icon
     • meta - "meta" icon
     • repeatable - "repeatable" icon (personally I would remove the "no ingame" icon)
     • repeatable meta - new "meta" and "repeatable" icons
     • no meta contribution - new icon (might need a shorter name)
     • parent - remove confusing name now that we have objectives for the meta achievements, functionality replaced by "no meta contribution"
3. link=Achievement should be removed since the wiki popup just shows the "Achievement" page

—Kvothe (talk) 17:57, 16 September 2020 (UTC)

Checking the parent parameter on Secret of Southsun: it seems that type=parent together with parent=<achievement> is still used historically, nowadays such a construction probably would use "objectives" instead, and hence, for legacy reasons we can't really remove it.

Nevertheless, it should not be used to mark not meta contributing achievements. The question is if such a non-meta-contributing achievement differs from a standard achievement. Thus, wouldn't be a parameter called "no meta contribution" which can be set to "true" (default "false") be better instead of using the parameter "type" for this?

Are the "Fractal Fighter" achievements from the category Fractals of the Mists (achievements) repeatable? I can't see the infinity sign above the achievement icon. Instead I think they reset weekly, hence "repeatable meta" doesn't really fit... wouldn't be type = meta (with a note in the page intro that these reset weekly) enough? --Tolkyria (talk) 16:17, 21 September 2020 (UTC)

I just do not see the use of type = parent and parent = xyz. They just share a common objective (gathering samples or speaking with someone for "Secret of Southsun"). Ingame there is no association of parent/child in the sense, that is just something someone came up with on the wiki (and was also used for non meta contribution). As it stands nowadays we would have an achievement with objectives. We do not loose information if we remove type=parent and parent parameter as the achievements did not have the functionality ingame.

Fractal Fighter achievements reset weekly regardless of progress. Do we want to distinguish between resetting and repeatable achievements?

Maybe it would be appropriate to move type functinality and split to parameters | meta = y, | repeatable = y, | no meta contribution = y, | reset = daily/weekly.

Or keep type = standard/meta/repeatable and create parameters "no meta contribution" and "reset" separately.

Side note we should link "hidden icon" with List of hidden achievements. —Kvothe (talk) 17:05, 21 September 2020 (UTC)

Our "repeatable" achievements are marked ingame with "Infinite" e.g. Dungeon Frequenter, the API has flag "repeatable". An infinite icon for repeatable would probably be clearer and an undo/back icon for resetting achievements. —Kvothe (talk) 17:15, 21 September 2020 (UTC)

Personally I definitely think we should distinguish between repeatable achievements and achievements that reset on a timer. Allowing to set the flag for no meta contribution separately also sonds like a good idea. I don't really care about the concrete icons used, your suggestion sounds fine to me. --Alcahata (talk) 17:34, 21 September 2020 (UTC)

I would suggest to keep the parameter type:

1. to be consistent with the behaviour of the template code and with the property Has achievement type
2. to match the in-game achievement types

and we should keep the following values

• standard
• meta
• repeatable
• probably parent (I would personally keep it for legacy reasons or if you insist until the two categories Dragon Bash (2013 achievements) and Secret of Southsun have been adjusted)

Furthermore, based on your feedback, I would introduce the following values to the parameter type:

• daily (as it's behaviour is different from a "standard" achievement)
• daily meta (the "complete 3 achievements" achievement)
• weekly (e.g. the new achievement in Weekly Raids)
• weekly meta (e.g. the Fractal Fighter achievements)

The question is which icons should daily/weekly get? Note that the suffix "meta" adds the current meta icon. Setting an icon to type "daily" achievements, all of them on a page already containing the term "Daily" in page name sounds like an overkill (this change would then probably only affect the property Has achievement type). So I think only "weekly" should get an icon, which one?

Regarding the parameter no meta contribution, I think we can all agree that this one as

1. it isn't really an achievement type and
2. it would be nice to have (using the current "parent" icon). --Tolkyria (talk) 18:23, 21 September 2020 (UTC)

I removed parent from the two pages. For Dragon Bash 2013 it was more appropriate to use meta anyway.

• Daily - no icon
• weekly - maybe sort of
• repeatable - new infiniy tango icon
• meta, daily meta, weekly meta -
• no meta contribution -

—Kvothe (talk) 23:25, 21 September 2020 (UTC)

Done.

I didn't replace the repeatable icon for several reasons: Creating a new infinity tango icon is kinda hard and simply taking the in-game won't look good (that's why we are using tango icons). Furthermore, the yellow circle arrow fits nicely in a square. Last but not least, the wiki users already know the current icon, don't underestimate this. --Tolkyria (talk) 09:02, 22 September 2020 (UTC)

I have adjusted the meta achievement text to "This is a meta achievement." since there can be multiple meta achievements in one category.

For repeatable I added that they do not contribute to a meta achievement.

(Edits on both Achievement table row and Achievement box result format.)

Looking at the repeatable icon with the description text it is probably clear enough now, I know that there were questions before what the different icons mean. —Kvothe (talk) 11:11, 22 September 2020 (UTC)

Mastery point count

No Quarter (achievements) / Morale Breaker awards 2 mastery points in total through the use of service items but the table row shows 1 . This results in incorrect total counts in the header, on Achievement and is one of the reasons for incorrect total count on Mastery point unlocks (see Talk:Mastery point unlocks#Incorrect Icebrood Saga mastery point count for discussion on that as well...). Is there a way to set that number to show and count as 2? If not, there probably should be... 19:57, 5 November 2020 (UTC)

Morale Breaker actually gives 3. Two from services, and one from completion. The table row symbol means, as always, that it awards a mastery when completed - check API: [2]. The header and Achievement only document those awarded for completion, not service items. The incorrect number on Mastery Point unlocks has been fixed already, see the talk page there. DJemba (talk) 20:30, 5 November 2020 (UTC)

I was wrong, the times when the icon shows and when doesn't are weird. Tolkyria should have fixed this by now. DJemba (talk) 21:12, 5 November 2020 (UTC)

"The table row symbol means, as always, that it awards a mastery when completed" That was based on a hypothesis about how it worked prior to The Icebrood Saga. However, now we have 4 achievements which show us that symbol doesn't have to mean you get the mastery point at the end, but it can be at any tier.

I'm not 100% certain whether Morale Breaker gives 2 or 3 points, though, to be fair. Out of those 4 abnormal achievements I have completed one (Master of the Ancestral Forge) and I am absolutely certain it only awards 1 point, not 2, and I have also got the two points from Morale Breaker and the game no longer shows the mastery point icon for it, so I'd say it's fairly safe to assume it only gives two, unless the game is even more inconstent in its inconsistencies. Whatever the case, now the wiki shows 2 points for the achievement and it's reflected in the header and Achievement, so thanks a lot ^^. 23:38, 5 November 2020 (UTC)

Quick summary: I added the parameter "mastery quantity" to this template, defaulting to 1 if the parameter "mastery" is set, so right now only Moral Breaker needs it (setting "mastery quantity = 2"). --Tolkyria (talk) 23:51, 5 November 2020 (UTC)

Prerequisite

Prerequisites do not show on Mobilization Global Rewards. Any idea why? —Kvothe (talk) 00:01, 2 December 2020 (UTC)

Can you give an example wrapped in pre tags? Because right now I can't see why it shouldn't work. --Tolkyria (talk) 09:16, 2 December 2020 (UTC)

The prerequisite is not shown in the table. —Kvothe (talk) 11:48, 2 December 2020 (UTC)

Sorry, I'm afraid I can't help you here. For me everything looks like working as intended. --Tolkyria (talk) 17:51, 2 December 2020 (UTC)

Kvothe, I've circled in your exact screenshot where the prerequisites are showing. What's the issue? -Chieftain Alex 19:16, 2 December 2020 (UTC)

Turns out I'm just blind. —Kvothe (talk) 20:15, 2 December 2020 (UTC)

Objectives

I once added the achievement unlock check to the objectives list, but then reverted it pretty quickly. With the new EoD achievements it would nice if we could reconsider this edit and extend the API check to the last missing part. Theoretically we should be able to do this by strictly excluding the achievements where the API misbehaves and doesn't match with the wiki.

Known issues:

• For meta achievements the API doesn't list the bits and the in-game order is not sufficient enough, the account API might (or even in fact) has a different order.
• Explorer achievement are a mess in the API, they don't match the in-game order and also introduce empty strings that we obiviously can't handle at the wiki. So the best would to ignore those achievements.

Now the question is if everything else is behaving well and we actually should try it again? I searched through the achievement API for wierd parts like "" (basically only explorer achievements), however I haven't checked yet how the API values compare to Property:Has achievement objectives in full detail. --Tolkyria (talk) 16:45, 10 March 2022 (UTC)

Okay, now I know why I instantly reverted in 2020, the API is a total mess, I really thought it was better. See my sandbox. And I created objectives table row today, what a stupid move... --Tolkyria (talk) 18:58, 10 March 2022 (UTC)

Number of objectives

Is it possible to add the amount of objectives to the table row display? It would be relevant information especially for achievements with more objectives than nessesary for completion. E.g. changing Objectives: to e.g. <amount/number> Objectives:. If possible also make "1 Objective:" singular when that applies (not sure if we have that case currently). —Kvothe (talk) 12:54, 16 June 2022 (UTC)

We already count the objectives in order to switch between an expanded or a collapsed objectives list, so basically we just have to show the counter variable. In-game it always uses the plural "Objectives:", even for the only achievement with one objective that I found (see Dive Master: Chak Hive). I'm not very convinced by the suggested prefix format yet and would prefer to stay with the in-game style, what about adding the total amount as suffix, probably in small tags, e.g. "Objectives:" (X in total)"? --Tolkyria (talk) 10:00, 20 June 2022 (UTC)

Sounds good. Side note: Because you mentioned that "Objectives:" is always plural I went ahead and checked collections - they do not use a colon after the word. —Kvothe (talk) 15:46, 20 June 2022 (UTC)

Added the objectives counter, removed the collection colon.

We might want to reconsider the objectives counter format/placement. Just an idea, what about aligning it to the right and somehow merging "(X in total)" and "Show all objectives" for the collapsed case? --Tolkyria (talk) 19:00, 20 June 2022 (UTC)

Might look better - worth a try. Something like X objectives total [show all]? —Kvothe (talk) 17:51, 21 June 2022 (UTC)