I find I tend to get sucked into the minutiae of the rules, and then get frustrated by the length of time things take. So, I typically stick to rules-light until something dramatically important happens, where more details can add to the story and it's worth going more slo-mo for the action. Similar to the idea of using mooks for the most part, but the lieutenants and the boss get full combat options.
this post was submitted on 11 Jul 2023
2 points (100.0% liked)
GURPS
240 readers
1 users here now
founded 2 years ago
MODERATORS
This seems like the most pragmatic approach. Personally, in my upcoming game, I'm planning to basically go with my gut while allowing my players to challenge my rulings at any time. If they do, they can reference a specific mechanic they think should be used, and I'll either agree or counter.
That way, things keep moving most of the time, but players don't feel like they suffered some crucial irreversible consequence because of flippant or inconsistent rulings. I think putting the burden of finding the rule primarily on the player also prevents overzealous challenges from bogging the game down.
I used to get super crunchy when I played GURPS Supers. Less so with other genres.
Man, I haven't played GURPS in decades. I naturally barely remember its play tbh.
But I'm generally a crunch friendly GM, but not a crunch mandatory one. I tend to prefer crunch where it's useful, meaning in combat. Outside of combat, there's much less use for it. You don't really run into things where it makes a lot of sense unless there's a lot of quasi-random factors in the activity in the real world.
That's interesting, I was drawn to GURPS precisely because it offers so much crunch outside combat. As much as I do appreciate the granular combat mechanics, I like the unique blend of freedom and consistency offered by the skill mechanics. I've grown tired of DnD which forces the GM to either spontaneously adjudicate an action and try to stay consistent the next time the scenario comes up, or just forbid any action not specifically described RAW.
Yes, obviously, the GM is still the one to have final say, but I think it's so much easier to have RAW defaults to refer to when needed.
Crunch is not exactly a problem if you can write a few simple programs to take care of it.
I've been playing with a local GPT instance trained on the sourcebooks. It needs a little work but hopefully by the time our campaign starts I'll have a working GM assistant.