Jump to content

thane98

Member
  • Content Count

    149
  • Joined

  • Last visited

Everything posted by thane98

  1. Yeah I think you have the wrong folder. It looks like you set your Extracted RomFS folder and output folder to the same place. Do you have a dump of the game? Have you extracted the romfs so you have the game files in a folder? You can do this in Citra. Extracted RomFS folder should point to the directory of your game files. There should be other folders inside of it like "bs", "GameData", "sound", etc. The output folder is where Paragon should save updates. Generally you make the location where Citra will read your modded files from or somewhere similar for Luma. But main thing is to not point it your rom files since that will overwrite the original data.
  2. Paragon went through a rewrite a while back and import/export hasn't made it to the new version yet. You can use this version or any earlier version if you need to import/export JSON patches.
  3. For editing single sounds, this section in the wiki covers it: https://github.com/thane98/BCSAR-View/wiki/Editing-Sound-Sets For the error, have you set up any tools do wav <-> cwav conversion? The tool doesn't have a built in way to do this yet, so you need to configure another program. Wiki: https://github.com/thane98/BCSAR-View/wiki/Setup#wav---cwav-conversion Subtitles are probably in the m folder of the ROM. You could edit these directly in Paragon, but for this it would be easier to use FEAT: https://github.com/VelouriasMoon/FEAT/releases
  4. Very likely that you have two entries with identical names which isn't allowed by the format. Quick fix is to get rid of the identical names.
  5. Paragon doesn't support DLC directly - you would need to drop the files into your project or the base game's RomFS. DLC's also a pain to work with in general, so I don't remember the process for dumping and modding it.
  6. Currently the only option in Paragon is the Dispos module. Multis tab -> Dispos -> Select File. You can edit everything there but it will be clunky since there's no way to visualize enemies on the map. 3DSFE has a full chapter editor with the map layout, sprites, etc. but we're still mapping out most of this for FE10.
  7. This takes a fair amount of work since you need to modify the bcsar (sound archive) and then set up sound sets for the ported voices. For the first part, I wrote BCSAR View and the wiki has an article on how to import sounds from another game. Sound sets can be managed through Paragon.
  8. This usually means one of the following: Your RomFS directory is not set correctly. It needs to be pointed to an extracted RomFS. The folder you point it to should have subfolders like "asset", "bs", "GameData", etc. Your game dump is incomplete. Verify that your extracted RomFS has the file indicated in the error message.
  9. I responded on Discord where you were asking about this - ping me there if you need more help. It's a binary file, not a text file. You should be able to execute it from the terminal. If you get a permissions error, you may need to add execute permissions with chmod.
  10. For most games, this isn't included in the character data. You can change starting inventories by editing the character's spawn in the dispos (Multis -> Dispos from the main window).
  11. Gen 1 units should swap access to a gen 2 unit. So if Leo and Gunter swap places then Gunter should unlock a child unit when he marries while Leo should not. If that isn't happening let me know the seed and I can see what went wrong.
  12. I can spend some time looking into this when I set up the FE10Battle module. I'll put together some steps for adding the unused weapons.
  13. I want to say the infinite uses flag is for weapons like Falchion. My guess is that IS never set up that flag to work for consumables.
  14. 1. Good to know. For music configs, main question is what prefix the EU version uses for localized files. If it's still "e_" for EU, this is an easy fix. 2. Thanks, I will update that module to say movement cost data. 3. I'm pretty sure Paragon's loading and displaying every entry in the items table - I'm guessing the assets are present but there isn't an item entry for it? In that case you could create entries for both items in Paragon. You may need to give it an AID entry in FE10Battle as well. Paragon doesn't have a module for this yet, but it will in the next release.
  15. Any NA or JPN version should be fine - I haven't looked at the EU version yet, so Paragon may be missing support for a couple languages in that version.
  16. The data files. You can extract them from the ISO using Dolphin.
  17. As far as I know stats are signed, so min value = -128, max value = 127.
  18. - You should be able to copy character data using Ctrl + C, Ctrl + V - Not sure about this one personally, but there are people in the 3DSFE modding Discord that could help you do this. PM me your Discord ID if you need an invite.
  19. No Discord for the randomizer, but there is one for general 3DSFE ROM Hacking. If you're interested in that, PM your Discord user ID and I can send you an invite. I don't have a video for the randomizer and I'm not much of a video creator. It's possible someone else has made one though. That last line in the "Caused by" section is what you want. Ignis looked for the file in two locations: D:\Program Files (x86)\Games\Randomizers\Fire Emblem\Fire Emblem Fates\Randomizer Files\Randomizer Game\asset\ROM2.lz D:\Program Files (x86)\Games\Randomizers\Fire Emblem\Fire Emblem Fates\Randomizer Files\ROMfs File\asset\ROM2.lz Based on that second path, I'm guessing "ROMfs File" only has your romfs.bin file? You need to extract the contents of that file and point Paragon at that. You can use something like https://github.com/evandixon/DotNet3dsToolkit For reference, the ROM directory you select should look like this:
  20. Paragon doesn't manage script files yet, so I wouldn't expect them to show up in your project or anywhere in the UI. If you need to edit them you can use Exalt. General approach is to take the script you want to edit from your extracted RomFS, put it in the same location in your project (ex. put it under {project dir}/Scripts/C/C027.cmb), and then open it in Exalt. Still looking into this one. Main issue is reproducing this reliably. As a short term fix I may take this out of the chapter editor since most people don't need to edit landscape anyway.
  21. You downloaded the source code, not the release. You want FEAT.zip from this page: https://github.com/VelouriasMoon/FEAT/releases/tag/v2.6
  22. To be clear: You only need to build if you are trying to modify the randomizer code or run it on Mac/Linux. This looks like you downloaded a release build, so run ignis.exe instead.
  23. It's an issue reading the file, usually it's one of two issues: The paths you chose are wrong. Check if the file it's looking for actually exists at one of the two paths. There's a permissions error with reading the file. This is a rare issue, but best suggestion I have is moving the extracted RomFS to a different lcoation.
×
×
  • Create New...