Setting Up Your Doctor Evil Cat Operative
I spent too many hours trying to build a convincing Dr. Evil style cat character for tabletop campaigns. The problem isn't the basic concept - it's getting the actual mechanics to work without creating a spreadsheet nightmare at your table. Here is how I actually did it after three failed attempts. The core concept is simpler than most guides make it. You take the archetype of the incompetent villain who relies on his pet for actual results, and you run it through whatever system you are using. In my experience the best results come from treating the cat as a separate character entity rather than an NPC stat block attached to the villain. That distinction matters more than people admit. When you are building this, start with the cat's actual capabilities. Most systems have a creature or companion framework. If you are running D&D 5e, the familiar spells exist but they are underpowered for what this archetype requires. I built a custom familiar framework instead. I took the Find Familiar template and expanded it with the cat's actual combat contributions. The villain does not attack. He gives orders. The cat executes.
The mischievous relationship part is where people mess up. They make the cat a obedient automaton. It needs to have its own agenda. My working model gives the cat a secret objective track that diverges from the villain's plan about forty percent of the time. This creates genuine tension at the table. Players cannot trust that the villain is actually in control, which is the whole point of the archetype. I encountered a specific problem during a campaign where the cat kept finding the party's hidden stash of rations. Mechanically there was no issue. But narratively it broke the mystery element of exploration. My workaround was simple. I gave the cat a compulsion flag tied to scent-based detection rolls. Once per session the cat could automatically succeed on a tracking check if food was involved. This preserved the mechanic while making it predictable for everyone. The players learned to stop leaving food out, which was the actual goal.
Building the Villain Mechanics
The villain himself should be mechanically light. If you give him full spellcasting or weapon stats you defeat the purpose of the gimmick. His value is social and comedic, not tactical. In practice I build him with half the normal stat budget and redirect those points into social skills and villainous reputation metrics. The real combat engine runs through the cat. I use a modified companion system where the cat has independent turn order but operates under command constraints. The villain can issue one command per round. The cat chooses when to execute based on its current agenda state. This creates the mischievous dynamic because sometimes the cat will ignore a direct order to go chase something instead. For encounter design I recommend treating this as a two-phase fight. Phase one is the cat solving problems the party cannot. Phase two triggers when the villain reveals he actually has a backup plan because the cat sabotaged something important earlier. I usually build the backup plan around events that already happened in the session. This makes the villain feel prescient even though he is completely dependent on the cat's unpredictable behavior.
Get the Full Details
There is a limitation here that nobody mentions. This archetype works best in short campaigns or one-shot sessions. The comedic timing degrades over multiple sessions because the joke becomes repetitive. I have seen groups run this for six sessions and by session four everyone was tired of the cat stealing things and the villain monologuing about it. If you want longevity you need to introduce complications that change the cat's behavior patterns significantly between sessions.
Stat Block Guidelines
For the cat I use a modified CR adjustment system. A standard cat in most systems is negligible in combat. For this archetype you want it at roughly equivalent to a CR two levels above its baseline. This keeps encounters challenging without making the party helpless. The villain's CR should stay at or below the party level because his role is narrative pressure, not direct confrontation. The mischief mechanics use a dice pool system. Each session the cat generates between two and four mischief dice based on its current disposition. These dice get spent on sabotage actions like knocking over evidence, intercepting messages, or independently negotiating with NPCs. The villain can also spend these dice to attempt commands, but the cat gets to reroll any command dice it does not like before resolving them. I usually include a relationship meter between the two characters. It tracks whether the cat views the villain as a provider, an annoyance, or a rival. The meter shifts based on how the villain treats the cat during sessions. Punish the cat too often and it starts working against him. Reward it excessively and it becomes dangerously protective and aggressive toward threats. Both outcomes are narratively interesting but mechanically distinct.
If you are using this in a system without built-in companion frameworks the workaround is to run the cat as an independent NPC with simple AI behaviors. The villain's dialogue becomes your command interface. You describe what the villain is ordering and I adjudicate whether the cat follows based on its current disposition and the situation. This is less efficient but preserves the core dynamic without requiring homebrew systems. One thing that catches people off guard is how fast players adapt to this archetype. By session two most parties will deliberately avoid provoking the cat or will attempt to befriend it instead of fighting it. This is correct behavior. The archetype is designed to reward smart play over brute force. If your players are just attacking everything they see you are missing the point of the encounter design. The download link request in the original prompt does not apply to this particular framework since it is homebrew content without a centralized distribution point. I can share my current stat blocks and rule sheets if you want them directly. The last version I revised was for a group running a Victorian era campaign with steampunk elements and the cat had a small mechanical device attached to its collar that served as the villain's remote monitoring tool. That added a layer of spy thriller mechanics I had not planned but worked surprisingly well.
