- Mar 2, 2017
- 441
- 2,444
I understand where you are coming from, but they were never my instructions. They were bupos.If you want to quit cracking because of some retards on this site, so be it. It's a more than reasonable justification, but have you thought about leaving instructions for a possible successor of yours? If you don't wanna, it's fine. A good magician never tells his tricks, but think about the users who appreciated your work too and not only about the idiots who cannot (and won't) understand shit. There aren't only dickwads here
156_163_146_167 made a post a long while back with the important information, that or search the posts made by "BupoTiling03-Retired" to get the info. That is all we were really given to work off of. Using that information and a little learning from some google searches nets quite a bit. I can wholly say the way bupo delivered his information was the only reason I decided to even try, not a walkthrough that you follow and don't learn from but just enough to get you on the track to learn it for yourself. I can call this thread my gateway to disassembly, before I had never even touched a debugger let alone cracked a program. While I still know very little about reverse engineering, I have taken what I learned from this and applied it onto other things. As I type I'm trying to figure out how someone managed to bypass a patreon authentication check for another game by pulling apart a dll file. From getting AES keys to paks so I can decensor some japanese unreal games to pulling the password out of the Timestamps game for extracting the images in storage.vngine, I wouldn't have known how to do any of that without this thread.
I am willing to help those that are trying to learn, but I have gotten some stupid conversation starters ranging from the typical begging about a step by step guide to one person who demanded a pdf with pictures explaining on how to do it "or else..." so I tend to look over my conversations with a judgemental mindset.
Shifting focus a little bit, I managed to patch the Ekc6420.dll to punch itself in the face. With it there is no longer a need for creating new exes for the game which means no reason to trigger the reimplemented md5 check. Did I mention it seems to work recursively? Works on older versions of the game, works on the original Fallen Doll game(which has an older version of Eleckey), heck it works on the most recent version of Eleckey(2.0.9.20 as of writing this) at least anything made using the 30 day trial of it... as long as it is 64bit. They seem to have a different approach to x86 programs and didn't bother looking into it.
For anyone else that makes their own exes this is quite easy to do if you dick around the same region you pay attention to when dumping the exe.
Again, only done because I learned something from this thread.
You must be registered to see the links
tl:dr: this post wasn't for tl:dr's