Checking for filenames and common functions isn't sufficient. Stopping evil coded functions like that isn't difficult at all though(they all rely on a fairly common root).

Overriding the DSO wouldn't be advisable. Even with the correct function names, how would the cheater know how to construct the replies to send back? With the 1.1 client, all information sent between the server and client regarding anticheat is encrypted. The information is encrypted using a highly dynamic key system, just overwriting the function would be fairly useless. If you decide to hook onto it with a package, you'd still have to decrypt the instructions sent from the server, all within the 10 seconds required to send the correct information back to the server. The plain to hash conversion itself is over 30 steps in 1.1, versus 3 in 1.0, thus, it will even take Linker a while to determine the steps.

Either way, I think I'll have definitions on the server side, pre-encrypted without functions to encode new commands(thus twarting the encrypt and send malicious commands to users).

I'll work on this plenty in May, starting after the 10th.

Dev, I would like to see those evil functions so I can try and make preventative code(more for unreal than tribes, but its good practice)

well give it to me and see how long it takes for me to determine the steps.

btw dond as a, as you can say, apology, i'll give you a dts model of a m1 rifle... once i get the texturing done.

Ever finsh those missile effects?

anyway, its kind of you to want to give me the dts of the rifle, and i will take it gladly, but it may go some time before its used, because, i dont want my mod client side. unless i get a huge amount of followers like some sort of advertising ... With the new group of people that will come because they can download it. This might be possible for me to make it client side allowing for much more flexibilty in the game so i guess if i ever do make it client side i got a lot of recoding to do ... :/

those missile effects werent turning out right so i kind of left it alone... what i imagined wasnt exactly what turned out...

the rifle though... i'm planning on making a whole batch of ww2 weapons slowly over the months (why? i have no clue) so maybe after i made those weapons they can all be dumped on you at once... along with jeeps and tanks and whatnot...

........you nerds

Someone said my name?

Just AP Physics "B" exam left...

LOL!

just AP US History exam left...

Just implementation of AES encryption left... and that engine failsafe.

christ.....

I've revised my HM2 policy to "shoot and ask questions later" rather then an "ask questions then shoot". I'm running preliminary testing on 1.12b on "XL = Pandora = XL". There are some minor glitches to resolve, a substantial rewrite of the handling of unauthenticated players, and a bit of alteration on the "ask questions later" part.

It is, however, functional. After this bit is done, it will be time to write the obfuscation module to annoy script based locators and the like...

It appears that managing script based locators would be best done on the server side. The client I have currently developed will be fairly final in design, maybe a few alterations in the encryption.

Great, keep up the good work.

%SmacktardCheaters.blowup();