|4 people marked this as a favorite.|
A few remarks on guides for PF2, from a reader's perspective.
1) Stick to the point.
Given how PF2 feats fall into various categories, going through all of them in a class guide is a lot of pointless work. It is better to focus on class feats and only mention ancestral, feat and general feats that are specifically relevant to the class in question.
2) Mention what feats and features do.
When you discuss a feat (or class feature) make sure your reader is on the same page as you. For a guide to be useful to someone who knows the system less well than you (and why would you write a guide, if that is not your intended audience), you need to provide some of that knowledge. You don't need to quote the whole crunch, but at least say what it is for and how it works.
3) Make your reasoning clear.
This connects to the second point. A guide is more useful, if the reader learns something about why options are good, bad or ok. Writing on an option should contain more information than what is already present in the rating. "(red test) this is useless" is just stating the same opinion twice.
4) Give example partial builds and explain combos and interactions.
Doing this will help the reader to see how your reasoning applies to actual character building and to understand how various feats and features work together. Here too, it would be helpful to give more information than just listing the feats/features involved and stating an evaluation.