pokemon crystal emulator messes up the time

POKEMON CRYSTAL EMULATOR MESSES UP THE TIME CODE

This means that the graphics of trainers are gotten from address 0x4A * 0x4000 + (0x4000 -Ġx4000) = 0x128000. If you open pokemon Crystal rom file with Gameboy ASM Editor and go to address 0x5120d where this routine starts, you'll notice that the bank byte loaded into a is 4A and the pointer loaded into hl is 4000. If you pay attention to what is going on there, you'll notice that it loads the BANK byte in register a on line 329, and hl with pointer to the trainer image pointers on line 319. This routine is used for finding the image of the trainer you battle against, and it calls a few other routines for eventually de-compressing the image. A similar thing is done with all battle sprites in GSC because if they were in uncompressed format in the rom, they would take a lot more space. The text file is now basically compressed, and it can be de-compressed with some de-compression routine that is run when you tell the zip-file to Extract the contents inside it. You can for example have a text file of size 1.5MB, and when you compress it inside a zip-file, the size of the zip-file could easily turn out under 1MB. This is basically the same thing as what can be done with zip-files for instance. Even so, there is no guarantee the program won't break something else although in this situation I tried, it seemed to work otherwise just fine.Īll the battle sprites in the game are actually in compressed format, and they cannot be edited with TLP. This can be done by simply removing the text string lines and just compiling the stuff you want to edit at the moment. In other words, if you feel like using pksv for script editing in Crystal, make sure you at least do not compile text strings with it. When I compiled the script, the original text data was shown in pksv, and it re-wrote that strangely so that pksv apparently put another 00-byte in the beginning of each text string and thus 'messed things up'.

The subscript compiled correctly and the ending byte was 91. I replaced the setbit1 0x14 command with 2call 0x7FF0 and moved setbit1 0x14 into the subscript I called. I personally checked with a tool called 'IPS Peek' what happened when I compiled this same script after editing it. If you need to do more script editing afterwards, you can use pksv, but you need to be certain, what it is doing. If they're not shown, the script data will probably compile correctly although it shows lots of error messages when compiling (= those unknown command 'commandName') for me as well.īut I'd edit the script with a hex editor myself if I were you. Apparently pksv for some reason 'breaks' the text data when you compile a script with it when text data is shown under those '#orgs' below. Then try de-compiling the script with pksv and see if it should work properly.

POKEMON CRYSTAL EMULATOR MESSES UP THE TIME CODE

There you can write '33 14 00 33 BE 00 90' (or 91 instead of 90 if that is the 'end' code in Crystal). You can for example replace setbit1 0x14 with 2call command by searching for '33 14 00' and re-writing it with '00 xx yy' where xx yy is the pointer to the called routine. This can be done easily with a hex editor like seen here: What you can however do is to replace one existing 3-byte command (for example, one of the existing setbit1 -commands) with 2call and at you can write the setbit1 -command you replaced and setbit1 0xBE for the effect to take place. Nevertheless, you can't simply input that script command (which is actually 'setbit1 0xBE') anywhere you like since there is no room for extra bytes. I haven't personally used pksv with Crystal though, so it might not work. Strange that you're getting errors just as that. I've literally spent all day messing around with this to no avail, so hopefully someone here can help. However, he has the original event with the woman in the poke centre, so it may be completely different in his. I've tried opening up another rom file, which includes the GS Event (Pokemon Emu edition) and can't seem to find anything around the offsets kurt is linked to. It seems to overwrite this byte once the game starts. If I alter the rom file using TranslHextion, it does not recognise it. This only works in game though through the memory viewer. I've found what I need to change and what to change it to (Change the byte at xDA89 to 40). The problem now is getting kurt to recognise it. I've managed to include the GS Ball as a reward for a new post-post-game event in my Crystal Hack. As it is now just about this thing, I've created a new topic as not to muddy the other one. I started talking about this in another topic on the back of the running shoes query.

Pokemon crystal emulator messes up the time