There were two things I had to do, change the client so it could join RtCW 1.0 servers and change the server so it would pose as a normal 1.0 server.

In order to make the 1.3 server binary compatible with 1.0, I had to bypass the protocol check. This protocol check prevented the client to join servers with a different protocol. I used OllyDbg to find a specific error message, ‘ERROR: Protocol Mismatch Between Client and Server’. When I found the message, I merely had to change the assembly instruction which was responsible for comparing the two protocols(client/server) to always return true. This way any client would be able to connect to the server. Lastly, I had to change the version and protocol so it would register to the masterserver as a 1.0 server.

The client was a bit easier, it would only need to get a different server list. This was achieved by changing the filter RtCW sends to query servers from the masterserver.

After a couple of trials, S4NDM4NN and AG3NT asked if they could help out and they took over the project and added additional features and offered a central place for the community.

Despite the fact it was working fine, people were not keen in using it as some people experienced lag with Punkbuster.
We also found out people generally don’t like change. This RtCW 1.0PB meant they had to download new binaries from some website, which many people simply didn’t want.

WolfTV is a streaming server which allowed an large (if not unlimited) amount of players to spectate a live match.
Without WolfTV, you wouldn’t be able to accommodate that many players in one gameserver.

The original version he created was not compatible with Return To Castle Wolfenstein 1.0.
Despite its flaws, there were still alot of players which played RtCW 1.0 and also in a competitive way. One of these players, Orange, asked me to see if we can make it work for RtCW 1.0.
After some debugging with OllyDbg and trial and error, I managed to bypass the protocol check and change some information sent on connect and to the master server.
This resulted in a working WolfTV server for RtCW 1.0.
Unfortunately after searching for a while, I was unable to find any binaries.

The result is a simple client hook which;

• generated a GUID from the player’s hard drive
• scans the process list for known injectors
• scans the loaded module list for known cheats
• scans for known activated cheat variables
• sends a list of client variables to the server

Once the client has analysed the player’s instance, it would send the result to the server.

The Mousetrap server would then kick and ban that cheating player by GUID by sending it to the back-end.
Besides checking the players for cheats, the server would enforce a variable limit to the 4 variables known to be used for warping or misuse;

• ”cl_maxpackets”
• ”rate”
• ”cl_timenudge”
• ”cg_shadows”

In hindsight, the server was a bit messy and not super secure (although the data was obscured). I also changed tactics, instead of using QMM, I created a “Frankenstein library” which did the same thing as the client hook, but now for the game mod on the serverside.
The back-end was a collection of simple PHP scripts which was connected to a MySQL server.

I did this project in 2009 and I wasn’t the experienced developer I am now so it was all a bit messy.
The setup worked quite good but people were reluctant of installing it because it meant they had to manually install stuff. Also most of the server admins didn’t want to cooperate because they were scared of losing players. In the end I shut the project down because there wasn’t enough interest in it and I started with the RTCW 1.0PB project which worked better anyway.