The Head in the Road
In the end, he swore he wouldn’t interfere with the party’s mission; it would be best if they not be seen talking for the remainder of the trip. However, he could serve as a distraction; since the entire caravan knew about his supposed association with the Harpers, the cultists would certainly be keeping an eye on him, and less of an eye on any other potential threats. Also, he offered to get the party in touch with the Harper contingent in Waterdeep once they arrived.
A few days later, the party arrived in Daggerford, the last major stop before Waterdeep. Several passengers who had been traveling with the column left, but two signed on for the last leg of the journey: a female gnome, and a tall, bald man wearing a suspiciously warm woolen cap that covered his head, ears, and neck. Making matters more suspicious, this stranger managed to engage the cultists, and even to somehow book passage on their wagon.
With a fair bit of Wisdom (Perception), the warlock noticed that the stranger was sporting some interesting tattoos on his head and neck that he felt necessitated the strange choice of headgear. Although this stranger was traveling with the cultists, he didn’t seem welcome in their midst, so while the caravan camped beside the road one night, the warlock approached the stranger.
He seemed affable enough, and when the warlock called him out on his attempts at subterfuge, the man admitted that he was Thayan, a nationality known for it’s almost rabid devotion to necromancy, and feared and hated throughout the Sword Coast. However, he claimed that he was only a merchant before the rise of Szass Tam, the lich who now rules Thay. Not every Thayan was devoted to the art of raising the dead, this man claimed, and he was headed to Waterdeep to take a ship across the ocean to a place where Thayans aren’t as repugnant as they are considered on the Sword Coast.
* * *
The caravan trip is getting a bit long in the tooth, so events were sped up just enough to reach a milestone this week or next week. Modeling a two month old journey, mixing in excitement and adventure, is difficult. It shouldn’t be wall to wall combat, but it shouldn’t also be boring. It shouldn’t be undiscovered country (a well-traveled trade route), but it shouldn’t be uneventful. There’s always opportunities for combat in D&D, but there’s rarely scenarios which require real RP skills, so I wanted to focus this trip more on the non-combat random events listed in the module.
RPing is difficult, though, on both sides of the screen. From my perspective, combat is simple: pay attention to the enemy stats, use their abilities to drive their behavior, and pull no punches. The same goes for the players. RPing non-combat events is significantly less simple. These require a setup, which is easy and provided in the module, but they also require a response that’s built upon the player actions. It’s up to me whether or not the player actions can subvert and trivialize the importance of the event’s outcome for the remainder of the story, or to somehow make player actions have a long-lasting effect and find another way to keep the story on track. Ideally, in a custom campaign, I’d be perfectly fine with the first situation: let the players drive the story outright, and just fill in the gaps with the result. With a module, though, certain encounters and events are important later on, and if the players trivialize them by ignoring them, or turning them around (in a logical sense), taking the outcome of that encounter out of the flow of the module is like playing Jenga with the story. Once in a while should be OK; When it becomes a pattern, and too many blocks are removed, the whole thing falls apart.
I was a bit concerned about the approach the players were taking with the oathbreaker. They were confrontational and arrogant, playing the encounter like they had the upper hand. His story about breaking off an engagement couldn’t possibly be true since he had a Harper insignia, and outright told him that he owed them the plain truth for digging him out of the ground. I ended up strongly suggesting that maybe they should name-drop Leosin’s involvement, because I was very disappointed that they were taking a combative approach rather than an approach that (to me, which may have been the real problem) should have been more logically forthcoming: he’s a Harper, and the party was sent on the mission by the Harpers, so the mutual association could be exploited instead of relying on brow-beating this guy into compliance.
This was obviously an overstep of my job as the “impartial DM”. If the players want to approach a situation as they see fit, it should be their choice, and it’s up to me to either deal with the consequences (in some way), or to somehow re-route them back to the official story later on. This encounter was from the random encounter table, which means that technically it has little ramification on the overall story, so really there is nowhere to re-route the players to. I was more disappointed that I felt that there wasn’t a lot of thought being put into the approach, but that should ultimately be the player’s call: however they want to approach a situation should be the way they approach a situation, and it’s up to me to deal with the results. My job is really to not use the party’s actual approach as a determination for reward or punishment; their actions simply are what they are. If the players push the story away from the intended outcome, then it’s either find a way to get the story back on track (if it’s important to do so), or to simply let the outcome stand on it’s own.
However, after feeling really bad about blowing up about the situation, I opted to install this Harper as a reliable contact in Waterdeep that the players can use in an unfamiliar city. I figured that while the players considered getting the truth as gratitude for saving this guy made sense, getting the gratitude of an entire city-wide network of the Harper society was an even better reward.