*********************************************************************************
*																				*
*							Football Pro 2000									*
*								Final Patch										*
*							Readme    Document									*
*																				*
*********************************************************************************

Note from Joe Reifel:

This document contains information pertaining to the 2.010 patch for Football Pro 
2000.  This is the final patch for Football Pro 2000, and catches you up to
all development up to 3/2/99.

Due to the unexpectedness of the termination of the Football Pro product, this patch
was not completely up to a level that I would normally be comfortable with.  Many
bugs exist in the patch due to where we were in the development process, and I felt
that you should know that in case problems arise.  Nonetheless, I belive that the
improvements contained in this patch may very well outweigh the risks of releasing
it.

The rest of this document is an attempt to explain everything that was fixed/added/
improved, as well as a list of known issues with the current build.


2.010 patch installation

* Make sure you have the previous, 2.008 patch, installed prior to installing 2.010.

* Place FBPro2010.exe into your \sierra\fbpro99 folder and run it.  It will 
	automatically extract itself into the proper place.

2.010 patch additions

* Devensive Back coverage has improved, and is adjustable through the hookups.
* Running Back AI has been improved, and is adjustable through the hookups.
* The new ratings hookups system has been added.  See FB2000.ini for explanation of how it 
	works. 
* New blocking is in place, but no other blocking functionality was added. 
* New method of internally organizing the teams' rosters.  As a result, the league 
	files will be upgraded to the new version when you load them.  This should minimize
	trading/duping issues in the game.
* New Game Loop that should produce smoother gameplay.
* New play/playbook internal functionality was added - this may cause some issues with
	the play selectors, play editor, etc.  Your plays will be automatically upgraded.
* A bug where player ratings would be set to 0 and databases would become corrupt
	when viewing player statistics was fixed.
* Several FBSetup.ini file settings were added to improve flexibility.  As a result,
	a new document, FBSetupReadme.txt, was published to explain ALL FBSetup.ini 
	settings for your convenience.  Note that some debugging settings were also 
	published.  I did this because we no longer support FBPro99, and this may help 
	you to play the game.
* New method of gathering input in the game. This may have effectively broken the
	arcade mode of playing the game (joystick), as it was not completed yet.
* A situation editor was added (SituationEdit.exe).  Dial in the situation and fire it off.
	This might help with debugging/playtesting.


2.010 patch known bugs

* Joystick control is more erratic.  The game may have been effectively crippled in
	joystick control mode.
* Keyboard control may be erratic due to the changes that went into place before the
	office closure.
* Replay.dll has been removed from our project.  As a result, the "Load VCR Tape" 
	functionality was disabled, and therefore you will not be able to load replays
	from the shell.  You may want to just delete replays altogether to save on disk
	space.
* The resource leak still exists in the game, and may cause system slowdown after
	simming several weeks at once.
* There is a known lockup when simming an entire season at once - I've seen it happen
	after an average of 7 weeks, the game just locks up and stops responding.  
	Restarting the program fixes this problem, with no harm to data files done.
* Multiplayer play may very well be broken.  Every time we make major changes to the
	arcade game, it affects multiplayer, so I would not be surprised if this did not
	work in any form any more.
* Loading a play from the playbook inside the play editor is broken and will crash the 
	shell. There is no way around this fact - you have to load a play from the 
	play database and modify it. This is because the code simply wasn't finished in 
	time.
