Obfuscation of Game Files

[maplesyrupghost]

Hey!

 

Had an idea. I noticed after 'publishing' our game to a folder, it creates basically the finished product? The option to encrypt all files is a very nice feature to prevent people from extracting files, but they can still easily browse through the archive still. I don't see any other options for that stage so I could be wrong but to me it looks like they get to see pretty much everything that makes up the game. Models, textures, maps, sounds, etc. Practically game spoilers just be looking in the directory.

 

So wouldn't it be a nice checkbox to have at the publishing stage for total obfuscation of the game filenames.

 

For example, at the time of compiling just rename 'AddOns' folder to 'a', and then wherever in the code is a reference to the AddOns folder just change it to an 'a', so that path would be good for whenever it is needed. Repeat the same for all other directories and files, so it's just a folder full of random letters with retaining proper file extensions for the filetypes.

 

Since we don't need to decompile the binary again later, it doesn't matter what is in that executable file as long as it works. We can still always work with our normal directories for when we are creating our project, but when we give the game to the customer it is not only read protected but also disguised.

 

The only argument I could see for the way that it is done now is for patching later.

[Einlander]

This would need a better script editor than we currently have. One that is capable of understanding variables strings and resources.

[maplesyrupghost]

This would need a better script editor than we currently have. One that is capable of understanding variables strings and resources.

 

Exactly I'm sure it can be shoehorned into the code somewhere.

[AggrorJorn]

Practically game spoilers just be looking in the directory.

If a person is looking inside the encrypted game folder and he might see something that is a spoiler I would say it is kinda his own fault.