I've updated a few things:
- added verification step that checks if generator.bat can find the necessary vpk's (basically checking if cleantf2plus is in custom), like Zetos mentioned
- made flat textures and all model removals inform you of their progress, like Zetos mentioned
- attempted auto-detection and warning for weird behaviour some people (Adje) experienced. I can't confirm whether it'll work because it doesn't apply to my machine, but if you do experience it should just be a warning and let you still use the generator.bat (but you should mention it to me because it'll probably cause issues still).
Zetosand instead of a "Help" prompt, just place their descriptions there, since they're so short and there are few options to skim through.
This is the one thing I'm iffy on. I think the help system should stay, it's not really needed right now but if/when the descriptions get long in the future it'd be better to have everything already in place.
HrblsThanks for this fantastic work as usual.
Our of interest, how does the generator distinguish between Hats that should be kept for headsfeet and those that should be removed when generating?
Everything in this is a list of files and folders, essentially. There's a list for everything that should be used in nohats, and then there's another list for the things to take out from headsfeet (which just deletes those files, which might seem slow or impractical but is better for a few reasons -- updates are easier and it's actually faster anyway).
Nohats is mostly update-proof, since it's unlikely for new hats to be added into a new folder instead of existing ones that are already covered, but headsfeet would need to be manually updated whenever there's a new head/foot cosmetic added. It's not ideal (I was considering a python script to generate the list from items_game.txt, which I might still do to update the headsfeet list but I don't want everyone using cleantf2plus to also need python) but since it's just a line or two added to a text file that anyone could edit and send up a pull request for, it hopefully should be easier to manage making a new vpk each time.
Wiethoofd:: Find TF2 install location in the registry
REM https://stackoverflow.com/questions/39940343/how-to-find-the-directory-of-an-executable-using-a-batch-file
(for /f "usebackq tokens=1,2,*" %%a in (`reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Steam App 440" /v InstallLocation`) do set TF2x86=%%c)>nul 2>&1
(for /f "usebackq tokens=1,2,*" %%a in (`reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Steam App 440" /v InstallLocation`) do set TF2x64=%%c)>nul 2>&1
set TF2Path=%TF2x64%%TF2x86%
Right now a lot of the setup assumes that it's in the custom folder, so making everything work with this might be a decent chunk of work to do. When the rest of the system's stable I'll probably try my hand at this, unless someone else contributes it.