Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site alice.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!alice!pkh
From: pkh@alice.UUCP (Paul Pavlidis)
Newsgroups: net.games.frp
Subject: Re: other than TSR
Message-ID: <3669@alice.UUCP>
Date: Mon, 29-Apr-85 16:23:21 EDT
Article-I.D.: alice.3669
Posted: Mon Apr 29 16:23:21 1985
Date-Received: Tue, 30-Apr-85 06:14:38 EDT
References: <511@daemen.UUCP>
Organization: Bell Labs, Murray Hill
Lines: 20

You ask if a character should not be allowed because the players have never heard
of it.  I say, absolutely not.  What is the fun of springing a new NPC class
or monster on the party if they are familiar with the "new and unheard of" class?
I tried to keep my players from reading the Dragon so they wouldn't know all about
the new things I liked to surprise them with.  Do you let your players read the
monster manual/ other monster books during the game?  That's a definite no-no.
The fun of D&D is fighting creatures/classes which are new and unknown.  At least
for me.  I love to try to figure out what a monster does as we fight it;  I constantly
plague the DM with questions about what the monster looks like.  
	If players complain about a class/monster because it is too hard to fight,
perhaps you should reevaluate it for play balance.  *Is* it really too hard for the
party?  If you see a serious problem, don't trash the monster, change it.  Take 
away a couple of its minor abilities, or lessen damage.  Try to do this before
the game, so you don't find out that Megamonster will kill any party it encounters
after the fact.
	For the record, I like Dragon Magazine's suggested NPCs and monsters because
the SAVE ME TIME.

				in search of a party,
				Paul Pavlidis