Open Elbagast opened 10 years ago
This might be worth putting of for now.
e.g. if you wanted a lot of small tools to share the game settings/information it would be better to figure out how to separate that from the program and call it when needed. This program would do:
"is this file in the game?" -> true/false
Another tool (e.g. a material maker that wants an existing texture) might ask:
"what files of this type are in the game and where are they?" -> list of files "what is the data for this file?" -> the file's actual data
So I guess I need to bear in mind what sorts of things tools will want to know and share.
Consider adding checks against the game's files to provide information about which mod files are overriding existing game files, and which are adding new ones.
This would require setting up a way of scanning the game vpk files, but those are huge so more intelligent file scanning would be in order. This means figuring out how to detect and store stats about files and scan again only if they've changed since the last scan.