User talk:Joenuts

Archive 2013

ItemDisplay templates

 * Proposed exceptions ( see below )
 * Item pages to have common look, different color pattern. That's the plan.
 * Item page display / image expansion of table etc ( see below )
 * I like the idea of displaying location of vendor on item page. I think this can be done dynamically with DPL data. Challenge accepted.
 * Damage type listed vertically, that was a mistake on my part, meant to be comma seperated list. Fixable.
 * Freeform text in effects ( enchantments ) field. This is a tough one. I'll have to come back to that one.
 * Freeform text in chests / quests / chains / series fields. Makes sense, I'll work on something to allow for that.

Proposed item namespace exceptions

 * Bladedge, I certainly agree that generic information pages like what you mentioned ( Clothing, Jewelry, Weapons, Shields, Armor ) have no place in the item namespace.
 * There is no item named "Clothing" that can be placed in to inventory, that page is more of a description of what defines clothing. If anything, that page should be transcluded on to the clothing category page.
 * By "Individual potions", I assume you mean non named potions ( potion of clw, potion of mage armor, etc )
 * "Consumable pages" is a bit different, as many different item types can be consumable like potions / wands / scrolls / trinkets ( think scarab of spell absorption ).
 * So, for "Consumable pages", I assume you mean "Non named" : components, Food and drinks, Hireling contracts, potions, scrolls, tomes, tools and wands.
 * I don't want to misstate your position, would the following exception cover everything that you DONT think deserves a page in item namespace?


 * Generic ( Non Named ) items that exist in game in the following categories shall NOT have individual pages exist for each instance
 * Components, Food and Drinks, Hireling Contracts, Potions, Scrolls, Tomes, Tools, and Wands
 * If that is your position, can you give me some insight as to what problems may exist if an attempt is made to create pages for every item?
 * You mention "It's been done, and it does not work". Does that mean that it's too time consuming to manage? Do properties change too frequently for the information to be useful? etc.

Item page display layout

 * I'm unable to find discussion for LDS.
 * Eternal Flask definitely needs overhaul.
 * Agile Belt, Eternal Flask, even Epic Antique Greataxe page have layout ... hiccups.
 * The core of the problem is that images will sometimes be larger than the rows of data, and sometimes they will be smaller.
 * The question is "How to properly handle the extra whitespace when one column is not tall enough to match the opposing column"
 * On a page like Sword of Shadow, whitespace is handled two different ways.
 * The shown image is configured to span 20 rows, and be centered, leaving an even amount of whitespace above and below, and spanning 20 rows
 * The item detail image is on the single row with the tips details, which causes tips details to have whitespace above and below
 * This approach gives ( what I consider ) extra whitespace both in the picture column, AND in the item details column
 * Also, it does not lend itself to dynamic rows in the item details column ( adding or removing rows in the detail would change layout properties )
 * A different approach ( preferred ) would be to un marry the right ( image ) column from the left ( details ) column.
 * One way to handle this is to have the item details in their own table, the image(s) in their own table, all inside a master table
 * Then you can control how whitespace is handled independently of either side.
 * I created this example page User:Joenuts/Item Display Examples to show a different approach of how whitespace can be handled. ( forget about color pattern, that was just chosen to give an idea of where table and cells begin and end )
 * My preference is to have extra whitespace underneath the item details because I feel that you get more useful information in to a smaller footprint, so that's the direction i've been going.
 * It would be awesome to have whitespace and layout decisions handled by the skin, but that's a LONG ways away.
 * I believe that's what you're talking about when you mention "columns dont go all the way down", that's expected behaviour. Considering what I have explained, is it your preference that item details column be even with item images column?

You've been nominated for clown of the year!
Hey Joe, I've nominated you for clown of the year should you choose to accept! ShoeMaker (Contributions • Message) 17:39, January 2, 2014 (EST)

Lore Legacy Items

 * Solution : All pages that use the new Lore template will need to have image updated, and ultimately the page updated to use spelllore template with correct details. ( see : http://ddowiki.com/page/Special:WhatLinksHere/Template:Lore )
 * Once no pages reference that template, it can be deprecated, the created categories should have no pages so they can get deleted, etc.
 * In the current time, I think the broken links were very unsightly, and now even though information is a bit dated, it's not broken looking.
 * Joenuts (Contributions • &uArr; top &uArr;) 16:17, January 3, 2014 (EST)
 * If an indicator is required to notify viewers that information is out dated, perhaps I can add the Template:Update tag to each of those pages, and also modify the Template:Lore to show a tag that the that line of information needs to be updated. What do you think about that?
 * Joenuts (Contributions • &uArr; top &uArr;) 16:26, January 3, 2014 (EST)


 * If the pic needs to be updated, wouldnt the tag be preferred?
 * How is a visitor to know that the page requires a picture update if the only indicator is that the page is in a hidden category ( was very difficult for me to find, category doesnt even show up when i search for "info-box pic" )
 * I didnt realize that the only thing those pages needed was to correct the order of the parameters ( simple fix ), and the reason they were left out of order was to indicate that the picture needed to be updated ( another, simple fix ).
 * I'll update pages accordingly, adding them to the hidden "pic needed" category, although my opinion is that if the page picture is out of date, that warrants the update tag for the page.
 * Perhaps you could explain to me what exactly was wrong with the update I did on the iconic starter gear?
 * Joenuts (Contributions • &uArr; top &uArr;) 17:10, January 3, 2014 (EST)


 * I've started a centralized discussion for this topic so it will be easier to discuss on Talk:Spelllore templates and updating usage. Thanks ShoeMaker (Contributions • Message) 17:25, January 3, 2014 (EST)


 * I consider "rewards" loosely items that can be selected from an NPC as rewards for some completion ( quest / chain / 3rd series 20th series ). And with the advent of a category getting created for starter gear (not my choice, there were two already created ), I thought it fit more in the [starter] rewards than [starter] loot ( which I consider loot to be items pulled from chests ).
 * There was no existing distinction of one iconic's gear versus another iconic's gear as far as the categories went.
 * All I did was update all the pages that were putting the items in to [starter] loot, and update them to put in [starter] rewards.
 * I'm sorry you feel that me consolidating the categories for common gear is "messing with changes you've been working on for the last 5 months', I just want to clean up all the broken parts of the wiki now that I have some more time available to do so.
 * If you have an idea of how the starter gear categories should be structured, I'm all for that, I'm not a fan of lumping them in to rewards. Something like Item groups->Iconic Starter items-> ( Purple Dragon Knight starter items / Sun Elf starter items / Shadar-kai starter items ) would make sense to me.
 * If you're on board with that, then removing the quest "Advance to level 15" from the page and maybe manually adding the categories until the template can be modified to compensate may need to happen.
 * Let me know what you think about that.
 * Joenuts (Contributions • &uArr; top &uArr;) 17:40, January 3, 2014 (EST)


 * Kobold think everyone need to smile and give kobold all you shiny! Kobold worker (Contributions • Message) 15:53, January 11, 2014 (EST)

Armor template

 * No big deal on the feedback, I figured you had other stuff going on.
 * Concerning the most recent armor creations (within the last 2 hours), I've noticed there is a lag behind when some pages get updated on the wiki, and what gets pushed down to the end user.
 * I suspect the caching engine used by ddowiki causes a delay in getting the latest code out consistently. ( I think Shoe may have been running in to similar problems when updating mediawiki js pages )
 * The reason the armor pages show blank is because it's relying on css set on the main page that I dont believe is getting pushed out just yet. Give it a couple hours then check again.
 * I admit, I wouldnt like that blank look either!!
 * It should more like Item:Shards of Light and Item:Small Candle, but with a tan color pattern for armor.
 * I tried to make each data stored match where it appears in the image, which is why description shows above value/weight, and custom information below all provided information.
 * ( vendors / chests / quests / etc ) below actual.
 * Moving the data around is real easy on the template. I'll relocate description to be lower (maybe right above notes?).
 * Similarly, flipping the image is easy to do. I posted requesting comments on appearance on the help desk ( see Item display templates / display modification - rfc ) can't figure out how to link it.
 * It seemed like the preference was detail image above in game shown image, so I left it at that.
 * Joenuts (Contributions • &uArr; top &uArr;) 17:05, January 27, 2014 (EST)
 * Similarly, flipping the image is easy to do. I posted requesting comments on appearance on the help desk ( see Item display templates / display modification - rfc ) can't figure out how to link it.
 * It seemed like the preference was detail image above in game shown image, so I left it at that.
 * Joenuts (Contributions • &uArr; top &uArr;) 17:05, January 27, 2014 (EST)
 * Joenuts (Contributions • &uArr; top &uArr;) 17:05, January 27, 2014 (EST)