To find such a spot, first search for a "!Freespace = $XXXXXX" or "!FreeROM = $XXXXXX"(note that freespace and freerom are both the same thing) Open up the patch you want to insert into your rom, and find the spot where you have to set the freespace This is not really relevant, but you might want to avoid using freespace that has a size below 0x1000 The Size tells you how many bytes the freespace consists of(in hex). The LoROM offsets are, as stated in the text file itself, what we need for the xkas patches The PC offsets are for the specially interested(aka you wont need them if you just want to insert a patch) Each line consists of three attributes, "PC offset", "LoROM offset", and "Size" IMPORTANT: The "LoROM Offset" is what is entered in xkas as free spaceĮach separate line in this list is a freespace. There you should find a list that looks somewhat like this(my list is taken from a 'clean' rom expanded to 2MB):Ī total of 0x16C818 bytes of free space were found smc ", where desides how large(in bytes) a freespace must be for it to be listed in the text file, but that isn't really necessary) (alternatively you can use command prompt and input "slogger. Drag and drop your rom over 'slogger.exe'. It must be a rom that has been edited by Lunar Magic(and preferably expanded to at least 2MB using Lunar expand or a newer version of LM) Put the rom you want to patch to in the same folder. Download smkdan's "free space logger"(also known as "Slogger") here, and exract the zip to an empty folder. With all that said, lets get over to the important part! Luckily we have the handy tool "Free Space Logger" which does this for us =D However, keping track of which freespace you have used, and how many bytes are left in each is a very anoying task to do by hand. In reality the freespaces are not slots(like A, B and C), but amounts of bytes.Īnd patches only use a certain amount of bytes, which differs from patch to patch(one patch might use 40 bytes of freespace, while a second 400)Īnd if you have a patch hat needs 200 bytes of freespace, and set to a freespace which is 800 bytes large, you will still have 600 bytes of freespace left(which you then can use on another patch) What you have to do is to change "Patch 2" into "Patch 2", so the rom won't crash when you insert it. This will make the rom crash because A is not a freespace. Here is a very basic(although somewhat inaccurate) example to show you why several patches can't use the same freespace:Īnd you want to insert the following two patches:Ī is now used up and is no longer a freespace This will crash your rom because once the freespace is used by a patch, it isn't free anymore, and should not be used as freespace in another patch. You will generally need freespace when you want to create an xkas patch that adds aditional effects to the rom(often not needed if it is just a simple modification or removal of an already existing effect)įreespace is therefore generally used in patches, and it often occurs that several patches use the same freespace. If you happen to not give a damn about the explanation, and just want to learn how to set it, jump directly to section 2: How to set Freespace.įreespace is a row of bytes in the rom file that are not used by game itself(i.e. The below is a small wall of tex that in simple terms explains just what freespace is, and why you need to set it. It is however horribly outdated(expects you to use a hex editor even >_<)Īnd as I was tired of having to retype all of it each and every time someone wondered why their rom crashed after having inserted a patch, I decided to just make a damn tutorial that I could simply link to. Yes, we already have another tutorial about this. This Tutorial covers all the steps needed to successfully set freespace and avert getting blank screen of death
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |