So I was compiling my portraits collection, and figuring out which ones to put together into a hakpak for my module because I didn't want to make people download an entire 500MB portrait pack when I might only use a small fraction of it.
Then I got to thinking that I'd like to be able to do that again for my next module, but without having to go back through and compile a brand new portraits.2da by hand. So I made a spreadsheet of all my portrait names combined with the other relevant details to make it really easy to copy-paste them into a new 2da.
But this got me thinking: how doable would it be to set up a more involved system for other resources? Imagine a SQL database of all models and associated skins possible for every article of custom clothing and every phenotype out there. Imagine a simple program that would let you browse through screenshots of every article of clothing, and select which ones you want to use, and the program would automatically bundle them together with appropriately adjusted file names and 2das.
What do you guys think? It's fairly straightforward to write a basic script to trace the text in .mdls, etc and replace as needed as well as change file names and generate corresponding .2das. Maybe even making a basic database of files with the correct links to superset files, etc could be straightforward too. I feel pretty confident that with some review, I could write a program to trace through files and replace text, but I haven't done anything with SQL in years, so it would probably take me much longer to figure out how to do that.
How crazy would it be to try to build this? XD





Retour en haut






