ODF De-Referencer (In progress modding tool)

[Ded10c]

I recently started the ordeal of extracting the new Cerberi from EPIC into a standalone unit, and that's a pretty big job on my timescale. So, after a discussion with N1 about the idea, I've decided to create a program to ease the work of ODF wizards a touch; a program to look through an ODF and finds the keys used to reference other files, then print the names of the files referenced out to the user.

Firstly, do you think such a program would be useful? It's still in early development, but from here on out development is mostly copy-and-paste. I realise a program that is capable of reading dependencies from all BZ-related filetypes (XSI, MSH, ODF, TRN, BZN, etc.) would be fantastically useful, but that would require as much work again for every filetype, if not more. Such a thing is not likely to come about any time soon, and a program that only does one of these filetypes (or maybe two, since I can probably get it to read TRNs as well) is better than nothing.

[MrTwosheds]

Something I would find useful, would be something that did the opposite, searched folders both odf and xsi/msh or other files found their links and then informed me which files were not referenced by any of them. Taking years over a project means you get a lot of trash that you cannot remember the purpose of.

[General BlackDragon]

Something I would find useful, would be something that did the opposite, searched folders both odf and xsi/msh or other files found their links and then informed me which files were not referenced by any of them. Taking years over a project means you get a lot of trash that you cannot remember the purpose of.

Ditto.

Those filetypes would all be easy to do, they're all editable in notepad. Just add in the key things, such as XSI's texturename line, and AIP's build and attack lines, and bzn object lines, etcetc.

[Ded10c]

They wouldn't be easy to do at all. They'd have to be parsed individually by the program; the only reason ODF and TRN are easy is because INI parsers already exist.

You can always use the referencer to move all the linked files into a seperate folder, then just delete with not left. It takes longer, but it's not a terrible workaround.