Discussion: Protection Paladins Feedback in Wrath of the Lich King Beta (Sept. 4th)

This is your chance Paladins. For all things paladin and tanking, you should read this thread and keep on it. For those of you in the Beta, by all means start posting feedback; it’s the only way this kind of stuff will change or be addressed in any way.

We are about ready to do our next major pass on the Paladin trees.

We think Prot does have too many mandatory talents, and too many talents that offer passive mitigation without other interesting mechanics or even dps. This thread is a great opportunity to discuss the tree and offer your feedback.

For purposes of this thread, the kinds of feedback that are useful:
– Which talents are fun vs. which ones aren’t
– Areas in the tree that tie up too many talent points vs. areas that feel barren
– Talents that feel mandatory vs. talents that feel fun but optional vs. talents you’d never get

For purposes of this thread, we are less interested in:
– Mitigation and threat capabilities of the paladin vs. other tanks (we’ll get to that)
– Holy and Retribution (we’ll get to that)
– Mana, dps, interrupts or other paladin issues (we’ll get to that)
– Whether it’s a good goal for Prot to be viable at healing, dps or PvP. (It’s helpful to mention when talents might fit these roles, but let’s not use this particular thread for a debate on whether Prot should be at all decent in PvP.)
– Questions about other topics, pleas to visit other forums or catty arguments

Rest assured this is not our only avenue for collecting feedback. We do talk to experienced and beginner tanks alike as well as drawing on our own internal resources to make decisions.

Ready, Set, Go! (src)

Share and Enjoy:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • Fark
  • NewsVine
  • Reddit
  • Slashdot
  • StumbleUpon
  • Technorati

Leave a Reply

You can use these XHTML tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>