Camelot And The Knights Of The Round Table

So You Want to Actually Run a Camelot Campaign

Everyone talks about Arthurian legend like it's some pristine collection of noble quests and chivalric codes. It isn't. The source material is messy, contradictory, and full of stuff that would tank a traditional D&D campaign if you just pasted it in. I spent three years running a Camelot campaign for a regular table and learned most of the hard lessons the long way. The standard approach to Camelot And The Knights Of The Round Table is to read Thomas Malory, pick some knights, assign alignments, and start rolling initiative. That works fine for six sessions. Then the plot hits a wall. You realize most of the Lancelot-Guinevere story doesn't translate into gameplay. It's Courtly Love drama, not dungeon crawling. Your players are going to get bored within two sessions if you try to make that the backbone of anything. I learned this when my player trying to play a straight-chested Galahad variant started asking why nothing dramatic was happening. The game had plateaued. We had done three treasure hunts, two monster encounters, and a diplomatic visit to a rival kingdom. Nothing felt like Camelot. The problem wasn't the mechanics. It was the tone. I had been treating the setting like a generic fantasy kingdom with a round table aesthetic slapped on top. It isn't. The magic in these stories is psychological, political, and deeply personal. The real conflict is internal. You have to design around that.

The Honor System Is Your Core Mechanic

Here's what actually works: treat the knights as characters whose greatest weapon and their greatest weakness is the same thing. Honor. Not virtue. Honor. There's a difference. Virtue is doing the right thing. Honor is doing what you've sworn to do, even when the right thing and the sworn thing are in conflict. That's where the drama lives. In practice this means every knight has a set of Oaths. Not abstract alignment scores. Specific verbal commitments with clear triggers. When a player's character breaks an oath, it shouldn't be a morality point deduction. It should trigger a mechanical and narrative consequence. In my game I used a simple tracking sheet. Each Oath had a Stress marker. When challenged, the player made a check against their Oath Stress. Failed, they broke under pressure and took a permanent mark. Three marks on the same Oath and the character is effectively broken in that area. They can still act, but the story treats them differently now. Other knights won't trust them. The fae won't bargain fairly. This created more interesting roleplay than any amount of dungeon loot ever could.

Don't Skip the Political Layer

Camelot was never just a bunch of heroes hanging out in a castle. It was a fragile political alliance held together by charisma and shared purpose. The Round Table wasn't a seating arrangement. It was a constitutional statement. Every knight had equal voice regardless of birth. That caused problems. Real problems. High-born knights resented low-born ones getting equal say. Foreign kingdoms saw it as a threat. The Saxons didn't care about your code of chivalry. They cared that you were building a centralized power structure on land they'd held for generations. My workaround for this was implementing a Governance Phase at the start of each in-game month. The players had to allocate resources, negotiate with faction leaders, and make public decrees. Each decision generated Favor with some groups and Grievance with others. If Grievance hit a threshold with any major faction, it triggered complications. A border raid. A denied trade agreement. A rival claiming your castle is illegitimate. This kept the campaign from devolving into endless combat loops and forced the players to think about consequences beyond their next combat encounter.

The Lancelot Problem

You can't ignore the Lancelot-Guinevere arc. It's the thing that breaks Camelot. But handling it poorly turns your campaign into a soap opera. Here's what I did instead. I gave the player running Lancelot a secret secondary Oath. Their primary Oaths were to Arthur and the Table. The secret one was to Guinevere. The two Oaths were designed to be mutually exclusive over time. When the moment came where Lancelot had to choose, I didn't force it. I let the player feel the weight of it through the game mechanics. Both Oaths were at maximum Stress. Breaking either one was mechanically costly. The narrative consequence of choosing one over the other was handled through NPC reactions and shifting political alliances rather than a dramatic cutscene. The result was messier and more realistic than any scripted tragedy could have been. If you're looking for adventure seeds that fit the material, focus on these categories: For tracking the Honor system I recommend a simple spreadsheet with conditional formatting. Each Oath gets its own row, Stress markers are color-coded, and the Governance Phase uses a pivot table to summarize faction standings. There are some free online tools built around Arthurian campaigns. The Camelot And The Knights Of The Round Table project on GitHub has a Python-based character tracker that handles Oath Stress fairly well. It's not polished but it does the job. For maps, the British Library's Ptolemy-based maps of post-Roman Britain are public domain and surprisingly accurate for the period you're working with.

This system requires players who are comfortable with moral ambiguity and long-term consequence tracking. If your table prefers action-oriented gameplay with clear villains and loot rewards, you're going to fight the mechanics every session. There's no way around that. You could strip the Honor system down to a simple reputation tracker and lean harder into combat encounters, but then you lose what makes a Camelot campaign distinct from any other fantasy setting. The tradeoff is real. Pick your table carefully or adapt the framework significantly. Also, don't underestimate how much prep the Governance Phase demands. Each month requires you to prepare faction standings, potential complications, and NPC motivations. If you're running a weekly session, that's roughly two hours of prep per session just for the political layer. Combat encounters add more on top of that. It's not for GMs who want a light campaign. The system works because the political and personal stakes are always present, but that presence requires consistent maintenance. The one thing I wish someone had told me before starting was that the fall of Camelot isn't a disaster to avoid. It's the natural endpoint of the story. Every decision the players make, every Oath they break or keep, every political maneuver either accelerates or delays the collapse. Trying to prevent it entirely undermines the narrative. The campaign should be about what kind of Camelot they build before it falls, not whether it survives forever. That's the part that makes it feel authentic to the source material while still giving players meaningful agency.