Template talk:Coin

0 gold, 0 silver, 1 bronze

Can we somehow alter the template to allow 1 bronze to be displayed as 0 gold, 0 silver, and 1 bronze? As well as suffix single digits (0-9) with a blank space to fix aligning completely? I can tell why aligning is favourable, but it's incomplete right now. - Infinite - talk 18:40, 19 May 2012 (UTC)

Adding zeros for gold/silver won't help, as smth like 1000 0 0 and 0 1 0 will still align differently. This should be done by making tables with right-aligned columns for money values, imo. I've fixed widths of silver and bronze parts when they have less than 2 digit value though (see examples). Alfa-R 19:59, 19 May 2012 (UTC)

And its not borked... :/ Aqua (T|C) 20:00, 19 May 2012 (UTC)

Everything should be fine now. Alfa-R 20:13, 19 May 2012 (UTC)

1  should also be displaying 0 , in my opinion. - Infinite - talk 20:13, 19 May 2012 (UTC)

Indeed. Alfa-R 20:18, 19 May 2012 (UTC)

Brilliant! - Infinite - talk 20:19, 19 May 2012 (UTC)

1 silver, 0 bronze

Last one to be added, then it should be perfect. {{value|100}} should be displaying 1 0 . - Infinite - talk 10:20, 16 June 2012 (UTC)

Why should it? isn't adding non-significant zeroes what a second parameter is for? Alfa-R 11:30, 20 June 2012 (UTC)

In-game I've seen 1 silver costs always display 0 bronze (but never 0 gold, 1 silver, and 0 bronze). This template should probably reflect that.

Also it helps aligning mixes of bronze costs and silver (+ bronze) costs. - Infinite - talk 14:48, 20 June 2012 (UTC)

Making it useful in a 'text only' context.

I'm going to add a 'text=' parameter that will substitute 'g' for the gold coin image, 's' for the silver coin image and b for the bronze coin image. This will make the template more useful in text only situations like roll-over-drop-downs. --Max 2 03:59, 20 June 2012 (UTC)

At that point you don't need this template. Doesn't sound useful. --JonTheMon 04:36, 20 June 2012 (UTC)

Au contrar: I would find it very useful. Please consider that if I am willing to put the effort into a new feature, I have a use for it. On the other hand, if you know of a reason why it should not be added, or think it should be done differently, please say so! --Max 2 05:32, 20 June 2012 (UTC)

If I'm looking at this right, if I wanted something in a 'text only' context...I'd type in the text. The template is meant to ease the use of icons; at present time typing in the template for this text only business seems like far more busywork than just saying '12 g 25 s 12 c.' -- Traveler (talk) 05:58, 20 June 2012 (UTC)

I have found a situation where that isn't practical. I need to be able to add something like |value=123 as a template parameter and have it broken down properly when displayed. --Max 2 08:50, 20 June 2012 (UTC)

This template was specifically created to display all values in their proper format. On mainspace there shouldn't be any cases of text-based value notations, which is why this template does not require a text-only parameter update.

The section above, however, does require an update. - Infinite - talk 09:52, 20 June 2012 (UTC)

You could always copy the template into your userspace and customize it to your heart's content. Mediggo 10:19, 20 June 2012 (UTC)

I agree with the others. Text isn't what this should be used for. Alfa-R 11:31, 20 June 2012 (UTC)

Where is all this should stuff comming from? This is a moderatly complex template with a whole bunch of logic making it display a compact representation of the value wanted with options. Adding the ability to choose between displaying a letter and an icon with the default being the icon is useful in at least one application I expect to see in the main pages shortly. There is no change to the current way this template has to be used. I am putting that application, which I will request comment on before moving it to the main pages, togeather in my space, and the new template it requires is also in my space. Duplicating this template in my space would make sense if I changed the way it has to be used, but I have been very careful not to do that. --Max 2 12:00, 20 June 2012 (UTC)

And that's why no one is reverting your edits, people just say that they can't see use for what your changes. This template could also replace icons with fully spelled coin names, different icons, make it display values in a column, etc. But it shouldn't, as those kinds of behavior are not used anywhere, making template bigger for no use. Now, if you could explain how are you going to use the new parameter, it will help to determine the best solution for what you need (whether adding a parameter as you did, creating a different template or just using plain text). Alfa-R 12:15, 20 June 2012 (UTC)

(Edit conflict) So, besides the changes you made to a mainspace template with nary a pause ("I want to change this", "nah", "I'll do it anyway"), it seems like the consensus is to not do it and instead you'll need to make a copy in your userspace for your personal usage. If i'm not convinced otherwise by others, i'll be reverting soon to the consensus. --JonTheMon 12:20, 20 June 2012 (UTC)

The monetary system uses very simple mathematics in this game. Sureles if you want to break down 123 into their respective g/s/b counterparts you can do that mentally. I do not see a reason to have it in this template (which is primarily for displaying and using the icons as representation). I trust that if one has a requirement to use a text only solution, that one can simply do the math and type it out sans template. Venom20 13:27, 20 June 2012 (UTC)

The purpose of this template is to display a properly formatted coin value with icons. There is no need for a template to display text-only coin values — there is no need for any template that outputs plain text (except in rare circumstances, or if they are meant to be subst:ed). If there is ever a need to display coin value as plain text, then it can be typed out explicitly. —Dr Ishmael 14:22, 20 June 2012 (UTC)

(Reset indent) The *only* reason that this template exists is for easing the use of the coin icons. Typing {{value|34041}} is much easier than typing out 3 {{gold}}... which is easier than typing out 3 [[File:Gold coin.png]]... The reason that you have decided to change it is because you want it to work for tool-tips. Where, might I ask, are we currently or planning on using tooltips (other than dye name hovers) that wouldn't be able to support images? Aqua (talk) 15:37, 20 June 2012 (UTC)

Alfa-R: There you go with the shoulds again...

Venom20: See my comments to Aqua below. I think there may be instances where someone will want to check for information consistance in the future, and having the simple value available will make those checks much simpler. Sure, I could do the arithmetic, but there is already a template that does it. Not using it would make any checking harder. I've also been known to emit brain farts from time to time when doing mental arithmetic. Using the template is likely to reduce their frequency and effect.

JonTheMon: Your ad homium comments are way off the mark. I started this discussion topic, not anybody else, and I did it before I made the change. It will be used in main space if my project is accepted. Making the change to the main space template assures that the change does not break anything.

Dr Ishmael: You are describing the current use. Future use may include more.

Aqua: That is not even how it is currently used, much less how it might be used. However you at least deserve credit for seeing the usage as part of a 'tool tip'. IMO, we could do a lot more with tool tips, especially if there are no roadblocks like the original assumption built into this template getting in the way. Specifically, in Bank commodity slots, the game displays only the icon with more descriptive information desplayed as a delayed roll-over drop-down (a.ka. a tool tip). The value of the item is displayed as a colored overlay in the lower right corner. I don't know how to add the overlay with the wiki, much less scale it down by .5 or .7 as the game does, so I put the value in the tool tip. Tool tips do not do graphics, just text. --Max 2 18:37, 20 June 2012 (UTC)

Actually, tooltips can do pretty much whatever we want them to do- see WoWPedia just as an example. Mouse over some of the loot drops. And if we wanted to implement tooltips here, we would definitely make new templates for them, not use one that's transcluded in a large number of mainspace articles. Templates should be as specific to tasks as possible to avoid breaking things if they need to be changed later on. 21:26, 20 June 2012 (UTC)

Yes, but notice that there are no graphics in the tool tips. For my Bank Pane project I have defined the needed template with a tool tip. That template uses this template to format the object's value when supplied. 'This' template is a general formating template and should be usable in a wide variaty of situations. It did, however, always insert graphic elements and those elements did not show up in the tool tips. I changed it so that it would would use text in place of the graphics if requested. The method for selecting text mode was very simple minded, not at all fancy and could have been altered or expanded later. So your arguments apply to a different level in the template structure. In a low level formating implementation template like this one, such a control is definitely in scope. --Max 2 23:25, 20 June 2012 (UTC)

"It did, however, always insert graphic elements and those elements did not show up in the tool tips." Did you try fixing that before hopping on workarounds? And what tooltips are we talking about? Javascript tooltips? title attribute? — Rhoot 23:40, 20 June 2012 (UTC)

Like I said before - if you just want a text output, then type the text you want. There is absolutely no reason for something as simple as that to be in any template.

@Rhoot - he's talking about the <img alt="alternative display text"> that some browsers display when you hover on an image. You can set it in MediaWiki's image format as [[File:Mushroom.png|alternative display text]] (if you use the thumb option, then it becomes the thumbnail caption). It's generally not a good idea to rely on this alt-text because not all browsers display it the same way. (The original intent of the HTML attribute was to be an alternative thing to display instead of the image for pure-text browsers, which are pretty much extinct now.) —Dr Ishmael 23:45, 20 June 2012 (UTC)

I am well aware of what the alt attribute does and how to produce it, just not of the fact that it was what he was trying to do. If anything though, tooltips should use the 'title' attribute and not even that is guaranteed to display a tooltip. If a tooltip is what you want you should probably be using CSS3 or javascript.

The one use this template would have with the text parameter is to convert one integer into three currencies. It could be useful in some very specific cases but I don't think we have any such specific cases yet. I would not support it going through just to be able to use in an alt-attribute on an image unless the image specifically shows cash of the amount the alt-attribute would display. — Rhoot 23:59, 20 June 2012 (UTC)

Offhand, I can't think of any purpose for the text formatting. It may exist, but not in the contexts where it is needed. As stated previously, tool-tips can be graphical. For consideration is where Template:Value will be used. I could well see it being used not just on thousands of pages across the wiki, but hundreds of times on a single page in the format of a table listing 'all of <type>'. With that in mind, it's important that this template remain short and to purpose -- extra code in the template is extra code for such pages to parse. Extra time spent parsing means extra overhead. In my book, extra overhead is bad in hyper-common functions such as this. By making it multi-purpose, you also make it more complex. More complex means more ways for it to fail. As general as the template will be, *any failure* will be bad, even if it 'works ok now'. The effort by a novice to fix it may in fact break it, breaking thousands of pages across the wiki. This is a Bad Thing. I don't like Bad Things. I try to avoid them. I am in favor of smaller, less general templates that don't cause the UniVerse to implode if they are broken in error. As stated above, if you require a different behavior, a different template can suffice. I am not opposed to the behavior you want, I am opposed to making Template:Value more complex. Torrenal 01:50, 21 June 2012 (UTC)

I should likewise mention I am not really opposing the use of a text-only value parameter or template. What I am opposed of is incorrect use of the alt attribute. — Rhoot 01:59, 21 June 2012 (UTC)

I agree with that. In-depth tooltips generated with javascript, like WoWPedia's, are something I would consider worthwhile implementing. Alt text is not the proper way to implement the functionality you want, Mtew. 03:31, 21 June 2012 (UTC)

(Reset indent) I was using the [[Image:<file>|<frame>|<text>|link=<location>]] form that {{mat icon}} uses since that was what I wanted it to look like when it was done. Presumably the wiki engine should take care of any brouser specific issues. I have since dug up quite a bit more reference material on image composition so I may be able to use the graphical form as is.

There is a lot of material out there that I am trying to collect and some of the information I have found here simply does not match what I remember from in-game. My focus at this point is on getting the Beta information into a form where it can provide a foundation for detailed release data.

I was working around the text only problem before, and the change I had made to this low-level formatting template represented an attempt to remove an unnecessary design restriction. And it worked (although some of the comments got me thinking about better ways to d it). So I'll simply wait until this issue has been properly hashed out and I will ask that someone else put it back if that is what is decided. --Max 2 05:31, 21 June 2012 (UTC)

Great, I'm looking forward to seeing what you come up with. 14:50, 21 June 2012 (UTC)

FOUL Discussion was still in progress!

JonTheMon: You are way out of bounds here. Others have considered reverting the change and decided not to do it. You are declaring 'consensus' while the issue is still up in the air, and that is cheating. I think this is simply a personal vendeta on your part. You have shown me considerable disrespect in the past, and this is just another example. You have not responded to my points with logic, just opinions. I'll delay putting it back until others have had their say, but I will put it back because I have a critical need for the change. --Max 2 18:58, 20 June 2012 (UTC)

If you need it, copy it to your userspace. I think that message should be clear by now. Mainspace templates are not modified for personal use. If you intend to use it in a project that might later be implemented in mainspace, you can still use your userspace variant before going modifying mainspace templates, or at least bother explaining how you're going to use it and how this would exactly benefit the wiki and the occassional viewer. Mediggo 19:03, 20 June 2012 (UTC)

(Edit conflict) Jon was not out of line. Consensus was pretty much reached between those that presented their arguments up top. On similar lines, templates are not personal space. Your needs are not the communities. If the community doesn't have a critical need for the change, then the change probably shouldn't be implemented. -- Traveler (talk) 19:04, 20 June 2012 (UTC)

?? From readin things, the only individual who seems to be strongly in support of your edits is you, with several opposed. I was going to weigh in tonight among the opposed, but the big, bold 'foul' statement prompts me to respond now. Please, do not get emotional, that does not help your argument or the wiki. You can note that alternatives were suggested, such as creating a new template for the task you need. Never underestimate the power of the KISS design. I believe that should be applied here, and anything not simple belongs in another template. Torrenal 19:10, 20 June 2012 (UTC)

@Max 2. The consensus above is clearly that it doesn't need to be in the mainspace. I can't speak for others, but personally I haven't reverted it - despite a bunch of opinions against the change already being there - because I was hoping to see an explanation from you on how are you going to use it in the mainspace, but I totally agree with the revert. There is nothing wrong with what Jon did, he asked if anyone is against the change, and people (silently) agreed. I also can't see any vendetta from Jon here, so, please, calm down. You can always create a template in your namespace and use it there to set up some examples of how it can be used, and then propose a change to the community. Alfa-R 19:14, 20 June 2012 (UTC)

I still think he jumped the gun on the revert. Discussion was, and really still is, underway and he should have waited at least until the last round of comments had been considered before forcing the issue. Further, his attributions of motives to me is simply inconsistant with the sequence of events. That alone shows his disrespect. Given that, I think he should not have been the one doing the revert. (He also did a sloppy job of it, reverting changes others had made since I changed things. That shows an ill-considered haste on his part.) --Max 2 20:04, 20 June 2012 (UTC)

If you need it, then it can be in your userspace. Aqua (talk) 19:39, 20 June 2012 (UTC)

(Edit conflict) I need it at the moment, but I think many people could use it. It also needed to be checked to be sure it did not break other peoples use of the template. Without the need to assure things didn't break, I would have put it in my space. I did not see one 'you broke it' comment in the lot. If I had seen even one, I would have pulled (or fixed) the change immediately! --Max 2 20:04, 20 June 2012 (UTC)

That argument doesn't work. I could add a random parameter named "Aqua" to the Skill infobox template. It wouldn't do anything and therefore it wouldn't break anything, but people still wouldn't want it there. Aqua (talk) 20:09, 20 June 2012 (UTC)

The argument could also be made that you jumped the gun by making your change without waiting for discussion. —Dr Ishmael 20:12, 20 June 2012 (UTC)

Some changes

I've improved the code a bit. Works exactly as before, except some spacing issue I've seen you've been discussing. Now it's just a normal space all the time, but you should be able to make it have custom spaces easily by editing it, every part has its own clear line now you can put between span, or add more spaces. If you have problems trying to add custom spaces, just ask here, or feel free to revert it while we fix it.--Lon-ami 13:47, 7 July 2012 (UTC)

Alignment and spacing, especially for the all-icon version

There are three issues for the all-icon version:

1. The spacing is off: {{coin|105699|x}} should align with {{coin|100699|x}}, but does not; see below.
2. There should be commas for large values, e.g. {{coin|10000000}} should display as 1,000 instead of 1000 .
3. The spacing from number to coin should be noticeably less than that from gold to silver to copper (i.e. in the example below, 10 should be a bit closer to the gold coin, but 6 should be further apart; currently, they appear to be equidistant).

Alignment test (1)

10  56  99  ← {{coin|105699|x}}

10  6  99  ← {{coin|100699|x}}

(See how the gold coins align, but not the silver or copper ones.)

Comma test (2)

1000  ← {{coin|10000000}}

1,000

Separation test (3)

10  56  99  ← {{coin|105699|x}} (template)

10  56  99  ← (using &thinsp; and &ensp;, although I suppose other widths are reasonable.)

10  56  99  ← {{coin|105699|x}} (template)

10  56  99  ← (uses &nbsp; instead of &ensp; — worse than original imo, b/c it's more compact)

10  56  99  ← {{coin|105699|x}} (template)

10  56  99  ← (uses ordinary space instead of &ensp; — so close to current that maybe not worth effort)

– Tennessee Ernie Ford (TEF) 03:57, 11 July 2012 (UTC)

The use of '&thinspace' is entierly appropriate.  '&ensp' is probably over doing it a bit.  The seperator should be local selectable.  I think there may be a unicode for that; that is, something other than a comma (',').  I suspect you will need to special case '1' to keep the spacing consistant.  That or shift to a mono-space font (preferably not courier).  --Max 2 06:56, 11 July 2012 (UTC)

I don't think there's enough contrast using a regular-width space, but I am going to leave the implementation of it to others. – Tennessee Ernie Ford (TEF) 07:21, 11 July 2012 (UTC)

Using &nbsp; will keep the parts together, which I think is a good idea.  --Max 2 08:01, 11 July 2012 (UTC)

1)I don't see a problem with that. Either there would be an unusual gap or there would be a leading zero, neither of which look good. 2) I don't think this template should do that, since there's the question of separator and that would make the logic a lot messier (1 million gold). If you're that high, you can just switch to {{gold}}. 3) Eh, looks fine to me. We could try to make the number closer to its icon, but at that point you might want to remove the space altogether. --JonTheMon 12:48, 11 July 2012 (UTC)

1 and 3 can both be solved by wrapping each value in a div with min-width. Since the style is repeated for all three values, it should be added to Common.css as a class.

10

  

6

  

99

 

2 can be solved with the {{formatnum:}} magic word. Are those acceptable? —Dr Ishmael 14:27, 11 July 2012 (UTC)

Random question everyone else has probably considered already: is the font being used a monospace font? 71.204.175.10 15:48, 11 July 2012 (UTC)

I'm good with Ish's proposed changes. (And the examples above will provide a decent test-case.)

@Jon: of course, for stuff > 10,000 gold, {{value}} is probably a poor choice, but I expect to see a few uses for amounts in 1,000 - 5,000 range. However, since it's easy to use a magic word that resolves the issue, why not make it easy for people? That said, I wouldn't be opposed to a usage note that recommends against using the template for more than a few hundred gold. – Tennessee Ernie Ford (TEF) 17:42, 11 July 2012 (UTC)

That magic word would be sufficient for larger numbers. However, i'm still not sure about the spacing issue. In -line or by itself, the proposed spacing looks odd. It only really benefits tables and there it starts off correctly aligned. --JonTheMon 18:12, 11 July 2012 (UTC)

Even when they "start off" aligned, only one edge of the entire value output is aligned, not each individual component. If any of the values have single-digit g/s/b numbers while others have double-digit numbers, then you're going to lose component alignment.

10  56  99 

10  6  99 

10  6  9 

10  56  9 

1  6  9 

1  56  99 

—Dr Ishmael 18:29, 11 July 2012 (UTC)

(Reset indent) So, those do look badly aligned, but there's still the issue of in-line or solo values. It's almost like we need another parameter or a different template. --JonTheMon 18:41, 11 July 2012 (UTC)

Why wouldn't this work? For example, I don't think

10

  

6

  

99

  looks horrible. With how the template is coded, we could only use the div on any interstitial numbers, i.e. leave it off of the left-most number, like 10  

6

  

99

 . If you really didn't want the spacing for a certain usage, you can use the individual g/s/b templates. —Dr Ishmael 19:07, 11 July 2012 (UTC)

I suppose so, but I still think it looks odd. --JonTheMon 19:10, 11 July 2012 (UTC)

Rename from value to coin

I would like to suggest to rename this template to "Template:Coin". My main reason for this is that it is not only used to display values, but also costs. (We make an important distinction between value and cost on all items, cost for acquiring and resell value.) This is simply a template to display coin in different contexts, so I think an (even more) generic name would be fitting. I didn't add a move suggestion because I simply don't remember how to make it not appear on every page that includes this template :P - anja 12:11, 11 August 2012 (UTC)

Update

So it uses ishmael's solution when the format parameter is true. It looks pretty good in text (just don't format). I want to change the second parameter to a level so:

1 - Display bronze and silver

2 - Display bronze, silver, and gold

As bronze will always be displayed otherwise appear blank. {{coin|100}} would just display the silver, {{coin|100|1}} would display 1 silver and 0 bronze, {{coin|100|2}} display as it does currently.--Relyk 11:40, 7 November 2012 (UTC)

A final addition

I think this template is almost perfect, save for one small thing that irks me, the impossibility to use the alignment of the second parameter without the gold coin being added (for values under 1g). Per example:

99  99 

9  99 

99 

9 

Using the second parameter always adds the gold coin in the value. This is occasionally required, but far from always. Certain lists have values only ranging between a few coppers and a few silvers, no gold coins in sight. Currently, aligning those must be fully manual (unless I'm missing something here). I feel that lists where no gold coins are present in-game should also not show gold coins on the wiki. Currently, lists (would) look like this:

9  99 

7  9 

16  99 

7  99 

8  99 

9  9 

5  49 

Even when right-aligning these values, you will notice an inconsistency:

9  99  7  9  16  99  7  99  8  99  9  9  5  49 

Therefore, I was wondering if there can be another parameter, or an update to this template in another fashion, which can align silver and copper values, when gold isn't applicable. I have tried this in the past, but couldn't figure it out. Reading above, I think that is due to my inexperience with HTML names. Anyway, I hope I can expect a response. - Infinite - talk 14:02, 6 December 2012 (UTC)

I noted this in the section above >.> There are other cases that can be ignored to make this simple to stick in but ugly code. You have the case where all value are bronze, which will align properly; you can just use the template for formatting the portion with gold or silver value if you bother at all. You have where all values have gold and silver, where you'll include copper anyways. With that in mind, it's a two second change to the if statement.--Relyk 16:50, 6 December 2012 (UTC)

Ok, I noticed you went ahead and changed this, but did you make sure all the cases acted the same? The examples seem off now (e.g. 0 coins with "yes" parameter). Don't forget to sandbox first, since this is used so many places. --JonTheMon 03:22, 7 December 2012 (UTC)

And what about values of less than a silver, listed between silver prices? Same first example in this section, but the 9 and 99 should have its silver automatically removed. After that it is perfectly universal. :) - Infinite - talk 13:43, 7 December 2012 (UTC)

Which was intentional as I explained, I have a sandbox, and show preview was enough for that change jon :3 Mixing formatted and non-formatted leaves that spacing in div tags when there's no line indents and no one obviously wants the option to leave the gold and silver icons.--Relyk 20:58, 8 December 2012 (UTC)

Probably wrap the line in a div, that way we don't have to align-right it in every place. inventory template does it for you thankfully. My point on leaving the gold and/or silver icons is that you are listing values in terms of silver, gold, or copper when you format in the same way you list cents as a decimal of a dollar. For example: User:Relyk/coin. However, it's just as well to mimic the in-game method for listing coin.--Relyk 21:05, 8 December 2012 (UTC)

Comparing to dollars/cents doesn't map exactly. In that case, you are representing a value as a single rational number with a precision of 2. The only currency symbol is the dollar sign. In our case, we have a value split into 3 integers with 3 different currency symbols. I'm not sure that there *is* any real-world example of such a currency system. I support the in-game system of hiding the higher denominations when they are not used. —Dr Ishmael 22:20, 8 December 2012 (UTC)

Rylek's hit the issues right on its head in the last table on his sandbox, where the values are displayed perfectly, and I think the option to display gold and silver is still present in that template, as well (I skimmed the code very briefly). - Infinite - talk 12:37, 9 December 2012 (UTC)

Good ol' LSD, Doc - pounds, shillings and pence. Yes, I am that old. — snograt 14:59, 9 December 2012 (UTC)

Why thank you, Snog. From what I can find, it looks like the convention there was the same as GW2 in-game: omit any higher, unused denominations. —Dr Ishmael 15:45, 9 December 2012 (UTC)

Is there any way to get rid of the copper value when listing values that are just in gold? --JonTheMon 01:06, 10 December 2012 (UTC)

Use {{gold}}? 2  —Dr Ishmael 05:16, 10 December 2012 (UTC)

Well, yes, but I was wondering if it was possible with this template. Or are we stuck with always having a copper value. --JonTheMon 05:21, 10 December 2012 (UTC)

There you go.--Relyk 06:33, 10 December 2012 (UTC)

Thanks, but I perhaps phrased it wrong and should have asked "should this template do that"? If that's how it is, either way, then that's fine. I suppose I made my question more of a statement than it should have. Anyhow, is this how everyone else wants to leave it? --JonTheMon 07:10, 10 December 2012 (UTC)

All the coin listed in-game is formatted, but 0-valued denominations are omitted in prose on the wiki. I don't see people keeping coin denominations in anywhere not on a list.--Relyk 08:05, 10 December 2012 (UTC)

For the sake of the server's processors, we really should use the simpler individual templates for single-denomination values, instead of always using this template with its multiply-branching code. Otherwise, what's the point of having separate templates? —Dr Ishmael 13:21, 10 December 2012 (UTC)

The template assumes a combination of gold, silver, and bronze with the parameter, so of course, it will have to do additional work to check for single-value denomination to do less work. If you just want a template to output single values, you're abusing the purpose of the template, but should still be able to do it. All it does for unformatted is use the individual templates and adding spacing after all. Separating the formatted and non-formatted code into separate templates is a good idea as their usages are mutually exclusive.--Relyk 01:15, 15 December 2012 (UTC)