Removing Asar patches manually

How to remove Asar patches.

If you want to remove a patch, the solution is not to port all of your stuff to a new rom. There's an easier way.

Here's how you do it.
Go to your patch file. As an example, I will be using Ersanio's SMB3 P-Meter. Download.

Now, there are 2 types of edits patches make: simple edits and hijacks. Removing edits is easier, so I will show you how to do that, first.

In Speedbar.asm, you will find the following:

Now, to reverse this:
Count the amount of edited bytes. For the first ORG, that is 20. For the second, just 1.
Then, open a clean SMW ROM in a hex editor. I prefer using shex because of its SNES address support.
Copy over 20 bytes, and put them in a new patch like this, using the same org:


Do the same for the other ORG:


Now, to remove a hijack. A hijack is when there's a JSL or JML into freespace. (anything in freecode comes after a "freecode" or "freedata" command in asar)
First, we will clean up the free space.

Count the amount of bytes between the org and the JSL, plus one. In this case, that amount is 1.
In order to clean the freespace, do the following:

So in this case, autoclean read3($0081EA+1)
After that, count the amount of bytes your hijack uses. In this case, it's 5. (JML is 4 bytes, nop is 1)
Then, look in your hex editor again and place the 5 bytes of that location.

You need to do this (removing the hijack spot, not cleaning the freespace) for each hijack the patch makes.

The finished product should look like this:


This is your Anti-Patch. If you patch this with asar, the original patch will be removed.

Does it work with xkas patches applied with asar with on top ;@xkas???

This is actually quite a good tutorial. It definitely works!
I'll suggest a couple of improvements. First of all, it's worth mentioning that some patches rely on hijacks by Lunar Magic, which might mess stuff up if you copy the original bytes from a clean ROM. If the patch requires that you save a level (or the overworld) or insert graphics or anything like that, it could be a good idea to first do that to the "clean" ROM to ensure you're restoring code which Lunar Magic might've changed.
Also, it'd be good to have a little guide telling you how much bytes the more common instructions take up, as it might be a bit confusing to some. Have a look (yes, I know that dl is not an opcode):

Instruction	Size
JMP	3 bytes
JML	4 bytes
JSR	3 bytes
JSL	4 bytes
NOP	1 byte
BRA	2 bytes
dl	3 bytes

Generally, the opcode itself is 1 bytes and then there's another byte for every two digits of its parameter. Branching opcodes are 2 bytes.


It should, yes. Really all this is doing is cleaning up the freespace and restoring the original code.

Tool. Asar anti!

---

Userbar made by Green Jerry

And for the leaveyoshi.asm how do I unpatch

---

My unreleased ROM hack: Mario Saves Summer