Page 2 of 2

Posted: Wed Nov 24, 2010 3:17 am
by Astronomical girl
ooohhh :eek: the game is playing tricks on your minds

Posted: Wed Nov 24, 2010 5:21 am
by Androids101
Attack of the evil brain-washing games lol xd

Posted: Wed Nov 24, 2010 5:25 am
by Astronomical girl
haha :lol:

Posted: Wed Nov 24, 2010 5:27 am
by Dr. Jerk
No offense, but if you're unable to help, then maybe it's better to not post in this thread?

Posted: Sun Nov 28, 2010 4:48 pm
by fafner
I have completed the game, so I had a look it the event test, and of course they are mostly unlocked with the exception of the ones you are looking for :d oh: Since I played the game within an emulator, I was able to have a look in the save data of the game (which are stored in a file on the disk). I am rather sure I have found where the event test state is physically stored in the file, however I think the data are protected by a checksum because as soon as I touch anything in the file the game is reset to blank state (all event tests locked, wherever I modify something in the file). I think it is rather easy to crack it, however, to do this I need to know where is the checksum, and how it is calculated, which requires hours of wandering in the assembly code using a debugger.

I might have an interest in doing it next week-end, but before that I nevertheless need to know whether you are interested in getting the information from an actual crack; maybe you want to unlock it the normal way, in which case there is no need for that mess :p Cracking it may however reveal how to unlock the missing events the normal way, so it is up to you to decide whether it is useful or not ;)

Posted: Sun Nov 28, 2010 6:28 pm
by Dr. Jerk
I don't really mind either way though, if it gets the information, then why not. So if you would like to do that, sure, that'd be great. :)

I'm not so good at hacking roms myself, although what you're explaining is fairly simple to understand.

Should I go ahead and list the numbers that I still am missing? I found some more missing events since then, not sure why they slipped my eyes.

Posted: Sat Dec 04, 2010 12:21 pm
by fafner
Bad news: I thought the processor of the GBA was a Z80, but it is in fact a ARM (I think the Z80 was for the old Game Boy, thus my mistake). Problem is that I don't know this assembly language, and it seems to be far too different from what I know for me to understand what's happening in the debugger (I have seen many operations with 3 operands, while those I know usually have only 2). I will be looking for other solutions if I can, but it will take longer anyway. Sorry :blush:

Posted: Sat Dec 04, 2010 9:11 pm
by Dr. Jerk
If you want to look for other solutions, then go ahead. I'm busy with other things at the moment anyway, so if you want to look elsewhere, then I can wait.