Template talk:Skills

We, uh, already have a Template:Skill|skill template ( Deprecated ) which works rather well. Not quite sure what you're going for here... -LrdSlvrhnd 22:41, March 22, 2011 (EDT)
 * And I doubt anyone would want to read that big box of text when they hover over a skill. They are probably more interested if it's competence or enhancement bonus, and click the links if they want to know details. Neouni 00:11, March 23, 2011 (EDT)
 * Yah. Although at least you seem to have un-redlinked most of the text... But yeah.  98% of people know, at least generally speaking, what various skills do.  And the rest can click.  And requiring the +/- is... less than optimal, IMHO.  (We also have a Template:-Skill|neg skill template]] ...)   This isn't to say I don't appreciate the work you're doing - 'cause I do, and lord knows I'd absolutely fail at any attempt myself - but spending time building stuff we already have seems a waste to me.  The Sneak Attack template, good use of time.  This, notsomuch. -LrdSlvrhnd 00:20, March 23, 2011 (EDT)

The problem with the Template:Skill ( Deprecated ) that you reference is that it only covers Heal, Tumble, Jump, and Repair.. If you wish to re-locate Template:skills to Template:skill ( Deprecated ), be my guest.. I happen to like it's more descriptive condition however.. --Technical_13-- ShoeMaker 15:10, March 23, 2011 (EDT)


 * Hmm, let's see. skill|Heal|1 ( Deprecated )  Yep, that works like you said.  Let's try another!  skill|Disable Device|1 ( Deprecated ) Gosh, look at that, it works!  Howzabout skill|Use Magical Device|1 ( Deprecated )... yep, that works.  Let's go useless... skill|Swim|1 ( Deprecated ).  Yep, even works for the basically useless skills.  Basically, what I'm asking here is, where the heck did you get "it only covers Heal, Tumble, Jump and Repair" from?  It works on EVERY skill that I've ever tried, and I've templated a lot of items.  Yes, it's more descriptive... but we don't really NEED more descriptive there.  And if somebody *wants* (or even needs) more descriptive, they can click and read up on it.  IMHO, the enhancement tooltips should either say exactly (or nearly, at least) what the blurb in the item says, or summarize the effects (preferably the former).  Not add a whole bunch of extra text. -LrdSlvrhnd 16:00, March 23, 2011 (EDT)

That is the contents of Template:skill ( Deprecated ) --  I only see Heal, Tumble, Jump, Repair listed....  So that is where I got that from..... So, if I understand you right  is a great skill to have on an item??? Where are the limits?? Where is the ability to catch typo's and let the editor know about it? Some people don't want to have to click and navigate away from the page they are on to see a brief descriptor of a skill or stat... There are some pages I don't want to have to navigate away from to get a refresher on what a skill that I'm not familiar with does. Personally, I'd rather have the extra information there and just not read it then want the info and not have it.. --Technical_13-- ShoeMaker 19:10, March 23, 2011 (EDT)


 * Those are exceptions for refering to a page, because those are Disambiguations or something.
 * But you would have know if you could actually read the code instead of copy paste bits.
 * Try reading Template:Item ;) Neouni 19:18, March 23, 2011 (EDT)

Remove categorization

 * Agree. Templates with built in category used in other category spills over to unrelated pages. Happens alot when the entire item description are written out using the offending templates. Found this out a few days ago with u14 raid items. I just plan to remove those line from the template. I know keen, shatter, parrying, skills are some of the offending templates any others? Just curious where would this page be at? "(like there has been the policy in the past)" want to see what else it says. Bladedge (Contributions &bull; Message) 19:03, December 22, 2012 (EST)


 * Yeah, that problem will be fixed when I complete the Talk:Item Namespace project. Until then, it needs to stay as it is or everyone will complain the items aren't in the categories that they should be.  It's a catch 22 that only completing the previously mentioned project should properly fix.

ShoeMaker (Contributions • ) 20:32, December 22, 2012 (EST)


 * Would it not be better to fix badly working and badly used templates than come up with a new system that has problems of its own that also does NOT fix the original category bleed from templates. BlackSmith (Contributions &bull; Message) 16:31, December 25, 2012 (EST)


 * No, I do not believe it would be better to have to manually go through EVERY item on the wiki and manually categorize it into EVERY group it belongs in... Not only would that take just as long if not longer than moving everything to the Item: namespace, it would fail because of capitalization, spelling, spacing, punctuation, and differences in naming conventions... Also, it would defeat the ENTIRE purpose of the wiki template in the first place, which is to do repetitive tasks like formatting and categorization automatically and uniformly.

ShoeMaker (Contributions • ) 19:58, December 25, 2012 (EST)


 * You did beat me to the rollback, was waiting for the change to go through the entire wiki to give it a sort of jump start, it did clear some of the issues like it did with parrying. Bladedge (Contributions &bull; Message) 20:53, December 22, 2012 (EST)

Typo
Bouns -> Bonus Aldyron (Contributions • Message) 16:04, October 24, 2013 (EDT)