Jump to content

Search the Community

Showing results for tags 'parsing'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Important Links
    • Serenes Forest Code of Conduct
    • Mistakes or Errors on the Site
  • Important Forums
    • Announcements
    • Member Feedback
    • Site Content
  • General Forums
    • Introductions
    • General
    • Far from the Forest...
    • Creative
    • Fan Projects
    • General Gaming
  • Fire Emblem Forums
    • General Fire Emblem
    • NES and SNES Era
    • GameBoy Advance Era
    • GameCube and Wii Era
    • Nintendo DS Era
    • Nintendo 3DS Era
    • Fire Emblem: Three Houses
    • Fire Emblem: Engage
    • Fire Emblem Heroes
    • Related Games
  • Miscellaneous
    • Forum Graveyard

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Member Title


Jabber


Skype


Yahoo


ICQ


Website URL


MSN


AIM


Interests


Location

Found 1 result

  1. Because sometimes FEditor just curbstomps your rom I made an executable parser based on anti-huffman encoding. Needless to say, this method of text insertion requires the anti-huffman patch. This patch is auto-applied if you have opened and saved your ROM in FEditor. (If you'd rather not have FEditor touch your ROM at all, an EA installer for the Anti-Huffman Patch, based on the FEditor version, is here: http://feuniverse.us/t/fe7-fe8-anti-huffman-patch-ea-style/1703) Here's the link: FEU Another Text Parser Thread The usage is by basically making a file with the formatted text, then opening it with the parser. You can also parse a whole folder of text at once. It'll generate a .dmp file and you can insert that in the ROM and point to it, anti-huffman style (anyone got anti-huffman tutorials still lying around?). There's also an executable for parsing all text files in a directory/subdirectories. The newest version also allows declaration of your own directives, such as: (in definitions file:) [LoadEirikaPortrait] = [LoadPortrait][0x02][0x01] (in text file:) [OpenLeft][LoadEirikaPortait]Eirika says hi![A][X] Another example input: [OpenRight][LoadPortrait][0x01][0x01] [OpenLeft][LoadPortrait][0x02][0x02] [OpenRight] Eliwood, let me tell you[NL] about a lost art.[A] [OpenLeft] What is it, o wise[NL] question-mark man?[A] [OpenRight] Once upon a time, before the[NL] time of FEditor, we did text[A][NL] a different way. The anti-[NL] huffman way. This involved[A][NL] hex editing. In fact, FEditor[NL] only automates this method.[A][NL] [OpenLeft] I see. Why are you telling me this?[A] [OpenRight] Since it's what FEditor is based on,[NL] people should know how it works.[A][NL] That way new ways of editing text[NL] based on it can be created.[A][NL] For example, imagine if we could[NL] insert text through EA...[A][NL] [OpenLeft] That sounds like a[NL] useful option to have.[A] [OpenRight] By the way, there are bandits[NL] behind you, Eliwood.[A] [OpenLeft][MoveLeft] Ahh![A] [ClearFace] [OpenRight] Bye![A] [ClearFace][X] And this is the hex output: This can then be pasted somewhere in the ROM, and a text table entry can be repointed to it (add 0x80000000 to the pointer to tell the engine that it's anti-huffman'd). This process can be automated by EA, keep an eye out for a tutorial on that soon!
×
×
  • Create New...