Game mechanicsNewbie guideIn developmentDDO StoreSocial Media


ChallengesClassesCollectablesCraftingEnhancementsEpic DestiniesFavorFeats

GlossaryItemsMapsMonstersPlacesQuestsRacesReincarnationSkillsSpells


Please create an account or log in to build a reputation and unlock more editing privileges, and then visit DDO wiki's IRC Chat/Discord if you need any help!

Template talk:Named Item

From DDO wiki
Jump to: navigation, search

Notes[edit]

I have made this section of the talk page expecting some revisions to take more than the allotted "summary" space to detail.

  • Revision History
    • 03:03, May 26, 2011 ( 6,385 bytes) ShoeMaker (talk | contribs)
      • Basic universal components addressed and table form uploaded.
    • 13:55, May 26, 2011 ( +596 bytes) ShoeMaker (talk | contribs)
      • Working on craft(ing/able/ed) related sections.
        • Other than stripping the word "Epic" from the "Epic Version of" automatic completion row -- I have temporarily allowed for {{{craft name}}} to fill that spot, epic component should be completed.
        • Other than stripping the word "(unsuppressed)" from the "Unsuppressed from" automatic completion row -- I have temporarily allowed for {{{craft name}}} to fill that spot, (un)suppressed component should be completed.
        • Sora Katra and Unraveling Enchantments have place holders, and I have started figuring them out.
        • Considering creating a {{greensteel recipe|taper|oil/balm...|ore/filament..}} template and adding greensteel blanks to the template.
    • 17:02, May 26, 2011 ( +4,752 bytes) ShoeMaker (talk | contribs)
      • Added prototype /* USAGE */ and /* Examples */ sections.
      • Crafting sections are mostly done. May find a few minor tweeks as I continue. Still contemplating "greensteel" usage/need.
      • With the feature of making rows and features (not) appear, setting up the number of rows for the images is being worked on in my head.. I'm wanting to count the rows of text, and not the actual rows of the table.. This way I'm not stretching out any rows. I never liked much how the current "Named" templates stretched out an empty "Notes" section.
        • Neouni 23:25, May 26, 2011 (EDT)
          • Try using something like: {{#vardefine:rowcounter|{{#expr:1+{{#var:rowcounter}}}}}}
            at each of the lines that you are adding to the table.

some comments[edit]

I guess this requires more work. Here's some stuff that should appear here:

  • cosmetic items, cosmetic slots
  • multi-slot items like Chains

Good luck :) --Cru121 (ContribsMessage) 04:14, October 21, 2016 (EDT)

Clicky line?[edit]

Hello. I want to see a whole-sight page about Clickies, but when I try a thing such as {{ Named items category | category = Clicky items }} for Clicky items, It comes out none of the items. I realized It's because they in the Category page are all subpages of clickies. So, I'd like to ask if we can have something like << | clicky = Yes >> line to add a category option(Clicky type item) then It'll be cooler. By the way... will it result to change Clicky items to Clicky spells as the factor(Clicky = Yes) leads an item to Category:Clicky items? -- Targal (ContribsMessage) 13:35, October 3, 2019 (EDT)

Appearance[edit]

Hey everyone! As you may know, I've been working on trying to get this project completed on the DDOwiki Talk livestream on DDOstream on Twitch.tv the last few sessions, and I'm looking for feedback on appearance and functionality. I've added some ability like the ability to have multiple drop locations so we'll finally be able to list an item as dropping in multiple quests and list it as an end reward for a chain without abusing parameters. I've also added the ability to have multiple images which works well for docents to show how it looks on a WF and how it looks on an Iron Defender or to show Tiers of a tiered item. Do you have any ideas for things you'd like to see added or perfected, so we can get this template live? Things already on my to-do list for it are:

  • Change the |slot= to |type= and have the template automatically assume slot, race restrictions, etc.
  • Currently multiple pictures have picdesc default shown and the rest default collapsed, I'd like to add some logic to be able to override that and pick which image(s) to hide/show by default on a per item basis
  • Change the enhancements bulk section that looks for a bullet list to use individual |enhancement ##= parameters, so we can have more control over categorization and input - it'll also be helpful for a future stage of this project I have planned of a WYSIWYG style editor for items as a gadget. 👟 ShoeMaker (Contribs • Message) 👟 17:34, October 9, 2019 (EDT)
    • Hi, coming late to the party, so I have some simple questions and am not sure of the goal. It appears the named item templates are being combined into one, all-use, master template, yes? The benefits of this would be what? The One Template, to rule them all, I suppose? I am not currently entering Items all that frequently, unlike Cru121 who is like a master artificer with all of that. But speaking from a position of new wiki editors, the massiveness of it would be daunting. Deleting whole sections would not be something I would expect people to do, since the fear factor of screwing things up runs strongly. I like the idea of a universal template, but wonder if this has combined so many things that it prevents people from walking through it? Just my 2 cents. meander (ContribsMessage) 14:00, October 10, 2019 (EDT)
      • The reasons for this are multipart.
        1. Combining all of the "Named thing" templates into one gives consistency in parameter naming
        2. Combining all of the "Named thing" templates removes the middle-man step of passing everything through an intermediate {{Named item}} template in order for categorization and DPL queries to work properly.
        3. Combining all of the "Named thing" templates gives us an opportunity to fix issues we have with individual templates once and not have to copy and paste fixes to 8 different templates by slot.
        4. Combining all of the "Named thing" templates allows us to redo the formatting/look of the pages to accommodate tiered items and items with multiple drop locations better.
        5. Allows me to create a WYSIWYG JavaScript gadget editor/page creator for items to make it easier for editors to change/add item pages.
      These are just some of the goals/benefits.  👟 ShoeMaker (Contribs • Message) 👟 18:55, October 15, 2019 (EDT)
  • So I have not followed your development, but are there any sandbox examples (item pages) where I can see the new template in action? Cru121 (ContribsMessage) 03:35, October 11, 2019 (EDT)
    • Just these. Feel free to play with the parameters.  👟 ShoeMaker (Contribs • Message) 👟 18:47, October 15, 2019 (EDT)

────────────────────────────────────────────────────────────────────────────────────────────────────

  • Two quick comments:
    1. Is it intentional that the icon in the top row is a bit above the heading? I'd probably keep icon and heading in one line.
      • No, not intentional, and I have done some work on getting them in line and will do some more. It's a byproduct of not wanting the image in the header itself to prevent breaking section links. DDOstream (ContribsMessage) 09:16, October 16, 2019 (EDT) EDIT: I think this has been resolved - although I haven't checked on multiple screen sizes. DDOstream (ContribsMessage) 09:38, October 16, 2019 (EDT)
    2. A more serious suggestion: I think we should attempt to add a bit of responsive design. The big table could be separated into two standalone tables (one for parameters, one for pics), with display: inline-table. On narrow screens, the second table would jump below the first. Something like what we have here: Physical_Resistance_Rating#Sources_of_PRR. -- Cru121 (ContribsMessage) 07:00, October 16, 2019 (EDT)
      • I don't like the idea of separate standalone tables because it'll disrupt symmetry on the page, but I do like the idea of the images shifting down on smaller screens. I'll work on that. DDOstream (ContribsMessage) 09:16, October 16, 2019 (EDT)

So I tried to slap Sword of Shadow stats to {{Named_Item/Weapon}}

  • proficiency does not show up (maybe only used for categories?).
  • Equips to / |slot: should this be Weapon? or Main hand, as displayed on weapon? Using Main hand breaks some stuff.
  • Minimum Level does not show up
  • critical threat does not show up
  • no parameter for crit multiplier?

General comments / my personal preferences

  • Too much text centering for my taste.
  • I would prefer if we used sentence case rather than title case, but if we're using title case, also use it for "Description window".
  • I don't like how the left part gets expanded / collapsed when a large pic is expanded/collapsed on the right side. Imho the line/cell height in the left part should not change.
  • Left part should perhaps have a minimum width. maybe 400-500px?
  • Right part I think I'd like better if it aligned to the top?

-- Cru121 (ContribsMessage) 10:20, October 17, 2019 (EDT)

  • Responses:
    • Proficiency has been fixed. It was looking for |proficiency= instead of |proficiency requirement=. I don't think it currently does anything with |race requirement=, |class requirement=, |feat requirement=, or |alignment requirement= either - and those should be added/used.
    • |slot= <!-- *REQUIRED* bracers, ...snip..., helm, weapon, ammunition, ...snip..., or quiver --> -- should be weapon, for now. That parameter will probably go away once I finish the |specific type= auto-detection that will set slot and some requirements automatically.
    • |minimum level= has been fixed, there were some mismatched braces
    • Apparently none of the X-type specific sections have been added yet for weapons, shields, runearms, etc. Those will be added once the more complex logic sections are done - thank you for reminding me though as I had forgotten them.
    • Parameter |critical threat multiplier= has been added for weapons
    • We can get rid of centering and use some padding instead
    • Fixed on "Description Window" - which is a customizable field using the |picdesc description= parameter
    • I very specifically like the growing and shrinking in all rows instead of just the one "notes" row like it is now. The only compromise I'd be able to live with would be to set the screenshot box to be a static height with an overflow and scrollbar. I don't like when an image is expanded and causes all the text to shoot off the screen. Thoughts about how to make this work for everyone?
    • I need to set min/max widths for both left and right sides I can see - I'll work on that
    • top/middle/bottom alignment shouldn't really matter except when everything is collapsed. Can happily change it to top.
Anything else? Cool Face DDOstream (ContribsMessage) 10:03, October 23, 2019 (EDT)

@anything else: Expanding Cosmetic Appearance behaves badly, portion of the image is displayed off-screen, even on very wide screens. -- Cru121 (ContribsMessage) 07:57, November 4, 2019 (EST)

Wand[edit]

I have slapped some parameters to Template:Named Item/Wand. I noticed that T:Bind does not have an option for Destroyed on Leaving Adventure. Also, while the template does contains parameters defining the associated spell effect, and I provided those parameters, the effect is not listed anywhere. Also, not sure if we need to have another option related to location. This item does not come from chest, end reward, or turnin; it's an in-quest item that an NPC gives to you. -- Cru121 (ContribsMessage) 08:13, November 4, 2019 (EST)

  • {{ Bind | No | drops=leaving }} for Unbound, Drops on leaving adventureIcon tooltip.pngUnbound: This item is Unbound, and may take permanent damage.
    This item drops on leaving adventure
    is the closest you'll get for that. I can add "quest item" as an alternative for turnin/reward/chest.  👟 ShoeMaker (Contribs • Message) 👟 17:07, November 4, 2019 (EST)