When it comes to rules, what makes you say "I recognize that the council has made a decision, but given that it's a stupid-ass decision, I've elected to ignore it"?
When it comes to rules, what makes you say "I recognize that the council has made a decision, but given that it's a stupid-ass decision, I've elected to ignore it"?
In other words, what’s an official rule or interaction between different rules in Pathfinder 2e that you think is dumb?
You're viewing a single thread.
I recently handwaved the exact number of in-game days needed to retrain a feat because the player was feeling frustrated and had only used that feat maybe once in the entire campaign
The whole downtime rules seem really weird to me. I like the fact that they exist, in theory, but they're just so different from how I've always played I couldn't see myself use them.
I, and my players, tend to like actually role-playing what their characters do. Not just saying "I'm gonna schmooze" and rolling a die to see the result.
But also, I've never had large amounts of dedicated downtime. I play large campaigns. The PCs have shit to do, and the BBEG isn't gonna wait around for a month while they craft.
The downtime rules seem like they're made for a very old-school type of play where you go out and raid a dungeon and head back to town until you next decide to raid a dungeon, without as much of an overarching plot. And that's just not how I've ever played.
I like PF2's downtime stuff, but I don't like how many activities have a minimum duration of >2 days. In my experience, neither players nor the adventure will tolerate that much time spent not adventuring.
I, and my players, tend to like actually role-playing what their characters do. Not just saying "I'm gonna schmooze" and rolling a die to see the result.
I see people talk about running downtime like this,and exploration like this, too, and I scratch my head.
It's always been pretty clear to me that these sections of the book are for the GM, to give them tools to consistently adjudicate player choices, not to give players a value menu to order from
So, you do your roleplay, the GM sees what you're doing and maps it on to some Activity, and the Activity tells them how to decide how effective you were, mechanically.
Like, if a player ever told me that they were going to "use Avoid Notice", I'd just tilt my head at them and ask them again what their character was doing, and that I'll figure out what that means, mechanically. Because maybe they don't get to Avoid Notice because they've tailed for the last 20 miles by someone they themselves didn't notice.
This was maybe one of the bigger downsides to having both player and GM facing material in the same book, I think.
The way it's presented in the Core Rulebook pretty strongly implies to me that it is meant to be used that way by players. But I agree, regardless of what the designers intended, a better way to do it is for the GM to make a ruling based on the players' descriptive actions.
The problem for me is that actually, even if you do that, the downtime rules aren't very useful. Downtime activities have specific requirements for time spent to count as that activity, usually measured in days. But I've never had a situation where I have multiple days of downtime. My players and I don't say "I want to spend 2 days making money by sneaking into places and robbing them". More normal would be for the rogue to describe themselves sneaking into one specific house and asking what they find. The way they describe what actions they want to do is on the order of something that lasts a couple of minutes at a time. It's just far more fine-grained than the Activities listed in the Downtime section of the CRB is designed for.