Template talk:Contained in

The "contained" templates have been used for ground chests. That's a good idea, but this template doesn't seem to have an option to hide icons, which results in empty icons when used for those. It'll be nice if this didn't show icon if there was none, or if there was an option to hide the icon. MithTalk 23:24, 21 August 2014 (UTC)

That's only two pages: Dragon Chest and Sylvan Chest. I would argue that they should not be using {{contains}} at all, for different reasons:

• Dragon Chest uses it to list exclusive rewards, items that (AFAIK) can only be obtained from that chest. We don't need dynamic templates for that. Superior Rune of the Sunless is the only one doing it, so just replace this template with static text.
• Sylvan Chest uses it to list completely generic stuff - AFAIK (again), all chests can contain any tier/type of gemstone.

—Dr Ishmael 23:54, 21 August 2014 (UTC)

Whitespace

When used last in acquisition sections it adds unnecessary whitespace, as seen on this page, for example. However, when it's used in between other templates, such as on this page, it works fine. The issue doesn't appear when items are split into columns, so I'm assuming that it has something to do with the recent edits that added the column property. —Ventriloquist 13:18, 2 May 2015 (UTC)

Chieftain Alex on mobile here: I removed the newlines yet the problem is still there - it occurs for both with and without columns? I'll try again when I can inspect the html. -81.153.69.201 14:41, 2 May 2015 (UTC)

Nope, looks fine on two columns. —Ventriloquist 14:44, 2 May 2015 (UTC)

Replacing the template on Experience Booster with

{{#ask: [[Contains item::Experience Booster]] | format = ul }}

still results in a rogue newline on the end... so I think it is a SMW bug. Nevertheless, wrapping the output in a div will remove it. -Chieftain Alex 22:00, 4 May 2015 (UTC)

Hey, as long as it looks good, I'm happy. I take it there's no way to fix this bug without a wiki maintenance? —Ventriloquist 22:43, 4 May 2015 (UTC)

First it would have to be reported to the SMW team so they can fix it in the base code and roll it into the next version. Justin doesn't really like applying band-aid fixes on our own. —Dr Ishmael 01:47, 5 May 2015 (UTC)

Historical content

Can, or should, this template ignore historical content? I was looking at Gold Fractal Weapon Crate which appears to be contained in Champion Chest of the Mists, but the latter is no longer available in game. So should the gold fractal weapon crate still be listing as acquired from the champ chest? --BramStoker (talk, contribs) 08:24, 14 July 2016 (UTC)

Removing historical sources will empty out a lot of existing pages, so I'm against it. —Ventriloquist 08:58, 14 July 2016 (UTC)

It is possible for historical containers to exist in game and they would have a loot table, so we shouldn't ignore historical content. It is also possible that ANet removes a particular container from everyone's bag, but we wouldn't know if the loot table has been deleted from the game database. I wouldn't mind seeing a little note about whether the container listed is "historical" for convenience, perhaps even splitting the list into 2. Currently readers would have to check each container to see if it's marked historical. --BryghtShadow (talk) 09:15, 14 July 2016 (UTC)

That would probably be more useful, and somewhat inline with vendor templates which allow the greying-out of historical content. I can see that there could still be historical containers or old / less used accounts, but no doubt their presence will dwindle with time as players do use them up. --BramStoker (talk, contribs) 12:18, 14 July 2016 (UTC)

Came here to say all of this... ended up just doing it. -- Dagger (talk) 14:45, 26 August 2016 (UTC)

Counts and Columns

I thought it was just Dragonite Ore and Empyreal Fragments but it seems there's a few others. Is it possible to add that if an item is in over 75 containers it has 3 columns and if it's in over 100 containers that it has 4 columns? Or should I just continue with how I set up the aforementioned mats(mostly the t5 Fine mats + Silk Scraps and Thick Leather sections)? - Do_odleplex 22:03, 12 May 2017 (UTC)

Thanks Alex! - Do_odleplex 00:52, 13 May 2017 (UTC)

Context on acquisition

It would be nice if we could determine if the acquisition method is via drops or via purchase from a vendor. Anzenketh (talk) 23:36, 2 June 2019 (UTC)

Bold text suggestion

Could this template use bold text to emphasize "guaranteed" and "choice" (or perhaps different color)? This would be very helpful to easily identify the guaranteed loot in a long list of items. The word "chance" and "choice" look very similar and are then easily confused with each other. It takes more time to search with your eyes for items with "choice" especially with the small text and when the list is very long. Example

• Tiny Bag of Stolen Goods (chance)
• Tiny Bag of Stolen Goods (chance)
• Tiny Bag of Stolen Goods (guaranteed)
• Tiny Bag of Stolen Goods (chance)
• Tiny Bag of Stolen Goods (chance)
• Tiny Bag of Stolen Goods (choice)
• Tiny Bag of Stolen Goods (chance)

--78.8.143.133 17:14, 21 December 2022 (UTC)

Good suggestion. But would it be too obtrusive if the list was mostly choice or guaranteed (for example in Pristine Fractal Relic)? --BuffsEverywhere (talk) 20:28, 21 December 2022 (UTC)

Maybe can add parameter for show bold or conversely if need, then should be solve too obtrusive, i think -- Wong8888 (talk) 21:56, 21 December 2022 (UTC)

I believe it won't be too disruptive, given that the text is already small anyway. Most wiki users are gamers who are used to identifying content visually. But if you think so then maybe sorting would be a better approach. First guaranteed, then choice, then chance. We already have sorting for historical items, which are always at the end of the list. --78.8.143.133 09:16, 23 December 2022 (UTC)

Due to a wiki bug, the list can't be automatically sorted by historical items as well as drop chance for now. However, I've added a chance parameter to this template to filter the list so it can be split into sections, like this:

=== Contained in ===
==== Guaranteed ====
{{contained in|chance=guaranteed}}
==== Choice ====
{{contained in|chance=choice}}
==== Chance ====
{{contained in|chance=chance}}

See Dragonite Ore#Contained in for an example. Since this requires manual editing, it isn't an ideal solution to the issue so I've also implemented the suggestion for bold text for "guaranteed" and "choice". Let's see how it goes. --BuffsEverywhere (talk) 09:16, 25 December 2022 (UTC)