Talk:4e Paragon Tier Feats

Want to help, but unsure how

What specifically is the correct templating/formatting for these feats? If someone can link me to an example that I can follow, I should be able to correct these in a jiffy. - MisterSinister 20:24, 19 June 2011 (UTC)

The categories on these have all been updated already, so the templates should be updated as well. The big things that needed to be done were: category fixing (just feat, not paragon feat or whatever), keyword fixing (|keyword(n)= was being moved to |keywords= as a comma separated list) - see Category:Keywords Parameter Refactor Needed for 4e feats with this problem still, and breadcrumb updating. I think... been a bit since I was really focused on these. You might want to check out that category to see which powers still need keyword work done, since those likely need other stuff done as well. And then just compare to the preload, and update as looks appropriate. - Tarkisflux ^Talk 21:28, 19 June 2011 (UTC)

Sure, I'll get onto it ASAP. Probably after I go to the gym, since I'll have a few hours before work. - MisterSinister 21:33, 19 June 2011 (UTC)

And done! At least all the ones in the list you gave me. I'll check the feats listed on this page for any issues too, and post when done.

Proper Breadcrumbing of Feats

Should feats be breadcrumbed by type, by class, by tier, by some combination of the above, or by none of the above? I've seen a mixture of all of these, and wanted to know which was best before proceeding. - MisterSinister 05:12, 20 June 2011 (UTC)

Issues with Keyword Parameter Refactoring

The following page appears to be having issues parsing the new format: Chosen Rider, Drow Judicator, Spiderbound. There may be more - I'll add them as I find them. Additionally, there are parameter issues with the following: Zephyr's Song. - MisterSinister 02:34, 20 June 2011 (UTC)

There are quite a bit...I'm not sure how to fix it. --Havvy 02:58, 20 June 2011 (UTC)

How were they parsed under the old format? Potentially, the same answer can be applied here, but since I only understand the front-end interface, I'm not even sure how to begin to fix them. - MisterSinister 04:32, 20 June 2011 (UTC)

They were <no