Template talk:3.5e Feat

Templated Feat Category

I am using this so that I can tell the difference between feats that are templated, and those I haven't completed yet. We can delete this category later. --Aarnott 07:54, 29 July 2008 (MDT)

Design choice issues.

Why must the prerequisite string not be empty? Why dump everything into the template -at all-? Especially for feats that are a bit more complex than the standard prerequisite/benefit/special, something that omits that category, or has long and/or complicated writings in any of those three areas. Surgo 17:28, 18 November 2008 (MST)

Good point -- prereqs should be allowed to be blank. The reason to use a template is that you can ensure common formatting is used across all of the feats. Feel free to correct this template if you see errors. --Aarnott 14:13, 21 November 2008 (MST)

Redlink Categories

The 'templated feat' and 'no prereq feat' categories are coming up as redlinks on each page their on. I'm assuming if we wish to keep these the easiest thing to do is to create the base category page and it should auto fill in all the feats. Wanted to check with others before messing with a widely used template.  Hooper   talk    contribs    email   12:07, 23 December 2008 (MST)

No prereq feat will actually be used in the future. The templated feat category is temporary just so I can flag which feats are templated and which are not. --Aarnott 20:57, 23 December 2008 (MST)

added a 3e Benefit property so feats can be tabalized. -- Sleaker 19:10, 26 January 2009 (MST)

realized this was going to be unnecessary, as often people put large amounts of info in the benefits section. To keep it concise I'm just going to use the summary property for creating tables. -- Sleaker 19:14, 26 January 2009 (MST)

As it stands the only way I can see getting the NBoF rating into a table is if it gets added as a property so the ask function can pull the rating. -- Sleaker 19:19, 26 January 2009 (MST)

Template Problem That I don't Know How to Fix

If you look at DnD Halfling Feats, you see that prerequisite feats in that table aren't links, instead they say "Feat Name (DnD Feat)" -- something that doesn't happen when the template is used for regular pages. Does anyone know how to fix this so they become links? Surgo 15:31, 29 April 2009 (MDT)

I'll see what I can do. I won't be able to get to this until tomorrow, however. --Aarnott 09:54, 30 April 2009 (MDT)

It's because when a feat is listed as a prerequisite it uses the page name, so it displays the (DnD Feat), to fix this you'd have to change the prerequisites to link properly, (probably use [[Feat Name (DnD Feat)|Feat Name]] that way it strips the (DnD Feat) out of the feat name. The template isn't the problem, it's how the ask function handles a Row preload. It just isn't robust enough to strip the page names down properly.

EDIT: hmmm.. ok I thought it was a slightly different issue, I'm checking into it.

EDIT2: My next response is, don't try and use the ask function for use with prerequisite feats because the normal ask function code and table rows can't handle it properly? All the other feat tables on the wiki are static.

EDIT3: You can also check 3.5e Aerial Feats on how to use the prerequisite tables with a proper ask function, that one has a little better functionality as far as linked prerequisite feats are concerned.

Figured it out: Okay I'm pretty sure the reason why it's not working is because when the ask function is called it's getting items with main property of 3e Prerequisites. Guess what? that's a Property of type STRING. What this does is convert the text to a.. string. So you wont be able to have Properties of type Page inside of Properties of type String and then run an ask function and still maintain them as Type Page. This results in having the page link code stripped as is the case with what we currently have. There is going to be no fix for this I'm afraid as it looks like a code limitation. The only other option I can think of is to tag the feat as specific to a chain#. and then automatically display it at that indent level, this would let you display the whole prereq line with the normal links inside.

Check out these Links for more info on how to possibly fix it:

http://semantic-mediawiki.org/wiki/Help:Properties_and_types#Properties_with_multiple_types

http://semantic-mediawiki.org/wiki/Help:Many-valued_properties -- Sleaker 16:16, 8 May 2009 (MDT)

Thanks for the research and the help, Sleaker. Surgo 20:17, 8 May 2009 (MDT)

Another template problem

For whatever reason, when you use this template it adds an "edit" link to the page which holds the template... but when you click on that link, it actually opens up the edit dialogue for the template, not the feat. I can't figure out where there's an edit link anywhere, so I can't figure out how to fix it. Any ideas? JazzMan 16:43, 15 May 2011 (MDT)

Issue with Template

Unfortunately, the Template does not allow you to link pre-requisites from SRD Feats. Doing so breaks the template. This seems like something that should have already been included. Jwguy 07:02, 22 January 2012 (MST)

I see why. It automatically appends "_(3.5e Feat)" to the end of whatever feat you enter into the prereq_featX parameter. All of our SRD feats are in the form "SRD:Feat Name", so if you enter an SRD feat it tries to link to "Feat Name (3.5e Feat)" instead of "SRD:Feat Name". Off the top of my head I can't think of an easy way to fix this... Maybe we could have another variable SRD_prereq_featX, but then you'd need a way to support a feat with both SRD and non-SRD prereqs. JazzMan 07:48, 22 January 2012 (MST)

Unwanted Category

I removed the template's code to add the Category:Has Prerequisite Feat because it has never worked, to my knowledge. It adds the category to virtually every feat, regardless of appropriateness. It also cannot recognize SRD or non-D&D Wiki feats without additional parameters even if it worked, and making that work would require combing through 1,400 feats to add those new parameters onto articles. And considering that the category has never been useful to anyone because of this bug, and clearly not useful enough for this issue to be fixed, I don't think the effort to fix the template is worthwhile.--GamerAim (talk) 16:17, 29 August 2018 (MDT)

*insert hearty-eye emoji* BigShotFancyMan (talk) 17:33, 29 August 2018 (MDT)

That category was implemented when SMW was used to organize the feats. It enabled the cascading format for the feats. Since SMW is no longer used on these pages, it was right to remove it. --Green Dragon (talk) 23:28, 29 August 2018 (MDT)

Thanks for clarifying that! I was surprised that no one had ever mentioned it before, and I guess that's why.--GamerAim (talk) 06:33, 30 August 2018 (MDT)