| Full Name |
Fenris Wolfe |
| Race |
Large Canine |
| Classes/Levels |
Level 3 druid |
| Gender |
M |
| Size |
L |
| Age |
Old |
| Special Abilities |
Improved grab |
| Alignment |
CG |
| Deity |
da trees |
| Location |
the woods |
| Languages |
English, french |
| Occupation |
Forestry, GIS |
| Strength |
14 |
| Dexterity |
8 |
| Constitution |
16 |
| Intelligence |
14 |
| Wisdom |
12 |
| Charisma |
6 |
About BigNorseWolf
the flat rolling surfaces map
Druids log animal companions
Flutters guide for newbies
Branching out: Playing PFS online introductory beginners guide and simple macros to get started.
The absolute worst way to read the rules is like a logic problem: A implies B which Implies C which Implied D. In a perfectly coherent system a perfect logician can draw implications like that. Pathfinder is not that system *and as much as they hate to admit it, most gamers are not that logician)
Reading the rules so that one piece, one way, means that if you misunderstand something, or that wording was at all unclear, then you can't see other readings of the same words or other pieced of evidence pointing to another position. RAW is not limited to tiny myopic chunks, the other rules are there for a reason too.
A far better way to read rules is to consider the quality and quantity of evidence for and against a position. If you think a bit of rules text is absolutely written a certain way by all means consider "this rule is written this way" as evidence for a position, but not proof.
Evidence for----->
<----Evidence against
Evidence for-------------->
<-------Evidence against
This helps prevent you from derping on a reading, or if the author derped on one word choice.
