Server Anti-Cheat Software

[TeaLeaf]

1. Server Anti-Cheat Stuff

This is becoming increasingly important and I think we all need to know where we are going with this ASAP.  We are currently running an 'insecure' server with no anti-cheat stuff loaded.  What are we planning to have loaded in the big dMw scheme of things (I also have in mind here the #D2W challenge, a Clan who run 3 anti-cheat systems that provide each player with a healthy 60-off choke level  8O ).

TL.  

[TeaLeaf]

Bump.

Can someone in the know please provide an update on what is going to be the master plan please?  

TL.  

[Stryker]

ask oldie, hes in the know.... dont worry your pretty little head, we are on the case.... ah I may have some time today oldie.

[OldBloke]

TL et al,

Stryker has kindly agreed to look into the way our servers are setup on Blackadder. Let me (try to) explain.

At present we have both Meat Hook and Baldric running out of the same directory (HLDS_1). This means they have to share two very important config files:

1. server.cfg
2. Mapcycle.txt

The server.cfg file is run by the server on startup AND after every map change. It should contain all the server cvars including things like server password, server name, startmoney etc etc. However, we want (amongst other things) our two servers to have different names. So by some clever use of autoexec.cfg files these cvars have been removed and placed elsewhere. Which is all well and good but there's a reason why they should be in the server.cfg file. The HalfLife server (HLDS) is not very robust so by resetting all cvars at every map change via server.cfg gives the best chance of a trouble free server.

The mapcycle.txt file is as you've already guessed the file that controls the mapcycle. In our present setup we cannot run a different mapcycle on each of our servers.

So. What Stryker is going to attempt is the creation of a HLDS_2 directory in which will reside Baldric and all his config files.  

To further complicate the issue we also run something called halfd. This is extremely useful in that it allows an admin to stop and start the servers using remote access tools. This would be necessary after a mapcycle change for example.

With regards to anticheat measures: we cannot run VAC under the present setup. I've tried and it doesn't like it. Hopefully all will be well when the Siamese servers are no longer cojoined. We may then experiment by running a different anticheat measure on both servers to see which one 'fits' best.

If Stryker is successful then it will then be possible to set up each of our servers as we want them. It would be nice, for instance, to have Clanmod back on Baldric and Adminmod on both. We could also then look seriously at installing the mod that allows access to registered WONIDs only.

Sorry for the longwinded reply but hopefully I've explained a little about the problem and how we intend to deal with it.

Any questions? Tough  :twisted: