ROM Hack [WIP] Fire Emblem Fates Randomizer

  • Thread starter Thread starter thane98
  • Start date Start date
  • Views Views 291,318
  • Replies Replies 1,417
  • Likes Likes 20
Ahh sorry :'D
Maybe there's a way to replace that model with the randomized chara's?
That wasn't a jab at you for explaining btw. It was just a general statement. Sorry if it seemed that way.

And I wonder if that could be possible since all that model did was stand there (it didn't even run off screen to "fix the collar"). I mean, Elise's hugging Corrin model is used for whoever replaces her in that same cutscene, albeit a little wonky looking. Unless I'm getting the two models confused and this isn't possible at all.
 
I didn't test the text files because the file names got corrupted on my end, but everything else ran fine in game. Looking at the text files, it looks like m/GameData.txt and m/GMap.txt were never compressed back into .bin.lz form. Running them through FEAT again fixed the issue. I'll go ahead and include the recompressed versions below if you want to try adding those to your patch.

I'd go ahead and add those back in and see how things run. If you removed those files from a romfs before modifying them, then the crash likely occurred because the game couldn't find them in the modified romfs. If that's the case, then using the recompressed files should fix the issues.


I was planning to swap around which child is assigned to which parent. Tying multiple children to the same parent could be done, but I'd rather not mess with that right now. If you want to get both Kanas though, I think that @DeathChaos25 put together a patch which gives you both of them at the end of Paralogue 2.
Do you know if @DeathChaos25's tool is comparable with yours, or if it will be if it's not already?
[EDIT] also, how to I go about using the files you attached? [/EDIT]
 
Last edited by AtomSmasherMazionga,
That's because that part uses a specific model that is different from Leon's regular model. It uses the "your cape is inside out" model, which is specific to that scene only.
That's why in that part the model always remains Leon.
Actually, the game spawns both models in that cutscene, the regular and the inside out collar.

It just so happens that the regular model spawns and stands off Camera, and the Inside Out collar is the one that can be seen, so when he "runs off to fix his collar", that model runs off to an off camera place, and his regular model will move from where it was to where the inside out collar was within the camera.
 
Actually, the game spawns both models in that cutscene, the regular and the inside out collar.

It just so happens that the regular model spawns and stands off Camera, and the Inside Out collar is the one that can be seen, so when he "runs off to fix his collar", that model runs off to an off camera place, and his regular model will move from where it was to where the inside out collar was within the camera.
Ohhh alright, that makes sense!
 
Do you know if @DeathChaos25's tool is comparable with yours, or if it will be if it's not already?
[EDIT] also, how to I go about using the files you attached? [/EDIT]
Sorry about that, the other files I attached were for @Kobazco. The twin kana patch is compatible right now, not sure how well it will work with child randomization in the future.

And I wonder if that could be possible since all that model did was stand there (it didn't even run off screen to "fix the collar"). I mean, Elise's hugging Corrin model is used for whoever replaces her in that same cutscene, albeit a little wonky looking. Unless I'm getting the two models confused and this isn't possible at all.
I might be able to get that swap working when I put the new script randomization system in place. I'll have to look at the instances where the models do not swap to figure out what exactly needs to happen to fix that.

I'm still working on building a more stable system for randomizing script/dispo files. The code is done for the most part, I just need to integrate it in with the randomizer and ensure that the new system doesn't cause a total meltdown (at least, more than the current one...).
 
Last edited by thane98,
  • Like
Reactions: KunoichiZ
Sorry about that, the other files I attached were for @Kobazco. The twin kana patch is compatible right now, not sure how well it will work with child randomization in the future.


I might be able to get that swap working when I put the new script randomization system in place. I'll have to look at the instances where the models do not swap to figure out what exactly needs to happen to fix that.

I'm still working on building a more stable system for randomizing script/dispo files. The code is done for the most part, I just need to integrate it in with the randomizer and ensure that the new system doesn't cause a total meltdown (at least, more than the current one...).
That sounds good, but what about getting the amiibo units and Anna (or at least the characters that replace them)?
 
That sounds good, but what about getting the amiibo units and Anna (or at least the characters that replace them)?
The amiibo units themselves should be available in the chapter of whatever character they switched with. As for the characters they switched with, you'd have to get access to their recruitment chapters or use something like an edited castle_join. I don't have anything like that in the randomizer at the moment, but I could try and implement something in the next update. If you want access to the chapters on your current game, you can get it by changing the type of those chapters to paralogue using the Nightmare Modules.

I can't really do anything about the character that switches with Anna though since her chapter is DLC content.
 
Last edited by thane98,
The amiibo units themselves should be available in the chapter of whatever character they switched with. As for the characters they switched with, you'd have to get access to their recruitment chapters or use something like an edited castle_join. I don't have anything like that in the randomizer at the moment, but I could try and implement something in the next update. If you want access to the chapters on your current game, you can get it by changing the type of those chapters to paralogue using the Nightmare Modules.

I can't really do anything about the character that switches with Anna though since her chapter is DLC content.
So running Anna on the Run would get us Anna and not the character that replaces her? Which Nightmare module would I need to use to change that?

Or is all this too complicated to do and I should just avoid randomizing Anna in the future? Unless someone has a workaround for the DLC?
 
Last edited by KunoichiZ,
Sorry about that, the other files I attached were for @Kobazco. The twin kana patch is compatible right now, not sure how well it will work with child randomization in the future.


I might be able to get that swap working when I put the new script randomization system in place. I'll have to look at the instances where the models do not swap to figure out what exactly needs to happen to fix that.

I'm still working on building a more stable system for randomizing script/dispo files. The code is done for the most part, I just need to integrate it in with the randomizer and ensure that the new system doesn't cause a total meltdown (at least, more than the current one...).
Oh, I see, my bad. Do you happen to have a link to the twin kana patch? (If my internet can stay on long enough I might be able to use google. The power company is "working on the power lines" which in SC means they're cold and wet and sitting around chatting up women while they cut off people's power for no reason, sometimes more than once in a day. )
 
Oh, I see, my bad. Do you happen to have a link to the twin kana patch? (If my internet can stay on long enough I might be able to use google. The power company is "working on the power lines" which in SC means they're cold and wet and sitting around chatting up women while they cut off people's power for no reason, sometimes more than once in a day. )
I don't, though somebody else might. I just remember seeing it a couple months ago.
 
Last edited by KunoichiZ,
Use the Chapter module on GameData.bin. You should just need to change the chapter type from amiibo to paralogue, but you may have to add a chapter prerequisite if the chapters don't have entries for those already.
Awesome, thanks. Do I randomize the files first then use the modules or modules first then randomize?

For the curious, across all paths, all of the amiibo hero battles need at least chapter 7 completion in order to unlock. So to unlock the paralogue/hero battle, just beat chapter 7.
 
Last edited by KunoichiZ,
Encountered an issue in Rev!Chapter 11. My Corrin can't talk to Saizo's replacement, in this case, Fuga. I'm not sure if it's the Randomizer's work or my files. I also can't recruit Orochi and Reina's replacements as a result. And upon completion of the chapter, the game crashed.

@Darthlink9 You're welcome. :)
 
Last edited by KunoichiZ,
I can't get this to work; where do I put this on the SD card for NTR? Do I have to make a patch folder?
 
I can't get this to work; where do I put this on the SD card for NTR? Do I have to make a patch folder?
You'll need to get the NTR plugin for your version of Fates. For the time being, you can get the plugin from the Same-Sex Expansion patch. That should come with a folder for the patch files.
 

Site & Scene News

Popular threads in this forum