Hiding Bitmap file
Author
I have wrote a tetris, but my tetris graphic file is not hidden and someone can just use them. Is there any way I can hide my 4 bmp file.
I know 2 way to hide it but there are disadvantage
1) Load bmp as resource, but will make tetris.exe file size very large.
2)rename bmp to dat file, but software like QuickviewPlus are still able to view it as bitmap file.
Does anyone got any other suggestion ???
tetris.exe
background1.bmp
background2.bmp
Block.bmp
title.bmp
Put some tag in your bmp files /replace the header to make them not recognizable. When the client launches, you remove the tag /put the original header and then load the file as usually.
You could use some compressed format too, it would uncompress the files during loading time, but it will probably increase loading time too much for the purpose.
But really, I think a simple renaming should be enough for your tetris game.
[edited by - Cahaan on June 3, 2003 6:01:03 AM]
You could use some compressed format too, it would uncompress the files during loading time, but it will probably increase loading time too much for the purpose.
But really, I think a simple renaming should be enough for your tetris game.
[edited by - Cahaan on June 3, 2003 6:01:03 AM]
I wrote an obfuscator for all my image and sound files.
It mangles the data (I.e. adds a PSEUDO-random value to each byte in my file to make it unreadable).
When my game app runs, it reads the file, subtracts the pseudo-random value from each byte, and I have the true file in memory.
I can then create it as a texture/wave/midi file, and make it part of my game.
Also, FYI, even if you do make the BMP a resource, it still will be accessible.
Note that my images are easily crackable, but it deters hackers from wasting time messing with your project. My images are shit anyways, but I did this as a learning experience.
I learned:
1) algorithms that return random numbers with long periods
2) managing BMP/sound files that reside in memory
3) figuring out how to read files from memory (Not as difficult as I thought it would be).
the obfuscator is just a single class with static methods to mangle/unmangle data.
I''d share it with you, bun then you''d be able to get at my game data!
www.cppnow.com
It mangles the data (I.e. adds a PSEUDO-random value to each byte in my file to make it unreadable).
When my game app runs, it reads the file, subtracts the pseudo-random value from each byte, and I have the true file in memory.
I can then create it as a texture/wave/midi file, and make it part of my game.
Also, FYI, even if you do make the BMP a resource, it still will be accessible.
Note that my images are easily crackable, but it deters hackers from wasting time messing with your project. My images are shit anyways, but I did this as a learning experience.
I learned:
1) algorithms that return random numbers with long periods
2) managing BMP/sound files that reside in memory
3) figuring out how to read files from memory (Not as difficult as I thought it would be).
the obfuscator is just a single class with static methods to mangle/unmangle data.
I''d share it with you, bun then you''d be able to get at my game data!
www.cppnow.com
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
