Tribes:Vengeance is based on the Unreal Tournament Engine.

Here’s how it differs from normal UT scripting:

•  When extending other base classes you have to specify the fully qualified name of the base class, e.g. instead of doing class Foo extends Object; you HAVE to do class Foo extends Core.Object; – this is naturally braindead but I guess IG may have had their reasons.
•  C-Style comments are broken. Don’t use /* or */ to delimit comments, or blocks of code. It breaks if there are any other slashes inside. This  is pretty dumb.
• When attempting to use structs defined inside other classes in your own derived classes, you may have to use the dependson() directive like so: class Foo extends Engine.Object dependson(~SomeClassWithStructsInIt);

Things you will need to do to make UCC work (For Beta/Demo)

Edit your UCC.ini, and ensure that you have the packages that you’re working on listed like in this following example:

~EditPackages=~Core ~EditPackages=~Engine ~EditPackages=~IGEffectsSystem ~EditPackages=~IGVisualEffectsSubsystem ~EditPackages=~IGSoundEffectsSubsystem ~EditPackages=~Editor ~EditPackages=~UWindow ~EditPackages=~GUI ~EditPackages=~UnrealEd ~EditPackages=~IpDrv ~EditPackages=~UWeb ~EditPackages=~UDebugMenu ~EditPackages=~MojoCore ~EditPackages=~MojoActions ~EditPackages=~PathFinding ~EditPackages=~Scripting ~EditPackages=~AICommon ~EditPackages=~Movement ~EditPackages=~Gameplay ;~EditPackages=~TribesGui ; these have to be commented out, crashes otherwise. ;~EditPackages=~Tyrion ; these have to be commented out, crashes otherwise. ~EditPackages=~Physics ~EditPackages=~TribesAdmin ~EditPackages=~TribesWebAdmin ~EditPackages=~TribesVoting ~EditPackages=~TribesTVClient ~EditPackages=~TribesTVServer ; my packages ~EditPackages=~FooPackage ; Add your packages at the bottom of the list, othwerise you’ll get undefined()s

•  When compiling, you need to use “ucc make -NoBind” otherwise all the core packages will look for their associated headers/and dll’s to bind.
• You will need to edit StartupUCC.ini and include the path to the script source code.

I wrote a bit of code, using Luigi’s code for GameSpy in PHP, that allows you to query the gamespy master server and retrieve the list of IP and port’s for any of the GameSpy supported games.

This handy image –> [http://vengeance.za.net/servers/serverpng.png]
for example, is generated using the code, and is updated dynamically every 3 minutes.

The query code isn’t really cleaned up enough or ready for release yet, but you can mail me  if you’re interested in obtaining a copy in the meantime.

I wrote a small PHP script that uses QStat, and XML/XSL to display a Tribes:Vengeance servers’ server state. If you can’t make it work please don’t bug me for support. There is NO support for this thing and I don’t have the time to answer everyone’s queries, even though I’d like to.

It’s available here under a GPL license.

Sadly,  it turned out that Tribes:Vengeance really sucks. Vivendi cancelled the very FIRST patch for the game, with a couple of lame excuses.  Such as “we only sold 7800 copies in the first week”. It’s pretty straight forward guys.  Release a game that is broken, unfinished and no fun to play, and nobody is going to want to buy it. Simple economics. If you had at least bothered to fix it, you may have caught the “long tail” and benefited from the loyalty of the fanbase.

It’s a pity. Tribes was the best team-based Science Fiction game of the last two decades, and I’m going to seriously miss it. Every other game I look at that doesn’t have jetpacks simply gets a “poor groundhuggers” response from me. Perhaps community games like Renegades, or StarSiege:2845 will bring back some of the goodness that was Tribes, but it just simply isn’t going to happen in the next year or two.

*sob*

I have however dabbled in some Tribes:Vengeance development, but only briefly.

My T:V Projects

VengeanceSpawn – infinite spawn-like tool for Tribes:Vengeance
VengeanceMaster – info about the Gamespy system used by the in-game  T:V matchmaking