Tulunk Village

It's made from Power, but there shouldn't be any glitches if patched on Speed...
But still, I guess it would be better to play it on Power, just in case.

I was playing around with the compression/decompression tools. I was able to get it to work, and when I tried to compress them, I got a log.txt and a file called "G0." What do I do with this file? Do I copy this and put it in a hex editor?

What IPS patching program should I use for this?

Blaziken257 wrote:I was playing around with the compression/decompression tools. I was able to get it to work, and when I tried to compress them, I got a log.txt and a file called "G0." What do I do with this file? Do I copy this and put it in a hex editor?

The"G0" file contains the raw binary data that will be reinserted into the game. To use it, you'll need a hex editor. If you want to insert the data, just copy the data and paste it (write not insert) into the rom at the starting point indicated by log.txt. I would have my compression program do this, but that only really works if the new data is the same size or less than the original. If it's bigger, you run into the problem of overwriting other data which tends to cause problems.

If inserting the data becomes too much of a problem, I could make it so the data is inserted automatically if the size is right. Any thoughts?

Jade wrote: What IPS patching program should I use for this?

I personally use Lunar IPS, but if you use VisualBoyAdvance, you can use soft patching just by naming the patch the same as the ROM (except with an ips extension instead of zip or gbc). And of course, make sure "Auto-apply IPS/UPS/PPF" is checked (on older versions, I think the text says "Enable IPS Patching" if I remember correctly).

But if you use Lunar IPS (or any hard patcher), make sure you're patching a non-ZIP file.

Malias wrote:

Blaziken257 wrote:I was playing around with the compression/decompression tools. I was able to get it to work, and when I tried to compress them, I got a log.txt and a file called "G0." What do I do with this file? Do I copy this and put it in a hex editor?

The"G0" file contains the raw binary data that will be reinserted into the game. To use it, you'll need a hex editor. If you want to insert the data, just copy the data and paste it (write not insert) into the rom at the starting point indicated by log.txt. I would have my compression program do this, but that only really works if the new data is the same size or less than the original. If it's bigger, you run into the problem of overwriting other data which tends to cause problems.

If inserting the data becomes too much of a problem, I could make it so the data is inserted automatically if the size is right. Any thoughts?

I tried doing this, but the problem is that the new data (I tried changing a few tiles just to see what it was like) is one byte longer than before. I tried inserting one byte at the beginning then overwriting it, then I noticed there was blank space in the DDD5F-DDD6E range, so I removed one of the 00 bytes to make up for it. Still, no matter what I did, the game would crash when I went to the phone menu screen. My saved data was even erased (though I have plenty of save states to restore this...).

Blaziken257 wrote: I was playing around with the compression/decompression tools. I was able to get it to work, and when I tried to compress them, I got a log.txt and a file called "G0." What do I do with this file? Do I copy this and put it in a hex editor?

Uh, Blaziken. You might want to read the readme file, your question has been answered in there already.

Blaziken257 wrote:I tried doing this, but the problem is that the new data (I tried changing a few tiles just to see what it was like) is one byte longer than before. I tried inserting one byte at the beginning then overwriting it, then I noticed there was blank space in the DDD5F-DDD6E range, so I removed one of the 00 bytes to make up for it. Still, no matter what I did, the game would crash when I went to the phone menu screen. My saved data was even erased (though I have plenty of save states to restore this...).

First of all, with the compressed data all the bytes have to be present in order for the game to read it properly. You can't just overwrite a byte in order to shoehorn data where it don't fit.

Second of all, it sounds like you need more room. This is where all the game's empty space comes in handy. After the block of tiles for the cell menu, there's a lot of empty space at the end of the bank you can move the data to. Just copy it starting at DF15F or after. Of course, you'll need to modify the pointer for the data. To find the pointer, go to the beginning of the rom and search for the pointer address. It will be between 1DE1 and about 1EA0. This is the location of the pointer table for the compressed tiles.

Malias, did you know that your tools (at least the graphics ones) work on the GB game Medarot, too? that's really great.

I can finally change the font!
The game was made Imagineer and Natsume, like Telefang, so it's no wonder that the compression is identical. Expect your tutorial on how to find the adress didn't work - but I found it manually.
Do you think more games use the compression? Maybe it'd be helpful to make a list...

Sanky wrote: Expect your tutorial on how to find the adress didn't work - but I found it manually.

Could I please have the address? I think I can use it to find the required breakpoint for Medarot.

That would be awesome.
There are three addresses I found for now:
20000 - small set of characters, always in memory. Contains numbers and punctuation, along with other characters
20168 - dialogue set: contains pretty much kana. That's what I changed for the naming screen
206F1 - battle set: this one is used only in battles. Not quite sure about the adress yet, though. If it doesn't fit in, don't mind it.