Don't worry about it, you were doing everything correctly - the file wasn't exporting because of a bug with the Awakening dispo editor. I've uploaded a fix, so give it a try and see if the file exports correctly now.
I have a question about the Skill Modules, what does the Stat, Trigger % factor, and Trigger % divisor do? I'm assumed they had to do with the activation trigger of certain skills, but when I open up the GameData in FENightmare to edit these points I notice that they don't match up with what the triggers would be (Sol is 0x3 Magic, 3, and 4 respectively). Did I perhaps mess up or is something wrong with the module?
Since it's sort of aside from features, what about a couple more guides? One for adding a class would be helpful.
I might at some point in the future. But as I said, I'm pretty burnt out on working on the tool at the moment - I don't have any interest in writing guides right now.
That said, adding in a new class shouldn't be too hard. All that you need to do is add in a new class block and class AID. There are injectors for both of those in FEFNightmare.
Hey, first of all, thanks for the update, it's much better. Now, I have some questions: is there a way to remove a support option with the support editor? And how does the indirect sound editor work? In which file do I need to export it?
Hi, I've been using the Fates Support Editor in this for the past two days or so and it's been working perfectly up until now. I can't think of anything I did differently, only that I briefly switched from using the Fates Support Editor to taking a small look at the Awakening Character Editor module in FEFNightmare (after switching the mode to Awakening, even). The problem I've run into is that, in the Fates Support Editor, all characters' names except for the two Corrins have been replaced by their hex id codes. Like, instead of saying Gunter like it did literally yesterday it just says 0x3. I know this is still usable in this state but I've barely ever done any hex editing and would prefer if I could find a way to revert back. (Also, as flagpole343 said, being able to remove support options at some point in the future would be great.)
There's no way to remove a support option at the moment - the support editor uses an injection method to handle adding in new supports without screwing up the file. Doing removal with it is a little bit tougher, so I haven't bothered with it yet. I'll probably get around to it at some point.
Anyways, I think I'm a little confused by your second question. Do you not know which file to open?
The support editor uses a data file to help match character IDs/support IDs with names. You can choose the file that FEFEditor uses for this in the options menu. If you don't, it should default to an internal version - I have no idea why your version is having issues reading the default file. Is there still a file called "FatesGameData.txt" in the "External" folder?
You're looking for "IndirectSound.bin.lz", which is located in the sound folder of the ROM.
Thanks so much for your help. After reading this, I was able to fix it. The options menu (which I swear I don't remember messing with, if I ever did) wasn't pointing to a text file at all, so I directed it to the file you mentioned in the External folder, and now everything is working fine. Also, "Auto Complete" was off when I checked and I turned it on when I fixed the file path, in case that affected anything. It's really weird, considering I removed all of the folders & files and re-downloaded them in an attempt to fix this earlier, and it persisted through that somehow when you'd think something like that would reset the options. Oh well.
You can mix and match up to 2 different animation sets on an AID/JID block, it's a matter of knowing how the bitflags work (which is super complicated).
If the animation set does not exist (like Sword animations for Sky Knight), then you'd need to make a new block in aset.bin which involves Pointer Region 2, meaning with no current tools for that it'd be next to impossible.
For anyone who needed a way to remove supports, @SecretiveCactus was kind enough to implement the feature. The download link in the main post has been updated to include support removal, so try it out if you're interested.
Something odd I noticed when running the support editor is that Corrin's lists of supports are cut off: they go down all the way from Ryoma to Effie, but anyone after Effie on the table can't be edited for some reason. Not sure the reason why
I can't seem to reproduce that on the latest version of FEFEditor - the list of supports for both Corrins displays all characters and allows editing past Effie. Is there anything unique about the GameData.bin you're using?
I made some edits to the GameData.bin file with a previous version of FEFNightmare. It was mostly adding classes, a few units, and weapons. The only thing I think that might've caused that is that I gave Nichol and Candace and a couple of dudes the same support Ids as a few of the kids (since I'm planning on cutting them) but even when I changed that, it didn't fix the issue.
Last edited by king_frost93,
When I go to use the dialogue editor, I always get a message that it failed to decompress a file. Also, when I add text, what ever I put in the box stays there no matter what I click on on the sidebar. Am I just missing something or is something wrong?
Similar threads
-
Xdqwerty
what are you looking at?
-
-
-
-
@
SylverReZ:
@Psionic Roshambo, The Doom NES cartridges, a few batches were made. One was given to AVGN as seen in his Doom video.+1 -
-
@
Sicklyboy:
I finally modeled and 3d printed the new HDD cages I need in order to build my 2nd NAS. Original ones don't fit the mounting holes on the hdds I'm using. Been sitting on this project for over 2 years smfh -
-
@
Sicklyboy:
I'm finally gonna get this NAS racked and powered on tonight, install truenas core, and burn the disks in with badblocks
-
@
Sicklyboy:
Also another 70TB going in the front mount drive bays of this server. 182tb raw, going to probably use a zfs RAID-Z3 for 3 parity disks, so 140TB usable
-
@
Sicklyboy:
I could claw back 14tb by only doing 2 parity disks but I feel like with 13 disks in the RAID I'd be kind of pushing my luck on rebuild time if I encounter a disk failure
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
