I've done a lot of work to make my pack as easy to install as possible. If you read this page you'll hopefully be able to avoid the most common mistakes that other people have made!

First, after you've downloaded the file, you'll notice the PrestoPack has a lot of script files a single .ZIP file. You have to extract these files into your Tribes config directory, with subdirectories turned on! This will create a new subdirectory, called Presto, under your Tribes\config directory.

How can you tell if you unzipped it right? The majority of the files should have ended up in the directory TRIBES\CONFIG\PRESTO. For instance, if TRIBES is in C:\DYNAMIX\TRIBES, then my files are in C:\DYNAMIX\TRIBES\CONFIG\PRESTO.

Want to make absoluteley sure? Well, after you've unzipped, hit the Windows Start Menu button, then select Find... and Files or Computers. Enter a search for one of my files, for instance TEAMHUD.CS -- make sure you're looking on the right drive! It should find the file, and in the right directory (In this picture, I've made the important things a little bigger so you can see them)
In other words, you should find the file in a directory that ends with TRIBES\CONFIG\PRESTO. If it tells you the directory on the right, it means you accidentally unzipped it into the TRIBES directory instead of the TRIBES\CONFIG directory, so go back and Make Things Right. :)

Next, edit your TRIBES\CONFIG\AUTOEXEC.CS file, and on the very last line of the file, insert the line
	exec("presto\\install.cs");
Type it exactly like that, with the double backslash and everything, and make sure it's the last line. Don't rename the file to that text, just open it in a text editor and add that line as the last line. (Sorry, I know you're not dumb, but some people are ;) ) You should not be running Tribes when you do this, by the way. Quit first, then restart when you've made your changes.

If you don't have a TRIBES\CONFIG\AUTOEXEC.CS file, then I have included one in my pack for you. Just copy it out of the TRIBES\CONFIG\PRESTO directory and up into the TRIBES\CONFIG directory. The copy I included has already been modified to add the install line, so you don't have to do it yourself.

Don't run Tribes yet. Read the rest of this page first.


Your personal settings are stored in the file PRESTOPREFS.CS, which is in the TRIBES\CONFIG\PRESTO directory. Each option has a full explanation. Please read the entire file to see what options are available to you!

Future releases of the PrestoPak will include an updated PRESTOPREFS.CS ... So if you customize the settings, please back up your PRESTOPREFS.CS file so that it is not lost when you install a later version of PrestoPak.

When you run my pack for the first time, it will back up your AUTOEXEC.CS and CONFIG.CS files. These files store your script loadings and key bindings. I back them up in case someday, heaven forbid, you should decide you don't want to run my script any more.


Should the day arrive that you no longer require the services of PrestoPack, bring up a console in Tribes. This is done with the ~ key. At the prompt, type:
	UninstallPrestoPack();
Yes, that's a semicolon at the end, and you need it. If it says "Syntax error line 1", you mistyped it.

DON'T BE SURPRISED! When you uninstall, Tribes will immediately quit. I had to do this so that it wouldn't just auto-save my keys back over your config! Tribes did not crash.

You will find that your AUTOEXEC.CS and CONFIG.CS have been restored to exactly as they were right before you installed my pack. I'm sorry, this means that any config changes you made while my pack was installed will also be lost. There's no way I can uninstall my stuff and not your other changes.

  • If you don't want this to happen, don't use the automatic uninstall.
  • If you're just evaluating the pack, don't make other significant changes until you've decided if you want to keep using my pack!
  • Even though you've uninstalled to the point right before you ran my script for the first time, you still have to edit your AUTOEXEC.CS and remove the exec("presto\\install.cs") line! Otherwise it will install again :)
Okay, you can go run my script now!

If you have any trouble, make sure to visit the Troubleshooting Page