You can bind the server to a specific address by setting $Host::BindAddress in prefs/serverprefs.cs if you want them to use seperate IP addresses.
If you want them to use the same (default) address, you'll just need to set them to run on different ports ($Host::Port in the same file).  If you run the servers with ispawn and use this method, make sure to change the port it tries to contact in the shortcut as well.

In order to use Photoshop effectively to view the skins and alpha channels as they were meant to be edited, you'll need the old png plugin.  The default plugin uses the channel for transparency, resulting in the lighter image you see there.

The variable that stops you from using keys during recording playback is $globalActionMapOnly
Make sure this is set to false, and you won't have a problem using the console.

If you want to add a key to switch it on and off, you can use something like: GlobalActionMap.bindCmd(keyboard, "ctrl minus", "", "$globalActionMapOnly = !$globalActionMapOnly;");

[TCP]

Actually, being unable to ping a server or connect to IRC is directly related to your firewall setup. 
Tribes2.exe must be able to communicate over TCP in order to use chat, in addition to retrieving the server list.
Tribes2.exe must also be able to communicate over UDP in order to query, connect to, and play on servers.

The SierraUp replacement we've included simply passes through to Tribes2.exe, as this allows people to continue using the original shortcuts.
The auto-update system is not currently implemented in the release, but when it is, it will be run through the ruby interpreter ingame.

That bug did slip by (just a missing trigger to disable the NEXT button), but as far as bugs go it is pretty fleeting.  If the person reads the text - if that ever happens - they should see that it didn't retrieve the server address and as such wouldn't have much chance of registering... the rc1d build would simply say that it couldn't connect. 
Still, the version on the site has been recompiled to include the fix to stop them at that point.

We usually recommend you download and run the full version 25034 installer located in our files section...  However, installing from the original release CD, you will need to run the 21570/24834 to 25034 prior to running our patch.  If you don't, it will simply corrupt the executable and you'll need to remove it.

We apologize for the obvious inconvenience caused by the downtime, but we were moving the site to a new server and encountered a chance error with the PHP build.  Naturally it had to be recompiled, and any PHP portion of the site was down during this time.  The auth locator and everything else was fine.
Normally in cases such as this the listing would revert to the secondary server, but this system is still untested and will probably be put more into practice with a later revision.

You should only timeout from a server if it closes or your connection... times out.  Check to make sure there's nothing on your network causing an inordinate amount of traffic, and that your connection isn't resetting mid-game.

Prefs can be reset if the server unexpectedly closes when exporting, when a syntax error is encountered in the file, or for a variety of other reasons.  It's usually best to keep a backup just in case.

I gather there may be trouble writing the client prefs under wine, so you might want to try modifying them manually or see if the working directory is correct.
Also open your console (~) after making a selection to see if it reports any errors.
A default derm selection pref might look something like this:

Code:

$pref::Player0 = "MojoBlue\tBioderm\thorde\tDerm1";

However, if the prefs are working correctly... some servers/mods may restrict you to certain armours and skins, so if you're only trying one server, you might try another.

You will need to add the executable to your firewall's exceptions as discussed earlier (tribes2.exe.local and tribes2.exe.bak are not used by the game).  Sseeing as you couldn't be running the game if tribes2.exe didn't exist, you must be missing it somewhere.  Right click the shortcut you use to start the game and click properties, and the path should be listed there.
If you use the default sierraup shortcut to launch, right click the "classic" shortcut instead.

I'm sure we could consider it for RC2... Do you know specifically what was changed or will we have to open it up and have a look? :p

The setting you're looking for is "environment mapping" under textures, but disabling this will remove reflections on all objects, water, etc.  If you don't care about shiny things though, that should sort it out.

Oh, just a note as it hasn't been mentioned yet: if your mod or customization site needs hosting, we can provide you something on hosted.tribesnext.com
If you're interested, just contact Krash on IRC, email support@tribesnext.com with "hosting" in the subject line, or drop me a private message here.