ROM Hack GUIDE to Implement a custom FE:Fates Support FAST (No hex editing!)

xTiredx

Member
OP
Newcomer
Joined
Jun 4, 2017
Messages
10
Trophies
0
Age
26
XP
73
Country
United States
Hey there guys, previously, implementing FE: Fates supports could take hours, due to the amount of hex-editing and copy-pasting involved. Now, it can be done much quicker due to the various tools available.

0-YaOr5XNU5r7VpRE9V5xPllXEPHxpN0eSjDgooL93IDkXCjXPHkMiXRAWTjO0Wflv_S5UDAy4YynPxfLto3swUvt9DQhej5KoUrS3UMOvpl8GSzn1yx2n62Ipp8vEFFhnCEEB28
36rqSdVhliXQ2QZGss3OB70yw4UyMhUgjyQ9bR7M0T3T4LTdXpUiCRjYHYa3qlu18J9IQNw_vxm91SgpaO__T87-nJAAeZQONJj_ECSycok7GjgSXwSbNQ3vC0Qljf8h17Nn1s19
A3IFvBn9uRC1MGzTsl73-FUr5dEJUSb9s1_9qtwJBIeiaQ3f8pV0so19EAabkr3PCRGJ1vexqO3LSeQYO39NXQRH-Ot1_UqKCaAiGhPTI1fBOq8sfZ_z20EGDPXLAygBKKU0Rrlh


(NOTE: I did not make any of these tools)
TOOLS YOU NEED:
FEAT
Fire Emblem Fates Support Editor
Fire Emblem Conversation Editor
Fates Core Resource Pack
Fates BGM Pack
Luma3DS
[OPTIONAL if using Gay Fates AND making full C-S support] A dumped 3DS cart
[OPTIONAL] Gay Fates Hack

NOTE: It is highly recommended, but not required, to make a seperate folder to manage all these files.
PT. 1: Adding Support Options
  1. Inside your Decrypted ROMFS folder, navigate to Gamedata and copy the file GameData.bin.lz
    1. If using Gay Fates, just use the GameData.bin.lz file provided in the NTR CFW version or the All Paralogues Unlocked version, depending on which you prefer.
  2. Extract FEAT and open it.
  3. Drag and drop GameData.bin.lz into FEAT.
  4. You will get a file called GameData.bin
  5. Extract and open the Fire Emblem Fates Support Editor
  6. Open GameData.bin in it.
  7. Make the necessary edits and save.
  8. Drag and drop the modified GameData.bin into FEAT to get the final GameData.bin.lz
PT. 2: Adding Support Conversations.
  1. Extract the Fire Emblem Conversation Editor, the Core Resource Pack, and the BGM Pack.
  2. Move all the files from Core Resource Pack to fe-conversation-editor-1.2.1\resources\global
  3. Move all the files from BGM Pack to fe-conversation-editor-1.2.1\resources\global\sound
  4. Open fe-conversation-editor-hw.bat if on Windows, and fe-conversation-editor-hw.sh on any other OS (not sure if it works on Mac).
  5. Go to File->New Support Conversation
  6. Fill in the details and click OK.
    1. Type “username” if you want a support with Corrin (case sensitive).
  7. Follow this user guide here to write your support and add fitting BGM. It’s very thorough and gives you everything you need to write your support.
    1. Remember to ALWAYS add “(TYPE: ONE)” sans quotes after [FORMATTED SCRIPT]. Otherwise, characters will slide in and off screen randomly.
    2. Save often. The support editor is very buggy and crashes occasionally. Make sure you have your work saved so you don’t have to write everything again.
    3. Make sure you type in (HAS PERMANENTS) at the top of the screen, otherwise gender/username dependent text will crash.
PT. 3: Adding the conversations to game.

IF C-A/C-S SUPPORT:

  1. This is easy. Save the file as a .bin.lz file
    1. NOTE: Once you have saved it, DO NOT edit the .bin.lz file in the conversation editor! Only edit .fescript files. This is because the editor often loses information when converting from game language to English, but never the other way around.
IF ONLY S SUPPORT:

  1. In the S-Support Tab, press “Convert to Game”.
TLLnjNLeQ2MbJaBG6xyjo-OyEkRZDxB-dA0u6kqRL3uvAUTVtqSHvmDneUUFjIaFzsgO5RygYR9_qKUK9By_0-qGq_nn7dz94dCotG5Zr0s2U_34kKO6mjAcaSDL34g3sGgWsHtz

2. Highlight everything & copy it.
9ZSHjLcohBhd3w4AWy1Tr0996vxHFDABpLJNLET3BLCQCQ4u8mBugA5x8vKXIGljh_JZilHyMCtOwfhYAb30WdQv0UV0xE6Arsy0k47YrpmtyQx27D5Fp2N3ieXcqSkLp-bhv7qp


3. DO NOT SAVE after you have converted to game. This is so that your original .fescript is intact so you can edit it at will.
4. In your Decrpyted ROMFS folder, find a .bin.lz file in m\@E with the same name as your .fescript file.
a. For example, for my Kaze/Xander S Support, the file name is スズカゼ_マークス.bin.
b. If you can’t find it, you might have put the names in the wrong order. Do a search with the names in the other order because that’s what happened with my Kaze/Xander support.​
5. Drag and drop that file into FEAT. You will get two files: a .bin file and a .txt file. Ignore the .bin file.
6. Open the .txt file and you will see something like MID_Japanesenames_S:
a. E.g: Xander/Kaze is MID_スズカゼ_マークス_S:
b. If you don’t see it, add it in.​
7. Next to the colon, paste your clipboard.
8. Save the text file.
9. Drag & Drop the text file into FEAT.
10. You will get a .bin.lz file.
BOTH S & C-S SUPPORTS:
  1. Make this folder structure on the root of your SD card: SD:/luma/titles/titleid/romfs/m/@E
  2. Rename “titleid” to your specific game’s title ID (use 3dsdb.com)
    1. For example, Conquest is 0004000000179600
  3. Copy your .bin.lz file and paste it into @E
  4. Put your SD card back into your system, hold down Select, and turn the system on to enter your Luma settings.
  5. Enable "Enable game patching" then save your settings.
  6. Launch the game to see if you have the support conversation
(I used KunoichiZ steps for Gay Fates for this as well)

NOTE: If supporting with Corrin, rename any mentions of “username” to:
プレイヤー女 = Female Corrin
プレイヤー男 = Male Corrin
Make sure to rename the filename as well.
The best way to do this is to use the search and replace function when it is in .txt file.

EDIT 1: Formatted better.
 
Last edited by xTiredx,

livipup

Well-Known Member
Newcomer
Joined
Feb 23, 2019
Messages
53
Trophies
0
Age
26
Location
Toronto
XP
144
Country
Canada
8. Drag and drop the modified GameData.bin into FEAT to get the final GameData.bin.lz
So FEAT was able to decompress my GameData.bin.lz, but isn't recompressing it. I have no idea why. Nothing happens when I drag it in or hit open then then go. I tried recompressing with BatchLZ77 instead, but I don't know if that will be the same since BLZ77 wouldn't even work on my original .bin.lz file. It does work, but I'm just not sure if it will work in game since I had to use two different programs to get this result. Also not entirely sure how BatchLZ77 works. It generates a .bin.compressed. Do I just change the file extension to make it work in game?

EDIT: I packed the rom with the BLZ77 GameData.bin.lz and the game works without any horrible problems, so I guess it's fine. Although the new supports I made didn't show up in game even using a fresh save, so idk if the support editor even worked. I guess I could check the hex values to see if the file saved correctly. If it didn't I guess I'll just have to do everything manually.
 
Last edited by livipup,

Nekusaku93

Member
Newcomer
Joined
Jan 7, 2018
Messages
20
Trophies
0
Age
30
XP
159
Country
United States
So FEAT was able to decompress my GameData.bin.lz, but isn't recompressing it. I have no idea why. Nothing happens when I drag it in or hit open then then go. I tried recompressing with BatchLZ77 instead, but I don't know if that will be the same since BLZ77 wouldn't even work on my original .bin.lz file. It does work, but I'm just not sure if it will work in game since I had to use two different programs to get this result. Also not entirely sure how BatchLZ77 works. It generates a .bin.compressed. Do I just change the file extension to make it work in game?

EDIT: I packed the rom with the BLZ77 GameData.bin.lz and the game works without any horrible problems, so I guess it's fine. Although the new supports I made didn't show up in game even using a fresh save, so idk if the support editor even worked. I guess I could check the hex values to see if the file saved correctly. If it didn't I guess I'll just have to do everything manually.

Hi. I've been on the same boat as you (being stuck on turning my .bin file back to .bin.lz). Have you found a way to implement supports in the game? To be honest, I don't even know if me making the custom edits when it was a .bin file worked (the two characters I want to support already have an existing gay C-S support, so I just followed the rules for customizing "existing supports". I looked at my .bin file properties after exiting the program and it said it was modified).
I'm trying to do a Felicia x Azura C-S support that a writing pal and I wrote a few months back, but I'm stuck. I'm sorry to ask, but could you possibly help, please? I'm playing the US Special Edition btw.
 
Last edited by Nekusaku93,

livipup

Well-Known Member
Newcomer
Joined
Feb 23, 2019
Messages
53
Trophies
0
Age
26
Location
Toronto
XP
144
Country
Canada
Hi. I've been on the same boat as you (being stuck on turning my .bin file back to .bin.lz). Have you found a way to implement supports in the game? To be honest, I don't even know if me making the custom edits when it was a .bin file worked (the two characters I want to support already have an existing gay C-S support, so I just followed the rules for customizing "existing supports". I looked at my .bin file properties after exiting the program and it said it was modified).
I'm trying to do a Felicia x Azura C-S support that a writing pal and I wrote a few months back, but I'm stuck. I'm sorry to ask, but could you possibly help, please? I'm playing the US Special Edition btw.
You can avoid this issue by manually editing the supports. There's a guide on how to edit the hex values written by UnassumingVenusaur here. I used FEAT to decompress and recompress my support dialogue files (m folder) and I used BatchLZ77 for my GameData file. Something important to note about the dialogue files is that when you're manually editing the text documents you need to decompress the .bin.lz file to extract a .bin and .txt file, then you need to decompress the .bin file that is created or else when you drag the .txt file into FEAT it won't recompress the .bin.lz file. This will create a new text file, overwriting the existing one, so make sure you extract the .bin before you make any changes to the dialogue. There's also a guide to proper dialogue syntax here that you can reference. It's pretty confusing to figure out on your own since the code parts mostly use Japanese hiragana instead of the English alphabet. (The few exceptions include things like \NU and $k$p which were most likely changed by the localization team to make writing English dialogue easier.) It's also important to watch out for the MIDs. For the most part you probably just have to copy and paste it then change a single character from a C, B, or A to an S, though I do believe that the S used in the MIDs is different from a standard capital S. I compared the Ss in Notepad and the S appeared to be a different font which suggests that it's a special character. I assume the same is true for the other rank-signifying letters as well. It does make sense since the game was designed by developers using Japanese keyboards which wouldn't have English letters as regular characters.
I feel like that's everything you need to know, but if you have more questions feel free to ask.
 

xTiredx

Member
OP
Newcomer
Joined
Jun 4, 2017
Messages
10
Trophies
0
Age
26
XP
73
Country
United States
I don't know if anyone is still interested but my sibling told me that there are still some people who are modding this game so

Can I ask what version of the conversation editor you're using to be able to copy and paste in it? Because for some reason it won't let me do that.
No idea im sorry, the post is from 2017 so check a release from that date?

Thank you!
No problem, have fun <3

So FEAT was able to decompress my GameData.bin.lz, but isn't recompressing it. I have no idea why. Nothing happens when I drag it in or hit open then then go. I tried recompressing with BatchLZ77 instead, but I don't know if that will be the same since BLZ77 wouldn't even work on my original .bin.lz file. It does work, but I'm just not sure if it will work in game since I had to use two different programs to get this result. Also not entirely sure how BatchLZ77 works. It generates a .bin.compressed. Do I just change the file extension to make it work in game?

EDIT: I packed the rom with the BLZ77 GameData.bin.lz and the game works without any horrible problems, so I guess it's fine. Although the new supports I made didn't show up in game even using a fresh save, so idk if the support editor even worked. I guess I could check the hex values to see if the file saved correctly. If it didn't I guess I'll just have to do everything manually.

Hi. I've been on the same boat as you (being stuck on turning my .bin file back to .bin.lz). Have you found a way to implement supports in the game? To be honest, I don't even know if me making the custom edits when it was a .bin file worked (the two characters I want to support already have an existing gay C-S support, so I just followed the rules for customizing "existing supports". I looked at my .bin file properties after exiting the program and it said it was modified).
I'm trying to do a Felicia x Azura C-S support that a writing pal and I wrote a few months back, but I'm stuck. I'm sorry to ask, but could you possibly help, please? I'm playing the US Special Edition btw.

You have to use an old version of FEAT, the most recent version does not work for some reason. I uploaded it here:
https://gofile.io/d/3uRAv9
 

Nekusaku93

Member
Newcomer
Joined
Jan 7, 2018
Messages
20
Trophies
0
Age
30
XP
159
Country
United States
I don't know if anyone is still interested but my sibling told me that there are still some people who are modding this game so


No idea im sorry, the post is from 2017 so check a release from that date?


No problem, have fun <3





You have to use an old version of FEAT, the most recent version does not work for some reason. I uploaded it here:
https://gofile.io/d/3uRAv9

The "gofile" link doesn't work. :(
 

Attachments

  • Screenshot (18).png
    Screenshot (18).png
    90.7 KB · Views: 222

Nekusaku93

Member
Newcomer
Joined
Jan 7, 2018
Messages
20
Trophies
0
Age
30
XP
159
Country
United States
You can avoid this issue by manually editing the supports. There's a guide on how to edit the hex values written by UnassumingVenusaur here. I used FEAT to decompress and recompress my support dialogue files (m folder) and I used BatchLZ77 for my GameData file. Something important to note about the dialogue files is that when you're manually editing the text documents you need to decompress the .bin.lz file to extract a .bin and .txt file, then you need to decompress the .bin file that is created or else when you drag the .txt file into FEAT it won't recompress the .bin.lz file. This will create a new text file, overwriting the existing one, so make sure you extract the .bin before you make any changes to the dialogue. There's also a guide to proper dialogue syntax here that you can reference. It's pretty confusing to figure out on your own since the code parts mostly use Japanese hiragana instead of the English alphabet. (The few exceptions include things like \NU and $k$p which were most likely changed by the localization team to make writing English dialogue easier.) It's also important to watch out for the MIDs. For the most part you probably just have to copy and paste it then change a single character from a C, B, or A to an S, though I do believe that the S used in the MIDs is different from a standard capital S. I compared the Ss in Notepad and the S appeared to be a different font which suggests that it's a special character. I assume the same is true for the other rank-signifying letters as well. It does make sense since the game was designed by developers using Japanese keyboards which wouldn't have English letters as regular characters.
I feel like that's everything you need to know, but if you have more questions feel free to ask.

After I made the .bin & .txt files, I dragged the .bin file into FEAT to decompress it like you mentioned, but it only gave me the message "Successfully Extracted MESS_ARCHIVE_アクア_フェリシア(アクア_フェリシア.bin)." Soon after, I messed with the text in the .txt file before dragging it back into FEAT and got the previous bin.lz file overwritten. I assume dragging the .bin file into FEAT to decompress it didn't work. Dropping it into BatchLZ77 didn't decompress the .bin file either (it gave me a message saying that it couldn't). I'll try again, maybe I missed something?

UPDATE: So I found out what I did wrong. Turns out I was using an old version of FEAT instead of the current one. I'm gonna see what I can do with everything else right now. Thanks for the help so far!
 
Last edited by Nekusaku93,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: @Mondooooo, there was a power outage while you were sleeping?