Template talk:Rarity

Syntax

Is there any reason why this template uses the deprecated <font> instead of <span style=...> tags? – Tennessee Ernie Ford (TEF) 17:02, 1 May 2012 (UTC)

No idea, but changed them all to spans. - Infinite - talk 19:35, 2 May 2012 (UTC)

Common

Is there a way that Common-grade designation can not be bolded? Would there be support in that? The heaviness of it places too much emphasis on basically the lowest rank of items in a merchant table and otherwise seems like an odd choice of emphasis for an item. Redshift 22:27, 13 June 2012 (UTC)

Yellow text on white background?

For ERare, the text is not what I would call especially readable. Could we get something with more contrast? Torrenal 04:24, 15 June 2012 (UTC)

Same thing with junk color. --Draygo Korvan 19:26, 18 June 2012 (UTC)

The existing colors are very similar to in-game colors (though in-game doesn't have white backgrounds). I looked at the RARE color for quite a while. Personally I don't have any trouble reading it. Is it better like this instead? It's difficult to add any more red, because then it becomes orange and looks too much like the EXOTIC color. We could make that darker too, but then it would look a funky brownish color.— Burfo 01:23, 23 August 2012 (UTC)

Why not giving them a shadow? Clear text with dark stroke can be read over any background. The CSS text-stroke property is not widespread yet, but "text-shadow: 0 0 1px black;" should do the trick well enough. Mith🌟Talk 21:31, 23 May 2019 (UTC)

Common as default

Is there a reason common is default? It'd make a lot more sense to me if {{rarity}} produced Unspecified and would make it easier to use this in templates. — Rhoot 12:48, 18 June 2012 (UTC)

If I had to guess, I'd say because this was set up so you can do {{rarity|msaterwork|Burfo's Boomerang}} (typo intentional) with a custom display text, and how would that display in unspecified text font? I don't mind if you change it, but how would you figure out how many basic items are (correctly) using the {{rarity}} that would therefore break?

Update needed

Legendary weapons are purple, not red (proof: Legendary Weapons Thread GW2Guru), so templates need to be changed. Should we use the same color for Mystic and Legendary? Linu 12:18, 2 October 2012 (UTC)

There's No Need For Erroneous Backward Compatibility

One editor kept the color for Legendary listed as "red" rather than the correct purple for backwards compatibility with some pages that are still using the "red" part of the template. This is undesirable. If these pages are using the wrong template then we should change them rather than making the system arcane and confusing with colors that don't do what they say they do.Strill 21:33, 15 October 2012 (UTC)

The problem is that most legendaries were denoted as red. The template update broke all enties. I agree with you, but if a template is updated, the guy who does the update, should make sure that nothing breaks because of that. If he does not a bit of backwards compatibility is desirable.

At the moment everything seems fine so the need is gone.- Yandere 01:59, 26 October 2012 (PDT)

Sorting

Have you considered adding a sort value to this template, such that when you click on the sort arrow at the top of a table it would sort like "Junk -> Basic -> .. -> Masterwork -> Rare -> Exotic" as opposed to by alphabetical order? Thoughts?

My suggestion would be formatted like:

<span style="display:none" class="sortkey">key</span>

(where "key" would be A for junk, B for basic, C for Fine, D for Masterwork, E for Rare, F for Exotic and G for legendary) 192.168.104.82 16:02, 23 October 2012 (UTC)

I see now that your formatting guidelines recommend alphabetical for everything. Still, I think that sorting it by anything other than superiority would be stupid :p Chieftain Alex 17:11, 23 October 2012 (UTC)

Yeah, this sounds neat, I'm all for it. Manifold 16:02, 25 October 2012 (UTC)

Apparently the class thing was just a label so I can get away with just this:

<span style="display:none">key</span>

Chieftain Alex 23:41, 25 October 2012 (PDT)

Internal Linking

Hi all, I am new to wiki editing and I am wondering if it is possible to keep an existing internal page link and also use the rarity template to colour the link. At present when I try various combinations I can't get them to work together. Any advice would be great. Yojimoshie 08:53, 7 November 2012 (UTC)

If I found a situation that I wanted the colour I'd use

[[User:Chieftain Alex|{{rarity|Exotic|Daft user}}]]

which would give FDaft user

Where were you wanting to use this? (I saw you using something similar at the top of weapon articles, but I'd leave them as uncoloured links since the infobox already tells the user the rarity (and its colour). --Chieftain Alex 10:49, 7 November 2012 (UTC)

My intention is to update as much as the PvP weapon section as I can, on each section I would like to link to the PvE equivilent and visa versa in the notes section, the one for the PvP Priory Staff in the main article was used as a test before I found the sandbox mode this morning, it's my second day here :). I have tested your suggestion above and it works exactly how I wanted it, thank you. Yojimoshie 11:31, 7 November 2012 (UTC)

Font colors shouldn't be used in prose. It doesn't look god and can be distracting. Especially the rare and exotic font :<--Relyk 11:55, 7 November 2012 (UTC)

Thanks for the feedback, I have reverted a minor edit and will keep this in mind when making future amendments Yojimoshie 13:23, 7 November 2012 (UTC)

Default case

Currently the template always forces Upper Case names, e.g. {{rarity|exotic}} becomes FExotic, instead of Fexotic. But the wiki's practice is that only proper names should be Upper Case and none of the rarity names are proper. So, shouldn't we change the temple so that the default is lower case? Or would it be better for the template to respect case? e.g. {{rarity|exotic}} = {{rarity|exotic|exotic}} and {{rarity|Exotic}} = {{rarity|exotic|Exotic}}. 75.37.16.187 21:14, 23 May 2013 (UTC)

No, you shouldn't use this template in prose.--Relyk ~ talk < 21:25, 23 May 2013 (UTC)

why not? 75.37.16.187 22:23, 23 May 2013 (UTC)

For the same stylistic reasons that you shouldn't capitalise every letter and colour them differently.. it just looks ugly ;) -Chieftain Alex 23:50, 23 May 2013 (UTC)

I agree with Alex, it doesn't look good to color and bolden random words in free text. Within infoboxes and tables that's fine, since those cases will also only be using it as a single word in a list of data points, ergo it should be title-case, the way this template was designed. —Dr Ishmael 00:06, 24 May 2013 (UTC)

Okay, it's been 6 years, can we revisit this? ;) This template can make prose more readable, see Piece of Unidentified Gear. I'd like the template to respect the case of its first parameter. --BuffsEverywhere (talk) 06:41, 4 August 2019 (UTC)