Talk:Named Ingredient template


 * I created a new template for named ingredients.
 * It's output is similar to other named displays like named weapon / named jewelry. This should help with the transition to a unified template in the future, and bring ingredients in to the fold with the more standardized look.
 * The template allows for an editor to define more than just the quest, or end reward where the item is found.
 * Categories for where the item drops ( not in a chest), where the item can be found in a chest, as a quest end reward, as a quest chain end reward, as a quest series (think 20th completion) end reward, and crafting devies where the item can be created are all distinguished.
 * A user can hover over the row name for a more detailed description of what information the row entails.
 * I've created Item namespace counterparts to the commendation items (ingredients) pages, but have not redirected the original pages to the item namespace page to give everyone a chance to see the difference, and offer ideas for improvement.
 * Please check out the difference between Commendation: War Wizards and Item:Commendation: War Wizards.
 * Let me know what you think shows all commendations using new format,  has links to original format.
 * A user can hover over the row name for a more detailed description of what information the row entails.
 * I've created Item namespace counterparts to the commendation items (ingredients) pages, but have not redirected the original pages to the item namespace page to give everyone a chance to see the difference, and offer ideas for improvement.
 * Please check out the difference between Commendation: War Wizards and Item:Commendation: War Wizards.
 * Let me know what you think shows all commendations using new format,  has links to original format.
 * Please check out the difference between Commendation: War Wizards and Item:Commendation: War Wizards.
 * Let me know what you think shows all commendations using new format,  has links to original format.


 * I like it already.

Cleaner, promotes uniformity, makes it possible to build automatic lists and tables (just a quick-and-dirty one).

Just a couple of issues.

First a minor issue. It might be just me, but every time I read the reward, chainreward and seriesreward field names, I think about the reward I get for trading this ingredient. I suggest, at the very least, changing reward to questreward, in order to reduce this ambiguity (even if sometimes this ingredient is given as a reward for a challenge and not a quest) and to increase the consistency in naming scheme between all three field names.

Then a medium issue. I assume your plan includes some kind of list of ingredient-item associations (that's sort of available in the old format), right? Aldyron (Contributions • Message) 07:17, September 18, 2013 (EDT)


 * On the variable naming, I agree they needed some fine tuning. I've since made some more changes. Template:Named Ingredient refactored and replaced with Template:ItemDisplayIngredient.


 * Variables reward / chainreward / seriesreward changed to simply : quests / chains / series. Editor should be able to deduce that the variables represent locations where items can be obtainted ( "quests" includes challenges and zones ).


 * On calculating the list of crafted items by ingredient, currently what is getting injected in to the item page ( Commendation: Clerics of Amaunator for example ) is the static content on the Page.


 * I plan on having the category pages created dynamically, but from the product, not from the ingredient, so the actual item page would have an "ingredient" variable that could be populated. The ingredient value(s) would dictate the crafted item by ingredient.[ingredient] crafted items categories pages. Once everything is populating properly, an editor may either provide a link to the direct category page "(ingredient name) crafted items", or can use a dynamic created listing of all the pages in the category, which should be real time up to date.


 * ItemDisplayIngredient template has been modified to allow for a ingredient values ( although it may be a bit confusing that an "ingredient" would have an "ingredient" property ). This is to allow for situations where multiple ingredients can be traded for another ( somewhat common in the game ).
 * Joenuts (Contributions • Message) 14:47, September 18, 2013 (EDT)