Even compiling code to the native machine won't stop a determined cheater. Look at the fiasco Diablo was. Most serious cheaters have access to SoftIce and modify the code as it's executing.
We experimented with obfuscation briefly. We discovered that it was far more difficult than it was worth. But since most of the work we do is server-side, the end user doesn't have a chance to make modifications that would compromise the system. Some take an entirely different approach. Since the cheaters are going to exist, give them tools and turn them into mod developers. ----- Original Message ----- From: "Toby Stephens" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 19, 2002 5:43 AM Subject: [JAVA3D] Game Distribution - Securing Code > Hi guys. > > I realise this isn't really a java3D question, but a lot of you guys are > using your java3D to develop games, so I wanted to run this by you ... > > I have a game that I'd like to send out to a few pepes to play-test with me. > I can see one of these geeks that I'll send it to decompiling the code and > changing a few classes to cheat :) > Relying on obfuscation is just not giving due credit to the patience of a > game hacker :) > > How do you chaps protect your code against against being decompiled ? Is > there a method you use to compile the whole thing into an .exe ? Do you > compile resources in too ? > > Cheers > > Toby > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the body > of the message "signoff JAVA3D-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
