Skeetendo

This is probably not a big issue to fix if you have been keeping backups of the rom. If you haven't, it may be difficult to track down what kind of change to the rom has caused this.

Try downloading IPS Peek from romhacking.net which lets you check, see an ips file of the hack does when you create a patch between unmodified rom (or practically any hack rom during production (= backup)) and the current hacked rom. If you have keeping backups, there won't be that many changes to check, what could cause the bug (if you check from backups, where the bug first takes place and where it doesn't).

If you haven't taken any backups from the rom and have done lots of changes here and there, you might have to do something trickier to find out what's causing the bug like following the routine for those balls, and checking if you have somehow corrupted it.

You haven't used any editor for editing items though?

Last edited by Miksy91 (2016-06-10 19:55:25)

I haven't used any item editor, other than for editing the price of items but that dates back to before the corrupt file. I'm sure of it. I've found a backup that isn't corrupt and it seems to be before the egg  change. Way before.

I have lots of backup gbc files, but I haven't kept a record with the differences between them. As such, I can't tell what change I made that may have corrupted it.

I downloaded IPS peek but it doesn't seem to show differences between the files. I made the first corrupt file an ips, and then opened that along with the rom file that is uncorrupted and there seems to be loads of things on the left side. I assume these aren't the differences, as there are way too many (557).

I don't know where the ball routine is and wouldn't even know where to check. The only thing I could do is play through the entirety of the uncorrupted rom to see what hasn't been added, and then re-add it.

Considering the huge number of backups I have made since that uncorrupted file (about 50), I have probably lost a few hundred hours work. Due to the amount of time it will take to identify what is missing and then re-adding it, I think that this is the end of the rom. Which is a disaster, as I had just finished all the additional tweaks from the beta, added loads more stuff, and I only needed to add the new spritework.

Last edited by Adam (2016-06-11 10:45:16)

It could be that. I use PKSV to view scripts, but never to change. I have accidentally compiled before, but have always reverted to previous backups. It's possibly that perhaps I forgot to load an older version and just didn't notice the corruption as I didn't need to catch anything (since I was testing stuff with a save made after beating the game).

Do you have any idea where the ball scripts are located? I think my best chance is probably to compare the hex coding from the section and change anything that as been altered. I' assuming it's the actual script that has been affected and not a pointer, since it runs the ball throwing animation and then crashes.

Thanks

The pokeball code is here. https://github.com/pret/pokered/blob/ma … s.asm#L103

Oh, I missed your post halfshadow. I'll try hex workshop. I kinda need something that will highlight any differences. If I did accidentally use a rom that had been warped by PKSV then it could be other stuff elsewhere that has been corrupted.

I'll give it a shot though and see if HW helps

Same thing in crystal: https://github.com/pret/pokecrystal/blo … s.asm#L202

I know you aren't using the disassembly, but the addresses are there.

Last edited by comet (2016-06-11 20:41:01)

Good to hear you got the problem fixed!
But yeah - the thing you could have done with backups is to use the most up-to-date hacked rom file that doesn't have the bug in it as "unmodified rom file", and the next backup (where the bug is already at along with all the following backups) as the "modified rom file" and created and ips patch between those two. Then you could have checked with IPS Peek, what are the differences between those files and try to track down the "corrupting data" that way, and just apply this fix to your "main" hack rom file then.

Last edited by Miksy91 (2016-06-12 17:25:42)