Allods Anti-Hack

So far I tested and seen that many things are stored locally, for example invisible walls in instances that prevent you from taking a shortcut, lua scripts for cooldowns (it adds an unclickable layer for certain time over a button), etc....

The only problem is if you change any of the files you also change its CRC checksum, and than the game wont run.

protect.exe and protect.dll are packed with UPX, protect.dll contains all the CRC checksums (database), and each patch its gets changed with new CRC checksums.

It is possible to make a CRC emulator and/or break the call for CRC checksum, however my lack in assembler prevents me from doing it.


I would really appreciate if we come together to test and break teh CRC check or make an emulator with our own CRC database injection.

The Program doesn't check the CRC checksum.
It check's the filesize (byte).

It 100% checks CRC, try editing some pak file and just changing 1 letter for a different one, the byte size will remain the same however the game will not load because the CRC is different. Unless it checks also for the date the file was last created/modfied.


If you unpack protect.dll you'll see refrences to checksum CRC and a refrence to a local database file they used with CRC checksums for files.


I have attached some documentations about the older StarForce protection method maybe it will help someone crack their StartForce FrontlineMMOG protection.

Quote:

Originally Posted by Yasker It 100% checks CRC, try editing some pak file and just changing 1 letter for a different one, the byte size will remain the same however the game will not load because the CRC is different. Unless it checks also for the date the file was last created/modfied. If you unpack protect.dll you'll see refrences to checksum CRC and a refrence to a local database file they used with CRC checksums for files. I have attached some documentations about the older StarForce protection method maybe it will help someone crack their StartForce FrontlineMMOG protection.

When you change one letter, 8 Bit changes.
1 letter = 8 Bit.

Quote:

Originally Posted by Anfang! When you change one letter, 8 Bit changes. 1 letter = 8 Bit.

1 Letter might be 1 byte, however with a CRC checksum it's gotta match.
Even if the value was changed a byte is a byte. The value of the byte is what is important with a CRC checksum.

However it is not just CRC that runs, it also checks for file size changes, so you are both correct with this matter. The pak files are easy though, if you want to change something inside of Character.pak for example make all changed into a new .pak file keeping the same folder structure as the original, then name it like ~Character.pak so it's easy to find at the top of the list, and it'll override the original Character.pak. This method works for all the texture mods too, I'm nude again ! xD

So try creating a custom pak file for any of the texture/script/icon/cursor/sound files ;)

i mmodding allods uis and skins its not possible to change something in the original allods folder but there is an entry the mods path but u dont have enough access to change something special :(

Quote:

Originally Posted by blinko The pak files are easy though, if you want to change something inside of Character.pak for example make all changed into a new .pak file keeping the same folder structure as the original, then name it like ~Character.pak so it's easy to find at the top of the list, and it'll override the original Character.pak. This method works for all the texture mods too, I'm nude again ! xD

Does it work with latest EU version?
I tried this morning with both nudepatch and autologin but it failed. No CRC check issue, but no modification of the game.