===================================================================================
 June 8, 1998
===================================================================================

Title                   : The Buffet Warren
Filename                : bwarren.zip
Author                  : Barry Walker "Jethro" 
Email Address           : barry@icom.net
WWW Homepage:		: http://idt.net/~diba/
Date 			: June 8, 1998
Description		: This is my first Q2 map.  In fact, its the first map of any sort
			that I've ever let out of my own house.  It's a CTF "mirror" map,
			as all of mine are likely to be.  I'd appreciate your feedback, but
			keep in mind that "your map stinks" won't help me make better maps.
			Be sure to tell my WHY it stinks and what I could do better.


Additional Credits to:	id - without whom I would never have made a map.
			Lithium (for QOOLE, my editor).
			RUST: for his excellent and useful tutorial.
			Quake 2 workshop: the guys who monitor qworkshop@quake.com, also
				for great tutorials and E-Mail assistance.
			Ridah (Ryan Feltrin): author of the amazing ERASER BOT, which is
				how I test these maps out.
			Colin ("funkyassmime"): my son, whose patience and assistance in
				play testing is invaluable.
			Diane (my wife): A Q2 widow, who puts up with this absorbing 
				pastime of mine.
=========================================================================================

* Play Information *

Game			: Quake II/CTF
Level Name       	: The Buffet Warren
File name		: bwarren.bsp, bwarren.rtz (ERASER BOT routes)
Single Player           : No.
Cooperative 		: No.
Deathmatch 2-8 Players  : Yes. (but it's not geared for DM play)
Difficulty Settings     : No.
New graphics		: No.
Anything else new:	: No.
			  
					 
					    
* Construction *

Build Time      : weeks and weeks 
Editors used    : QOOLE 2.45
		   	  

Compilation:	Qbsp3 	      build time: about 2 minutes
		Qvis3 (full)  build time: about 2.5 hours
		Qrad3 -extra  build time: about 1.5 hours
		Brushes:  1501
		Your mileage may vary.
		
============================================================================================
Platform used   : Win 95 on a P-233 64MB SRAM
Known Bugs      : I don't know that it's a bug, but I can't get the camper discouragement
		feature (water) to work exactly right.  Either you can always see the
		surface (whether the water's there or not - current implementation), or 
		you can never see the surface. 



--------------------------------------------------------------
The Story:
--------------------------------------------------------------
CTF:

Our two friendly rivals have taken over what was once a control station for a tidal flood
area.  In their battles, they destroyed the bottom of the piping, and the tides once again come 
in and out periodically, incidentally threatening to drown campers.  One of the guys got a 
little drunk one night, and decided that the tunnel boring machine made a perfectly good
aircraft, if you pretend that the ground is "just thick sky".  They got him off of
there, but not before he'd "flown" around some.
--------------------------------------------------------------


* Loading information *

To load this Q2 map:
Unzip both files in the archive to c:\quake2\baseq2\maps\
Start Quake 2/CTF normally.  Run the map by typing the tilde key (~) to bring down the
console and and type:

"map bwarren"

If you have the ERASER BOT, I've included my routes for this map.  It's easier to test
with BOTs, but I'd like to hear of human/human interactions as well.  The routes file
is bwarren.rtz.  Unzip this to ERASER's ROUTES directory to use it.

For whatever, just email me at barry@icom.net.		 


* Copyright / Permissions *

(c) by Barry Walker, 1998.
The author's written permission is required for commercial use.

You MAY distribute this BSP over or on any electronic media, provided that you include all
distributed files intact and unmodified, and you don't charge the recipient anything beyond
the actual cost of the media and shipping.

Use of this BSP and all associated files are entirely at your own discretion and risk.  I
assume no liabilty for any direct or consequential losses you might incur as a consequence
of using these files.  I don't even guarantee that they'll run on your machine, but I'm
willing to help if you have a problem.