From: mavra@cpac.washington.edu (Peter D. Adkison)
Subject: Re: Palladium/Wizards of the Coast Lawsuit
Organization: Wizards of the Coast, Inc.
	<1992Dec17.223531.4921@oz.plymouth.edu>
Date: Fri, 18 Dec 1992 01:59:08 GMT

In article <1992Dec17.223531.4921@oz.plymouth.edu> sos@oz.plymouth.edu (Steffan O'Sullivan) writes:

>   mavra@cpac.washington.edu (Peter D. Adkison) writes:

>   >What do you think?  Do you think that we at Wizards of the Coast
>   >should abandon our capsystem line and start producing yet more
>   >roleplaying games for a market that is already (IMHO) glutted with
>   >them, or should we try and use this case to establish a precedent that
>   >would encourage this sort of cross-company referencing?

>   I haven't seen your products yet, so I can't answer you exactly.  The
>   reason I haven't seen them yet is two-fold: I have no clue what the
>   word capsystem means (did you make it up, or is it from some milieu I
>   am unfamiliar with?), and I'm not interested in gaming multiple deities
>   except in a mythic Greek world, and I have enough knowledge to run that
>   on my own, thanks.  (Yes, I realize you will be making other types of
>   books - if I ever learn what capsystem means, I might pick one up.)

A capsystem is a system of rules for one topic.  It's not a complete
game system, but simply something that's designed to "cap" an existing
system.  The integration notes describe the interface between the
capsystem and the underlying system you're using.  TPO has integration
notes for 17 such systems.

>   I do remember, when you first asked for system gurus, telling you that
>   you'd probably be sued.  You thanked me for the warning, but said you
>   were sure your phrasing was proof against lawsuits.

Okay, so we were a bit naive.  :-)

What happened was that before we ever started this mess we retained
the services of an intellectual properties attorney (someone who
specialized in patents, trademarks, and copyrights).  We told him
about our capsystem idea, and he explained to us how we could do it
legally.

The problem is that even though we did everything legally, we're being
sued anyways.

>   I also remember saying I didn't think putting in system-specific stats
>   was either wise or necessary.  As I said, I haven't seen your product,
>   so I don't know how much space you devoted to system translations, but
>   it's bound to be a waste of space to most people.  If you give stats
>   for twenty systems, nobody will use nineteen of them.

I've engaged in many discussions with people on the usefullness of the
integration notes.  Remember, that just because you don't think
they're useful that doesn't mean they're not useful to others.  We've
received so many letters and compliments about the integration notes
that we're convinced that they are a major contributor to the success
of our capsystem line.  Those who prefer a more storytelling approach
don't see the need for them, but there are still many people out there
who like rules and want to know exactly how to convert stuff into
their systems.

>   Why can't you just make supplements like the Catalyst series?  These
>   are useful with any system, but don't risk copyright violation.  GMs
>   are usually smart people - they can translate from a generic system
>   better than I think you're giving them credit for.

Yes, I realize that many GMs are highly intelligent and wouldn't have
any trouble coming up with their own translation notes.  But what
about those GMs who aren't?  I know that *I* would prefer precise
translation notes so that I can at least get an idea of what the
original authors intended.

>   To answer your question: yes, make generic products, please.  But I
>   don't think you need to mention any other system.

I respect your opinion, but I think there are a great many people who
would disagree.  But rejoice, this may be what we end up having to do
anyways.

				--Mavra!
				  Peter D. Adkison
				  Janitor, Wizards of the Coast
				  mavra@wizards.com

The above internet address should be used for e-mail if it is
different from the e-mail address in the header.