This is my first actual tutorial, a work in progress over the last several months. Some of you might remember that discussion on creating an anti-cheat for Tribes 2 as serverside. I have tried, unsucessfully, many times to create something which would be sufficiently reliable in detection and would not create false positives. As of recently I have given up on the aspect of making it 100% server side, and rather have decided to make a small client side download. While am I aware of DefenseTurret and Rodent's efforts, I am not satisfied with the reliability, resource intensiveness, and extra bloat that comes with running a DT client.
My goal became creating a lightweight anti-cheat system that could be dropped into any server, a small download for clients that would do nothing on non-anticheat enabled servers, but would do a nearly foolproof detection of the cheats used in Tribes 2. Another goal, since this would require a client side download, was to prevent any changes to emulate the nature of the server-client communications in efforts to bypass the detection.
This is primarly focused to all the UltraXLers who were around during the RSA clan cheating incidents(use of HM2 in regular play to gain an advantage over other players) and the following evening of the playing field done by myself, and the following increase in the use of this hackpack across Tribes 2. I made a significant miscalculation in how far I was in creating a server side anti-cheat; insufficient testing and a bit of bad data made me thing I was closer then I actually was, ultimately leading to a dead end I didn't anticipate.
With the relaxed requirement of creating a client side download I have been able to develop a 100% effective countermeasure against HM2. I am prepared today to release a proof of concept to settle any doubts about my intentions. This is a public beta designed to show it is indeed possible, and can be implemented on any currently running server, usually without any compatability issues. It has not gone though the refining that the initial player targetted release will go though, there are a couple things half implemented, but the barebones are ready.
The beta is set to expire(it will cease working) 2 weeks from the 29th of Febuary, 2004 on March 21st 2004. It is specifically designed as proof of concept. Release version will be completely self functional. Configuration will be minimal, global cheat ban system will be implemented, both the client and server pieces will automatically update as needed. The goal of this anti-cheat being to be minimal hassle, maximum transparency, and forget it once it is installed.
Implemented in this beta proof-of-concept release are: authentication, forced to be stuck in observer unless authenticated, HM2 detection alert, and auto boot and 60 minute ban from server.
Anyway, on to the tutorial:
For server operators:
1) Download FFT2AC_SS.vl2 from
ftp://absolous.no-ip.com/FFT2AC_SS.vl2.
2) Place it in Tribes2\GameData\{mod directory}\ and launch server as usual. As soon as all the scripts are loaded you will get a set of messages in red text starting with "FFT2AC:" and a couple informational messages.
For players:
1) Download FFT2AC_CS.vl2 from
ftp://absolous.no-ip.com/FFT2AC_CS.vl2.
2) Place it in Tribes2\GameData\base\ and play as usual. You will now be able to play on protected servers.
I would like to note that this is an ongoing work in progress still in development stages, but this is fully functional in respects of the implemented aspects.
Those idiots are the reason happymod first got released. And then they had the nerve to blame the superior clan that always beat them S S A. Virus Horray4boobies Hellspawn Elvis Presly Tiki All those cheating asses forced thyth to make an anti cheat the fruit cups.