It's time to set the record straight. You see, me and a friend of mine have been getting some bad press lately, and while I don't mind if people talk trash about me (not that much, anyway), my buddy does care. What's worse, he usually does something about it. Something rather violent. And so, the purpose of this second episode of Play Dirty is devoted to explaining the often misunderstood actions of one of my oldest friends, Jefferson Carter. Episode Two: The Return of Jefferson Carter
In many ways, I am responsible for all the talk people have been spreading about Carter. After all, it was my own article on gamingoutpost.com that introduced many people to Jefferson and his methods. So, in order to move forward, in order to give you a complete understanding of the Man, let's take a couple of steps back. Then, and only then, can you fully understand. (If you haven't read the article yet, don't. Not just yet. Wait for a moment or two. I'll tell you when you should go read it. Be patient, all will be revealed in time.)
Let's start in 1988, when I first started college at the University of Minnesota. I was a game master, running a regular Call of Cthulhu game on Thursday nights (CoC being my first love, the first game I ever bought and the first game I ever played -- well, ran). The game gained quite a reputation. Everyone else was running games that were far more forgiving of PC error. I did everything I could to make the game legendary at the campus, including using every . . .
This article originally appeared in the second volume of Pyramid. See the current Pyramid website for more information.
Article publication date: November 19, 1999
Copyright © 1999 by Steve Jackson Games. All rights reserved. Pyramid subscribers are permitted to read this article online, or download it and print out a single hardcopy for personal use. Copying this text to any other online system or BBS, or making more than one hardcopy, is strictly prohibited. So please don't. And if you encounter copies of this article elsewhere on the web, please report it to [email protected].
