Template talk:Named Armor

Named Robes & Docents

Is there a way to get robes/outfits and docents to automatically pop into categories like light/medium/heavy armor does? I know that [[Template:Unique robe]] and [[Template:Unique docent]] do it, but I'm not sure how... I also have no idea how hard it would be to code it so that it reads the Armor Type and strips out the useless bits (ASF, dex bonus, etc) from the display, or at least strips out the feat and puts them in "Category: Named Robes" or "Category: Named Docents".

Or should I just forget about trying to combine robes, outfits, docents, and armor into one template? *g* - LrdSlvrhnd 17:58, April 14, 2011 (EDT)

Neouni Has removed these templates and relocated all items that used the to the "named" equivalent. ShoeMaker 22:17, May 18, 2011 (EDT)

Category Injection

Question : Why was the template modified to inject the branch category "Armor" in to items that contain this template? The template already injects leaf categories Cloth armor / Docents / Heavy armor / Light armor / Medium armor.

Given the logic of having the item exist in it's parent category, is there going to be a push to have the item live in the grandparent "Item" category as well?

It seems to me like confusion and duplication to have an item exist in it's leaf category as well as it's parent branch category. Should the Gloves / Belts etc also be part of THEIR parent category "Clothing"?

What is the reasoning behind this? The NiceCategoryList2 extension allows for defining a depth, so someone could retrieve information about a particular category branch and all leaf pages contained therein.

I've been working to clean up the category structure to make it more consistent, and remove duplication. I believe if the changes I'm making to try and clean up the wiki are going to be reverted, an explanation and discussion should happen first. See DDO wiki talk:Category policy

Joenuts (Contributions • Message) 12:37, September 30, 2013 (EDT)

Category:Armor is a heavy traffic page which had all its information removed. Its the is page which "List of all armor in the game" even when the key fields are missing, incomplete, incorrect or when all the other pages haven't been updated. Bladedge (Contributions • Message) 13:55, September 30, 2013 (EDT)

If the only reason for injecting armor item pages in to both the "Armor" parent category and the "Armor type" child category is to allow for a complete listing when viewers pull up the "Armor" parent category page, then I propose an alternate solution.

I suggest using the NCL extension to provide a listing of all pages in all subcategories of the "Armor" category on the Armor category page. For example : <ncl style=compact>Category:Armor</ncl> will show a simple listing of all pages sorted alphabetically, by subcategory.

It's very elegant, and removes the duplication so that item pages can adhere to a simplified category policy.

Joenuts (Contributions • Message) 14:58, September 30, 2013 (EDT)

It also has the benefit of not chopping the list in to sections of 200, so that the single page would ACTUALLY SHOW a list of ALL armor.

Joenuts (Contributions • Message) 15:02, September 30, 2013 (EDT)

I'm neutral, for the moment. I just believe that discussing over a demo is much better than discussing over imagination. Demo: User:Aldyron/Sandbox/Category Armor with ncl experiment. Feel free to edit or move the page.

So, if I got this right, the duplication of every armor before the sorting into categories is due to the fact that each suit of armor currently belongs to both the Armor category and the kind-of-armor category, right?

Aldyron (Contributions • Message) 19:34, September 30, 2013 (EDT)

Aldyron, you are absolutely correct. The fact that pages belong to both the category "Armor" and the category "<armor type>" is the cause of the duplication when displaying the pages that belong to Category Armor and any sub categories.

I am unaware of an easy way for an editor to list out all pages within Armor sub categories, but not pages in Armor. Other than maybe creating a list for each and every sub category independently.

Yet another reason for the removal of the pages to exist in two unique categories.

Joenuts (Contributions • Message) 19:46, September 30, 2013 (EDT)

Race restrictions

Maybe the race field needs an update: iconic races are not covered.

Then again, maybe not: I'm not sure, but are the only items with such race restrictions those in the respective starter equipment containers? In that case, would it be worth it?

Aldyron (Contributions • Message) 12:40, October 16, 2013 (EDT)

Example: Item:Creation Forge Docent Aldyron (Contributions • Message) 12:43, October 16, 2013 (EDT)

Tabs for different visuals

First off, I want to remind everyone that I'm not versed enough in codification to know if this is possible to do with our current system, but I want to throw a wild idea on the air, for those who do understand enough of coding.
Right now, every armor page have a single image pic. For many armors (specially in the first years of the game), this is enough. There is some variation on race and gender, but they are not THAT different. However, we have some armors now that looks wildly different on male and female characters. The Cormyrian Green Dragonhide Armor is the most prominent example.
There is also another place where differentiation would be helpful: Docents in general have different visual depending of your body feat. And that is not counting that we can add Iron Defenders on this list as well, since docents change the color of their stripes.
I was thinking about a dynamic tab system, like the one existent on the Final Fantasy wiki when they need to showcase enemy sprites that were revamped in later releases. Just to give an example, take this link and see the tabs above the creature's image. We could have four tabs on every docent (for Composite, Mithral, Adamantine, Iron Defender), and two for each non-docent armor (for Male and Female). If we REALLY wanted to be complete, under the gender tab could also be a race tab, but that would require even more work. ~ Nibelung (Contribs • Message • Email) 02:39, October 18, 2015 (EDT)

• Your example is on a wikia wiki instead of a mediawiki wiki. Different software. It also make use of javascript, which would be a pain to manage if someone wanted to create it. Then, you'd have to find someone with the time and ambition to gather all of the screenshots. I'm not opposed to the idea, but I'd rather see a much larger collection of screenshots to make it worth-while to invest that kind of .js development time into. The best thing to do for now is just include all of the views as a gallery below the item for now. Just my opinion, others may vary. ShoeMaker (Contribs • Message • Email) 16:39, October 18, 2015 (EDT)

Usage shown is incorrect

In the usage section 'Enhancements' is called 'Enchantments' and 'Weight' is called 'lbs'.

Instead of "Enchantments =" it should be "Enhancements =" and instead of "lbs =" it should be "weight ="

Can't edit of course because it is a template.

⇒ Some call me Tim (Contribs • Message • Email) 23:05, July 27, 2018 (EDT)

• ✔ Done ⇒ DDOstream (Contribs • Message • Email) 11:49, August 1, 2018 (EDT)

Race Absolutely Excluded None?

Looks like a bug creeped in here. All armors (non-docent) without race requirements now say "Race Absolutely Excluded None" rather than "Race Absolutely Excluded Warforged".

It appears that when the changes were made to use the new variable RaceName back on June 23, 2019 the default value for race was changed from "Warforged" to "None". The nonsensical value of of "Warforged" was used with a switch in the previous line that changed "Race Absolutely Required" to "Race Absolutely Excluded". This caused the page to correctly display "Race Absolutely Excluded Warforged". ⇒ Some call me Tim (Contribs • Message • Email) 20:31, July 18, 2022 (EDT)