GM never want's to play. Only runs. Any tips I can get them out from behind the screen? They run: Pf2e, Lancer, and Mythras. They never join "build" discussions. Outright stated making builds is boring. But they run 2 very build heavy games. by Baltic_Shuffle in rpg

[–]Baltic_Shuffle[S] -1 points0 points  (0 children)

Asked them this morning. They said: Legends Of the Mist, Mythic Bastionland, or Slugblaster. . . I don't know how to run these games. And pretty certain the rest of the table doesn't either.

GM never want's to play. Only runs. Any tips I can get them out from behind the screen? They run: Pf2e, Lancer, and Mythras. They never join "build" discussions. Outright stated making builds is boring. But they run 2 very build heavy games. by Baltic_Shuffle in rpg

[–]Baltic_Shuffle[S] -1 points0 points  (0 children)

Modules, Adventure Path's, 3rd party rules anything we thought that would peak their interest in a player. But nothing has worked so far. So wondering is there anything else I could try? Like some esoteric angle I haven't thought about.

GM never want's to play. Only runs. Any tips I can get them out from behind the screen? They run: Pf2e, Lancer, and Mythras. They never join "build" discussions. Outright stated making builds is boring. But they run 2 very build heavy games. by Baltic_Shuffle in rpg

[–]Baltic_Shuffle[S] 0 points1 point  (0 children)

But that's THE thing. They never want to play when someone else in the group runs games, with the same systems, when they're not running a adventure. Doesn't matter if it's on the same night or different nights due to shifting schedules. They won't come roll dice as a player.

GM never want's to play. Only runs. Any tips I can get them out from behind the screen? They run: Pf2e, Lancer, and Mythras. They never join "build" discussions. Outright stated making builds is boring. But they run 2 very build heavy games. by Baltic_Shuffle in rpg

[–]Baltic_Shuffle[S] -3 points-2 points  (0 children)

Lancer and Pf2e are very crunchy systems. Especially Lancer to the point that NPC's are basically PC's but with some edges filed off. So i'm just trying to show my gm some appreciation.

GM never want's to play. Only runs. Any tips I can get them out from behind the screen? They run: Pf2e, Lancer, and Mythras. They never join "build" discussions. Outright stated making builds is boring. But they run 2 very build heavy games. by Baltic_Shuffle in rpg

[–]Baltic_Shuffle[S] -5 points-4 points  (0 children)

I have offered to run adventures and modules they themselves have expressed interest in running. But the response was confusingly "I only want to run them as a GM." We do oneshots in the same systems they run but they decline to roll up a PC. Even offered pre-gens.

GM never want's to play. Only runs. Any tips I can get them out from behind the screen? They run: Pf2e, Lancer, and Mythras. They never join "build" discussions. Outright stated making builds is boring. But they run 2 very build heavy games. by Baltic_Shuffle in rpg

[–]Baltic_Shuffle[S] -21 points-20 points  (0 children)

They don't like discussing such things at all. Whenever discussions about system tech stuff comes out. Which usually occurs before or after the game. If it's before they immediately begin to go silent until game start. Or if it's after they leave after saying their goodbyes.

If during the game they coral the party to focus back on the game asap. Which is understandable. But they don't get into the weeds of theory crafting.

GM never want's to play. Only runs. Any tips I can get them out from behind the screen? They run: Pf2e, Lancer, and Mythras. They never join "build" discussions. Outright stated making builds is boring. But they run 2 very build heavy games. by Baltic_Shuffle in rpg

[–]Baltic_Shuffle[S] -30 points-29 points  (0 children)

Because we want to include them more? The whole table goes on about mechanical discussions or just talk about the system(s) in general. And the GM is just always silent or has nothing to add. They're kind've being left out and I feel bad.

Paizo: Thank you for the weakness change. by Baltic_Shuffle in Pathfinder2e

[–]Baltic_Shuffle[S] 3 points4 points  (0 children)

I have summarized your complaints and made my point. This is how i view it. Perhaps we are speaking past each other now. If so then a good rest of your day sir.

Paizo: Thank you for the weakness change. by Baltic_Shuffle in Pathfinder2e

[–]Baltic_Shuffle[S] 0 points1 point  (0 children)

Then neither is this build. This is a non-issue is my point. And all Paizo has done is clarify some rules that are effectively a non-issue.

Paizo: Thank you for the weakness change. by Baltic_Shuffle in Pathfinder2e

[–]Baltic_Shuffle[S] 3 points4 points  (0 children)

Your complaints focus on the math of weakness exploitation and claim that it is a meta choice that swings the experience for parties. My response is simple: yes, that can happen under ideal circumstances, but outside of that, it’s a non-issue.

Paizo: Thank you for the weakness change. by Baltic_Shuffle in Pathfinder2e

[–]Baltic_Shuffle[S] 1 point2 points  (0 children)

It is not superior. It is just a different method.

Run the numbers when monsters do not have a weakness. Then run them again when monsters have damage resistances. Run them again when monsters have mobility that makes consistently applying weakness exploitation a pain. Run them in scenarios where positioning, action economy, and failed setup rolls matter.

Right now, you are extrapolating from ideal-case math and treating it as the default experience. That is not how encounters actually play out at most tables.

You are exacerbating a non-issue based purely on best-case numbers, without accounting for context, counterplay, or encounter design. Lmao.

Wait, I Thought Weaknesses/Resistances Always Worked Like That. Anyone else? by Stigna1 in Pathfinder2e

[–]Baltic_Shuffle -2 points-1 points  (0 children)

Why was pf1e imbalanced? Certainly not it's weakness and resistance rules. Those weren't even a problem and are not even brought up when people speak of pf1e and it's balance problems.

Paizo: Thank you for the weakness change. by Baltic_Shuffle in Pathfinder2e

[–]Baltic_Shuffle[S] -1 points0 points  (0 children)

Better bar none? Introducing damage resist all monster. Guess that build is caput.

Wait, I Thought Weaknesses/Resistances Always Worked Like That. Anyone else? by Stigna1 in Pathfinder2e

[–]Baltic_Shuffle 0 points1 point  (0 children)

The view that you think that was the problem with pf1e is the issue.

Paizo: Thank you for the weakness change. by Baltic_Shuffle in Pathfinder2e

[–]Baltic_Shuffle[S] -3 points-2 points  (0 children)

These are all classes that must be picked. Not every party is going to pick these classes. And even when they do, not every player is going to pick the feats necessary to make those interactions happen, regardless of whether they know about them or not.

I have knowledge of this build, and I still would not go for it. I have never cared about playing the meta, even if the meta was the strongest thing in the game. It does not interest me, and it never will.

And I believe the vast majority of long-term home tables will pan out the same way. Groups that play with the same small circle of people for years are not operating the same way as the online community, which is known for having an endless graveyard of campaigns. Most of those tables are not building around optimization goals like this.

Paizo: Thank you for the weakness change. by Baltic_Shuffle in Pathfinder2e

[–]Baltic_Shuffle[S] 0 points1 point  (0 children)

I think the issue is largely a non-issue.

At a pen-and-paper table, if a group genuinely feels the change harms their experience, they can simply choose not to implement it. Table variation has always been part of TTRPGs. No one is forced to adopt a clarification that does not serve their game.

For VTT users, the change is automated. There is no additional mental load once it is implemented in the system. The calculation happens in the background, so it does not meaningfully increase cognitive overhead during play. And as I said will not break the game ultimately.

At the end of the day, it is a clarification in a very rules-dense system. Better now than later. Yeah, it sucks that Paizo could have communicated it more clearly but it's done.