
First of all, start of with a FRESH install of tribes (ofcoz upgraded to V1.11).
Do *NOT* install any scripts (even clientside scripts) or any modified bitmaps etc.


Now, follow this procedure:

1. make a subdirectory under tribes called Fstat (You *MUST* use this case!
   NOT! fstat, not FSTAT but Fstat)
   NOTE: It's *REALLY* important that it is called Fstat (note the case too!).
   The reason for this is that the secureloader checks *ONLY* in this directory
   if anything fails!
   
2. put scripts.vol and config.cs in this directory
   (\tribes\Fstat\)
3. Edit the Config.cs to your personal adjustments.
   NOTE: Some of the options in serverprefs.cs is also in config.cs, use
   config.cs to change them! (A bug in tribes might screw up your serverprefs.cs
   but not config.cs!

4. Start tribes (WITH INFINITIVESPAWN!)
   (EG: C:\tribes\infinitespawn *C:\tribes\tribes -mod Fstat +exec serverprefs.cs - dedicated)



If something goes wrong:

Check the name of the directory that you put scripts.vol and config.cs is called
Fstat! (\tribes\Fstat) And pay attaention! IT'S CASE SENTITVE!
Check that \tribes\config\autoexec.cs is EMPTY! (Yes, clientside scripts can
override functions needed!)
Check that you don't have any of your stupid cheats installed. The server will
validate these instead, and everyone else will not be able to connect!
Delete the file \tribes\console.log (if it exists)
put these lines into autoexec.cs:
   $Console::Logmode="1";
   $Console::Printlevel="3";
Then start the mod.
Check console.log for any errormessages that might give you a clue.
if all this fails, you can either email me at freaky@fstat.org, or
grab me at irc (#av on quakenet)


