Template talk:Infobox status

From Guild Wars 2 Wiki
Jump to navigationJump to search

You know I genuinely never noticed when you made this template, I was thinking I might make a template to stick at the top... but I went to the infoboxes category and found this already here. How about we set both "Is historical" + "Has availability" here? -Chieftain AlexUser Chieftain Alex sig.png 22:25, 10 February 2015 (UTC)

Discontinued[edit]

I really don’t like this “discontinued” status, or maybe it’s just the description text… Anyway, I fear that this will be used on item pages for items that can no longer be acquired, for example for event-related things, or even for living story stuff. And I really don’t want to see all these items plastered with such notices. If the item still exists in-game, then it shouldn’t have such a big template at the top. Its acquisition section should instead explain that you can no longer get it through regular means. poke | talk 18:45, 13 February 2015 (UTC)

I agree, that one doesn't really fit with the rest of the options. —Dr Ishmael User Dr ishmael Diablo the chicken.png 19:35, 13 February 2015 (UTC)
The purpose is we want to inform players whether they can access the content or not. For event-related items that are bound, readers will want some indication of that. We can probably do that in the summary or acquisition in prose. The summary is used in articles for releases, living world, and other content. In the case the item can be traded, the discontinued status would indicate there is a limited quantity in circulation. An infobox should have some way to identify that.--Relyk ~ talk < 19:58, 13 February 2015 (UTC)
My point was that "status" doesn't fit in the same spectrum as the rest. The others are all based on whether the content exists in the game or not. "Discontinued" is based on whether the content is accessible, which should be considered a different type of status; it doesn't need to be in this template, and it definitely doesn't need a giant quaggan in the notice box. —Dr Ishmael User Dr ishmael Diablo the chicken.png 20:26, 13 February 2015 (UTC)
Wrong indentation >.> I agree status/notice isn't an appropriate place.--Relyk ~ talk < 21:18, 13 February 2015 (UTC)
I don’t mind the infobox tracking this kind of information (although I fear that this might end up being a maintenance problem for things that end up returning later); I do mind that heavy box though. Just like we don’t put {{temporary}} on items that are event/story-limited, we shouldn’t put such a discontinued notice on them either. poke | talk 21:24, 13 February 2015 (UTC)

Heart of Thorns[edit]

"heart of thorns = {{Heart of Thorns future content}} {{#set:Is historical=Y|Has availability=Future}}" — Future content that is historical? Is this to keep pages out of templates on purpose or can this be changed to allow them into {{Trait table}}? Mora 00:21, 21 February 2015 (UTC)

Property:Is historical is set for compatibility, we can use Has availability for filtering.--Relyk ~ talk < 00:40, 21 February 2015 (UTC)

Usage in Infobox templates[edit]

Just pondering... Most of the Category:Infobox templates that incorporate this template have a description for the status parameter of:

status
Optional. Status of content. Only set if not currently obtainable ingame, displays relevant notice. Available options: "historical", "discontinued", "future", "unimplemented", "current" (default).

(as an example) there is some variety in the "available options" shown, and very few show the heart of thorns/hot option.

I'm just wondering if there's any mileage in going through each Infobox template, and adjusting the status parameter description to something like:

status
Optional. Status of content. Only set if not currently obtainable in the core game. For available options see {{Infobox status}}

which would mean all the possible status options (and any updates to them) only need to be listed in this one page? ingame to core game is also a deliberate careful choice of words, since this template now indicates HoT (or not!) content.--BramStoker (talk, contribs) 13:35, 17 February 2016 (UTC)

The HoT option is meant to be temporary until we implement a suitable way to indicate what module/release the content belongs to. The parameter only deals with the temporal availability of the content. I would copypaste the documentation on the template itself to the infoboxes since it's relatively static.--Relyk ~ talk < 15:23, 17 February 2016 (UTC)
The variable status = hot still remains undocumented, even though it is very widely used already. And because of its undocumented status, there are no official recommendations or guides when and where it should and should not be used. As a result, different authors use it in different sense. For example, we have a crafting material which can be obtained in core areas but is useful only in HoT recipes. Player without HoT can obtain such material but cannot use it; however, it's possible to sell it via Trading Post. Should it be labelled with this status (and HoT icon on the page) or not? Sure, you may not have an answer right now, but such recommendations should be elaborated eventually. They also will be applicable to the future expansions. --66.102.9.82 21:05, 20 April 2016 (UTC)

Inheriting status[edit]

I'm not sure, but was this edit, inheriting the status from the last status template that was called outside, too much? Sometimes, an upcoming item simply has {{Future content}} but does not set status = future in the infobox, here I think this edit makes sense. However, for the template {{temporary}}, which is only called outside this template, it might be too strict, e.g. Trick-or-Treat Bag or Wintersday Gift would be set to historical due to my edit although the are available on the trading post the whole year. Or on the other hand, maybe marking temporary content with historical isn't "correct" and we should introduce the new option Has availablity = "Temporary" and Is historical = "false" for content returning each year during a festival.

Again, I don't know, maybe we simply revert my edit. --Tolkyria (talk) 18:41, 14 October 2020 (UTC)

Partially nevermind, I removed the inherited variable from {{Temporary}}. The four other availabilities: unimplemented, future, historical, discontinued are fine imo. --Tolkyria (talk) 19:01, 14 October 2020 (UTC)