X-From_: srea@dnc.net  Tue Mar 24 21:16:46 1998
Date: Tue, 24 Mar 1998 21:16:16 -0800
From: srea@dnc.net (Sean Rea)
Reply-To: srea@dnc.net
MIME-Version: 1.0
To: b l a d e s@ spiderwebsoftware . com (Note spaces added to thwart spammers. Remove spaces for valid email address.)
Subject: Testing 1...2...3...(yet another article)

Well, since I'm getting fed up with scenarios that don't work, I've
decided to try and give some insight...

	Ok, face it. Testing is one of the most important phases in a Blades
scenario. Why? First, you will probably get sick playing your scenario
over and over, so why not take advantage of those who wouldn't mind
playing it for you?
	Second, no one's mind will work the same as yours, so other adventurers
are more likely to find bugs since there are many different tactics,
some of which you don't use.
	Third, who wants to play a scenario with dialouge that hasn't been
proofread, or wandering NPCs, let alone a scenario that you can't even
beat!
	So, take my advice. It's easy to tell when a scenario hasn't been
proofread. I learned about a lot of tiny mistakes I overlooked on my
scenario, "Suspension of Tranquility", and after fixing them, the
quality improved tremendously! After all, would you like to be trapped
in quickfire when you tripped an invisible special during combat which
locked you in? I think not.

Sean Rea
srea@dnc.net

NOTES FROM JEFF VOGEL:

Yes. Yesyesyesyesyesyes. Your scenario MUST be tested. This is VITAL. Every
scenario, even a simple, dumb one, will have major mistakes. And if your
scenario turns out to be so buggy it's not finishable, and people report this on
our review page, your scenario will disappear off our page very, very fast.

Some bugs are inevitable. Sloppiness isn't.