FEditor Adv text editor help

[Peter The Cool]

So how come ever time i modify a text, the rom gets way bigger?

[Brendor]

Because you're adding data to it?

[Klokinator]

Essentially, to put this in laymans terms, the rom has a ton of unmodified, encrypted text in it. FEditor works by taking encrypted text that you edit and pasting it at the end of the rom, but now as unencrypted blocks of text. Open up your rom in a hex editing program, and you'll see a bunch of text that doesn't exist in a vanilla rom when you scroll down to the end.

Edited September 27, 2014 by Klokinator

[Peter The Cool]

I see, so should I unencrypted all the text to manager space? Sorry for all the questions.

[Klokinator]

No, just edit text as you desire and FEditor will only unencrypt what needs to be unencrypted, in order to save space. It has fairly efficient auto-management IIRC.

However, do be careful when you use find/replace in FEditor. Camtech told me once that it effectively doubles the space your text uses in the rom's memory.

Edited September 27, 2014 by Klokinator

[Brendor]

All the text in the vanilla game is represented using a Huffman tree but FEditor Adv autopatches an AntiHuffman patch makes all the text follow the ASCII character set. You can replace the old text data since it's not being pointed to anymore if you change it. (I think that's what you're asking..)

[Peter The Cool]

Ok, one last question will Feditor use 0x00D00000 to 0x00E00000 free space or dose it add ever thing to the end of the rom.

I hope it only add to the end, so i can use the free space.

[Brendor]

Feditor allocates whatever free space is available

To see where your text ends up you can search for it in a hex editor or go to that slots entry

[Peter The Cool]

thank you both

[Chocolate Kitty]

Feditor allocates whatever free space is available

To see where your text ends up you can search for it in a hex editor or go to that slots entry

This is misleading; feditor will default to the end of the rom. If you specifically allocate space, it will write there. If you de-allocate space, it will not write there. Meaning that if you want feditor to write in the region 0x00D00000 to 0x00E00000, you'd need to tell it to(and once it runs out of space there, it will jump back to the end of the rom).

"Delete" is what you use to allocate space, "De-allocate" is obviously the opposite.

[Aleph]

that region is marked as free by default so you DON'T need to explicitly tell it that unless you A) hacked the ROM outside of FEditor and fucked your metadat or B) just plain fucked your metadata

compression != encryption

FEditor frees the memory used by obsolesced text to minimize the growth that occurs

there's probably loads of semantic and syntatic catastrophes I can't be assed to addressed up there and

the short of it is, if your ROM is over 16 meb just from editing text, you did something wrong. Read the doc.