30 April 2024

Beyond Hirelings, Sub-questors for Pyramid Questing

My Ducal House table had an idea that, since the number of things on the parties to-do list had grown so collossal they would never get to them, they would parcel off some quests as things that could be run at my Friday open table games. Become quest-givers in other words.

On the face of it I love the idea, with the caveat that the first thing they proposed to carve off was a pretty grim problem that might just make mincemeat out of some uninformed adventurers. However, with a little finesse, I am sure this can be addressed.

The pros for me are that I already have a huge quantity of material for all the things they want to deal with - since they could well have gone to deal with it themselves. So in theory I just need to extract the specific notes for whatever is the objective, shape it into a one-shot session and see however a party does.

If red-teaming is having the opposition run by others what is this called? Not blue-teaming because the people playing the one-shots would be being blue-teamed by the Ducal House players. Consultation with experts of the deep interwebs suggests 'sub-questing', 'nested questing' or 'pyramid questing' and I have to admit liking the latter quite a bit.

To make this work first I need the Ducal House players to pick some tasks they are carving off which might be a wrench given their (well founded) view that nobody else gets anything right if they do not do it themselves. Once they deign to outsource some tasks, I need to frame them up in a way that it can run as a one-shot.

Thinking about it any given task is going to have the 'dial' of how hard or easy it is to get to. The first two things mentioned in passing were retreiving a magical item from a presumed abandoned temple complex deep in the jungles of the Land of the Dead. The second thing was the harvesting of a magical component from a mythic location that they are not quite sure where it lies. Both of which have potentially interesting terrain adventures to be had.

The main Ducal House campaign has a balance of swift change (due to high PC mobility through magic) and plenty of warning for me as a DM since they like to plan things out. I think the template I'll be using here is the Spelljammer Academy mini-campaign which was all done around 'big hook' for any given session and then built out with stuff to do around that - typically the voyage to the location or the flight from consequences afterwards.

On a pure DM'ing level, it is going to be a fun exercise in T2-3 play and running bad-guys worth their salt at that level. Not quite Tuckers Kobolds level of 'ye shall fear the enemy' but the signature foes for some of this are individually not so dangerous but collectively a hazard.

I was nudging the Ducal House players towards 'you are high level now, you should have others doing things for you' - me thinking hirelings, vassals, maybe a couple of friendly NPCs. Classic DM mistake, my players took what I was thinking and ran off over the horizon with it...

4 comments:

  1. You've reached DM end-game. When your high-level players are ruling domains and giving out adventures to lower level groups. Do we need a term? This is what "domain play" looks like if you have a large enough group. :)

    ReplyDelete
    Replies
    1. You are right in that the Ducal House group are doing domain play but it just seems an odd way to describe it to the second bunch who have no connection to them... but maybe that is indeed a way to say it - 'you are catching the domain quests of another table'

      Delete
    2. It might feel a bit cumbersome but I like the explicit nature of describing it that way. There's a kind of expansion to the world's scope. It also helps to emphasize the shared-open-world nature of a big game, as well as signaling that PCs can become movers-and-shakers in the world.

      Not to mention, the Ducal House group are learning the answer to the frequently proposed question "Why don't all the high-level NPCs in the setting fix all these problems?" :)

      Delete
    3. That is a great point - it is ridiculously long to-do lists all the way down...

      Delete