kleenexfeu

I don't understand, I'm "replacing" this 8 bytes with the goto command

wait, did you actually re-write this 8 bytes at the end of your routine?

I think I'm doing it wrong since I'm deleting 8 bytes to insert it

but we're replacing some hex to insert it, is it ok?

About it..., I guess it's like callasm right? I'm asking what we're overwritting to insert it since we can't write it inbetween the codes

I always do this silly mistake, ahaha. And most of the time this is reason my routines freeze while testing xD

48F88 isn't a routine. It's a table that corresponds to all the individual routines after status. So the individual stat change routines will be in there. The bank will likely be loaded in there.

Kleenex! The table I wanted to find before (which has all the routines of the setbyte effect that you found) is at 48F88. It loads the routine from that list depending on the byte you have. So that's where Wrap, Knock-Off, Petal Dance, Recharge etc. etc. are. That's probably the best place to do your stat reversals for Contrary for that effect chooser.

Check out Jambo51's thread on Adding New Moves thread. Look for Doesntknowhowtoplay and Chaos Rush's posts for the second routine modifications or fixes. For Emerald, check out my conversation with either MrDollSteak or KDS (and I believe that the EM offsets are in the same thread too)

The routines I'm talking about that will support moves past 512.

You seem to be good at ASM routines. XD Wish you can help me out in the Adding New moves second routine problem. :3

What exactly is this choice specs you speak of for emerald?

Hmm. Actually the offset x49c04 was wrong it should be x49c8c (so restore the original content of 49c04 by seeing the value in the original EM ROM, and at offset x49c8c put the pointer of the first battle script).

Also according to your table your setword will be FA. And also the string at A204F0 should be terminated by Ff otherwise a infinite loop will happen and game will crash. Going to edit the original post to corrction in the offset.

I'm know sendung you VM so that it does not affect the problem. Actually, i did not test the emerald version yet. Could you send your offsets here so that i can identify it.