I had thought the “swap-variant” command might take care of this, but apparently, this isn’t the case. =(
If you really want, you can just directly set the “basename” of an item to “records/items/materia/compa_frozenheart.dbr”. That should work.
Just in case you’re interested, that basename was located by using the following command:
> q value~"frozen heart"
3 things showed up, one was a blueprint, one was a relic, one was a skill.
I guess it would make sense to extend the “swap-variant” command so people can pick between choices with the same name if the editor were to pick the wrong thing for them. But I don’t seem to have the bandwidth to deal with this at the moment. =(
can this tool be used to edit what quests you have completed ?
i fucked up my chars quest progression (and i was having the time of my life playing too, had just gotten to fort ikon) anyways…
i really wanna put my char back to exactly where he was at fort ikon and continue doing the quests and complete the game that way, i fucked up trying to add 2 weapons (i just wanted to get 2 cool looking swords for my char using GD stash) and it completely fucked up my quests putting me back in devils crossing, any help is greatly appreciated…
maybe someone have a char that is at fort ikon and could give me thier save file??
Quest progress is not saved in the char file, so I doubt the tool can do this.
Are you using cloud save ? If so, only make changes while GD is not running. I assume you do because this kind of thing never happens with local saves (as quest progress is stored in a file GD Stash does not even read, let alone write, this must have been cloud save).
Unfortunately, this tool does not let you edit quest progress. =( There was an attempt to do this some time ago, but it looked a little too complicated after some investigation.
Anyway, I’m pretty sure GD stash makes backups of your character when it makes changes to it. You might want to look in your save directory and just manually revert to the last backup.
it is rare, I’d say it is inpossible for this to be an error in the tool writing the file as it never actually does touch it, but cloud save works in mysterious ways and sometimes does this when the save file is touched with an external tool.
No idea what triggers it, but not having GD running while making changes seems to prevent this. Something to also keep in mind when using the char editor
Not at the moment, I’m afraid. It does expose data that records which ones are unlocked. However, they appear to be some kind of binary identifier that I never tried to make sense of.
