Talk:Refactored Armor template is in!!

Check out User:Joenuts/Armor_refactor

I attempted to keep the appearance changes as minimal as possible, but still bringing in line the overall "item" pages design.

Fields that are not populated / dont apply to the item are not displayed.

Data displayed is listed in the order it appears in the item.

Bladedge has commented that the description is best displayed lower because larger descriptions cause more important information to get shifted down too far, so description may be moving down somewhere in the overall display ( maybe below value and weight? ).

The details image and in game shown image have been flipped. Both SysteRn and I feel that details image should be above in game shown image, Bladedge feels that shown image should be above. I'd like to get some more comment/votes on this.

Now for the technical aspect changes :

Original template stored "type" (chainmail / leather / breastplate etc ) and "feat" ( light / medium / heavy ). The "type" variable has been repurposed to store the value listed in the game underneath armor title ( Cloth / Light / Medium / Heavy / Docent ).

This variable is used to determine what category the armor gets placed in to, and what proficiency requirements show on the armor. Since Cloth and Docent do not show any required proficiencies, there is no equivalent line for those types.

Armor bonus should be entered for non docent armor only. For Docent armor, adamantine body and mithril body values should be entered. ( I could not find a way in game to display docent composite plating values, is this something that got removed, or is there some special requirement? )

Location field has been removed, and chests, quests, chains, series, and vendors have been added. Each of these fields can be populated with multiple values, seperated by semicolons. Also, for each element in the semicolon separated list anything after a slash will be treated as a comment. The template will handle category injection properly for items that are found in chests (chests) vs items that are selected as rewards (quests) vs items that are available to be selected on 3rd or 20th reward (series) vs items that can be selected upon completion of a series of quests (series).

Enchantments field has been modified to expect the values in a list format ( same as above ). The ability to put formatted information in is lost, but what is gained is the ability to create readable, single line lists of items that display useful information including item enchantments ( all dynamic info, as the item info changes, no need to update pages that reference the details). See or User:Joenuts/Armor_refactor for very basic examples of what can be done dynamically when the data is stored in a structured format.

If anyone has any ideas or concerns about me moving forward to get this new functionality, I'd like to make sure everything is covered when it comes to making this transition.

Joenuts (Contributions • Message) 20:42, January 27, 2014 (EST)


 * Nice work. I like the new visual, and the automated loot table update is a nice function.

I agree with Bladeedge that description should be on the bottom row. Some items have REALLY long descriptions. Or we can switch the Location field to the top, since it is one of the most important info people want when checking a specific item.

Docent composite value got dropped from the docent description some updated ago, not sure when.

I also think the armor image should be on top, with the item box on the bottom. We already have the enchantments visible on the left column, no need to see the exact same info in paralel on the right column. The item infobox pic is more a "confirmation" thing than an "information" thing. Nibelung (Contributions • Message) 08:37, January 28, 2014 (EST)


 * Would it be possible for screen width 1600 pixels or more to place the pics in the same line?

--Cru121 (Contributions • Message) 09:03, January 28, 2014 (EST)