Organising Your Rig Scripts
There's so many rigs it spills into multiple pages WARGH
Introduction
We can fix that, with the amazing power of... Folders!
Since SFM looks in subfolders when populating that list of rigs, we can just do a little organization.
Before you start...
There are a couple of things to consider before following these steps.
Some rigs have logic that depends on other files being somewhere it expects. I don't use SFM_Init myself, but I imagine that might need manual intervention to correct paths to files. Orida reads and writes JSON files to the Usermod scripts folder, and needs editing to open the correct folder by default.
You can leave scripts that cause these complications in their original spaces if you prefer. If you're advanced, these are just Python scripts which you can edit in Notepad++.
The Workshop handler will not know about any changes you make, so you may end up with duplicate or orphaned files. Unsubscribing will not delete a file you've moved, for example.
How To Do The Thing
By default, your important folders are Usermod and Workshop. If you've added custom mod folders you'll need to handle their scripts folders too. If you don't know if you've got custom mod folders, the answer's almost certainly "no".
For simplicity's sake, I would use the Usermod folder as the place where scripts live. This will leave updated files from the workshop to sit there waiting for you to manage them.
In Workshop/Scripts/SFM/Animset are the files that are shown in the Rigs menu. What we want to do is move them into Usermod/Scripts/SFM/Animset so that all the rigs are together in one place.
By default, SFM ships with one script in Platform/Scripts/SFM/Animset, so make sure to move that one as well.
Make subfolders within Animset for your categories. I personally go with "1_Tools", "2_Bases", "3_Characters", "4_AutoRigged". Tools being for... you know, tools. Bases being for rigs that apply to several models sharing the same standards. Characters for individual characters, and AutoRigged for rigs put out by the Autorigger script on the Workshop.
While the folder names themselves don't show up in the rigs list, the folders are sorted alphanumerically, so the contents of 1_Tools will show in the list before 2_Bases, and so on.
Time for the boring part. Read the names of the rigs, and sort them into their subfolders.
You can also make a Trash folder and move it up a level into the SFM folder if you want to move files out of the menu, but still be able to find them with the Load Rig File... menu entry.
Headers! They're maybe the most important part for making the list manageable.
Just make an empty text file and name with a line of dashes, along with the name you want the header to show up as in SFM, and change the file extension to ".py". So for my Bases folder header, I just make a file called "----------------------------------Bases.py". The dashes are there for two reasons:
- to act as an actual divider for visual clarity, and
- because the contents of the folders show up alphanumerically in Windows and SFM, symbols such as dashes are sorted to appear before letters and numbers.
Remember that Windows hides file extensions by default. If you make the file and it doesn't show up, the file is probably still a ".txt" file, like "Bases.py.txt". You can also put one called "----------------------------------Unsorted.py" in the Animset folder to help distinguish those from sorted files.
Conclusion
Thanks to ImAFutureGuitarHero for checking over the guide and helping out!
This guide was created by its original author on the Steam Community. Are you the author and want it removed? Request removal.