Template talk:Weapon enchantment

Is it possible that once the Item:Namespace move is complete, this template could be made to auto-populate the "found on" field? That's a really useful thing, to be able to see all the items the enchantement is available on, and it seems like it should be workable if we are making all the weapon enchantments into templates for use on the items. The details of how to implement that are a bit beyond me, though. Or is this already one of the goals of the Item Namespace project? Nibor (Contributions • Message) 18:30, August 2, 2012 (EDT)

I'm sorry it took so long to respond Nibor, I had missed your question before now. I think it may be possible using <ncl> tags.

ShoeMaker (Contributions • Message) 08:22, December 29, 2012 (EST)

Add required trait

Would it be possible to add required trait and umd bypass optional fields to this template? For all those pure good, absolute law, supreme evil, the rebel, and similar enchantments. --Cru121 (Contributions • Message) 04:22, December 29, 2012 (EST)

Of course, anything is possible if minds are set to it. It will take some fine coding to accomplish what you want. You'll want it to show up when you actively use the arguments |required= and |umd= but not show up at all if you don't. If you are asking if myself or one of our other template gurus can whip this up, I'm a little busy at the moment, so it wouldn't be right away. Spring semester of classes are just starting up and I'm looking for a new job. Probably with-in a month I can implement this if no-one beats me to it.

ShoeMaker (Contributions • Message) 08:22, December 29, 2012 (EST)

I have added something, I think it breaks nothing, it was a long birth. I'd still like a space between req.trait and "(UMD:)" but that's beyond my skill. Check e.g. Destroyer. --Cru121 (Contributions • Message) 00:43, December 31, 2012 (EST)

Right idea Cru121, just needed to take it a little further. To get the space you wanted, simply code it in using the non-breaking space html entity (&nbsp;). I nested the #if: and #ifeq: for UMD inside of the nested ones for required because if there is no required trait, then there is no UMD to bypass it.

ShoeMaker (Contributions • Message) 09:50, December 31, 2012 (EST)

Which template

There are two templates that are currently doing the same functions Template:Weapon enchantment and Template:Weapon enhancement. Which is the correct one for the other can be can be depreciated. Bladedge (Contributions • Message) 19:06, May 28, 2013 (EDT)

I vote for enchantment, because that's what items have (enchantments). Enhancements are what you spend your action points on.

--Cru121 (Contributions • Message) 00:54, May 29, 2013 (EDT)

Nothing else links to old template. What now? Delete the Template:Weapon enhancement?

--Cru121 (Contributions • Message) 23:34, June 20, 2013 (EDT)

Nope. Deprecate it. Template:Deprecated should work for that as well. Put the template at the top of the page and then put the code to pass the variables from anything that uses the old template to the new one inside of includeonly tags. Check out any one of the other deprecated templates to see how. ShoeMaker (Contributions • Message) 07:39, June 21, 2013 (EDT)

Category/Type Code not functioning

The code which handles the Category and/or type is not functioning. All pages using this template are being place in the Uncategorized pages section. Bladedge (Contributions • Message) 01:16, June 11, 2013 (EDT)

I'll look into it when I have a moment... ShoeMaker (Contributions • Message) 14:42, June 11, 2013 (EDT)

I've added some category code. There's also some other category code there, not sure what that does. --Cru121 (Contributions • Message) 23:36, June 20, 2013 (EDT)

removing heading

Removing heading breaks pages like Elemental (weapon). Is this final design, name parameter useless? I don't care either way, just asking if I can start fixing the pages or is this unintended?--Cru121 (Contributions • Message) 14:19, June 18, 2013 (EDT)

I had to take a break for Sociology class... I'll revert my work for now, and pick it back up later... I need to put more thought into it. ShoeMaker (Contributions • Message) 14:56, June 18, 2013 (EDT)

Is it possible to use a template to determine if we're at the very beginning of an article? Because the title should be hidden in these circumstances: PAGENAME = name_parameter AND we're on article start. First condition is probably easy, the second one... I don't know if it's possible at all. --Cru121 (Contributions • Message) 12:48, June 21, 2013 (EDT)

• It can be tested to see if {{{name}}} = {{PAGENAME}} (simply put, there would have to be case desensitization and formatting stripping, because it should think that "BOLD PAGENAME" = "pagename". I'm curious as to why it would matter about it being at the top/start... ShoeMaker (Contributions • Message) 19:01, June 23, 2013 (EDT)
• The second condition would also work for pages like Heartseeker#Heartseeker. However, we can also not bother with this and simply not use the name parameter in the cases when we don't want to display the heading.
  • Yeah, I suppose... The only way to handle that is to add another parameter for those rare cases... Something like |top=false ShoeMaker (Contributions • Message) 08:01, June 24, 2013 (EDT)

sub - then should

• make a note. Communication is the key to teamwork. :P --Uurlock (Contribs • Message • Email) 18:12, September 26, 2016 (EDT)