Open wimpyrbx opened 7 months ago
A small addition. If above solution is not implemented or used in the rename function it would be nice if there was an option to make sure files remained in their respective recursive folders.
Like if I already have the nsp files in a folder called "Rain World" in the base folder I want to be able to make sure they stay in that folder and not default to the base folder.
(This point could become obsolete if the first suggestion is accepted though)
Yes using the title id we can relate the dlc and the updates, I already started working on this, not this particular issue but relating titles and dlcs/updates. Next release will be a major release as I'm planing to drop litedb and use sqlite, but normalizing the data is taking more than I anticipated. Once we have the data normalized I think we can address this particular issue easily.
When trying the rename feature I notice that some DLCs do not have {appname} that points to the original base nsp.
Example:
So what I tried to do was to place these in a folder named {TitleName} so the files would be inside a .\Rain World\ folder, however this did not work as expected.
Here is the data for the second file in titles.json
and here is the json data for the 1st file:
So, I guess the reason is that there is no relationship between the two in the json entries?
Just asking if there is a way to combine DLCs to their parent with a {value} in some fashion. It works when renaming with "Switch Library Manager 1.4.0", and I believe that uses the same data? Not sure how it does it.
Maybe it first finds the base version of the game by using it's ID 010047600BF73001 and remove the last 4 digits and make sure all other id's (4 digits removed) connects to that first one?
And then only do the rename on DLC/Updates if you already have the BASE and know where to place them if renaming using {FolderTitleName} (or similar variable) ?