Its easier to have a template when you are manually renaming lots and lots of files. How about something like:
Sex-Race-Age-Skin-FurColor-HairColor-EyeColor-Tits-Ass-Attribute1-Attribute2-Attribute...
Example:
Female-HalfkinWolf-Adult-PaleSkin-BrownHair-RedEyes-SmallTits-SmallAss-AnimalEars-AnimalTail
I have no idea what the filters for unimplemented attributes will be but for now I think Ill work on renaming following this template.
EDIT: actually do hyphens work as word separators?
What I'm saying is that this is entirely up to you. It has no impact on the mod. You can decide what you want the template to be for your mod pack on your own.
Personally, I'd use folders so it's easier to see how many I have for different chunks. Like:
Race/Sex/Age/HairFur-Eye-Tits-Ass-misc.png
and an example
Human/Female/Adult/Blond-RedEyes-TitsB-AssS-1.png
Again however, this is entirely up to you.
I'm tempted to write a portrait pack manager app. Lets you select a portrait, view it, and then edit the tags, and it renames both the portrait and body in-sync. Maybe even let you select an image as full body, select a section to crop as portrait, and add that? What OS do you guys use? My language of choice for such an app would probably be C#, the result working on Windows, and maybe on Linux/Mac via Mono. Probably make your work of renaming them a lot easier, as you'd just have to select an image, check some boxes, click apply, rinse repeat for folder.
sexiestmanalive is renaming something like 3100 pictures. Once that colossal portrait pack comes out, I'm pretty sure it will become the new standard naming format for packs. As far as I know, it doesn't use eye color. I'm a take the path of least resistance and leave the eyes out of naming. Some portraits have eye color that wouldn't appear on that particular race anyway (so you're only naming eyes on those, for people to use the search function)
This next part is what I'm gonna try and use for naming (from manalive)
Breasts_Size: ["TitsS", "TitsM", "TitsL", "TitsH"] where: TitsS = "masculine", "flat", "small"; TitsM = "average"; TitsL = "big"; TitsH = "huge"
Skin_Tone: ["SkinL", "SkinT", "SkinD" "SkinP" "SkinB"] where: SkinL = "pale", "fair"; SkinT = "olive", "tan"; SkinD = "brown", "dark"; SkinP="purple"; SkinB="blue"
Butt_Size: ["AssS", "AssM", "AssL", "AssH"] where: AssS = "masculine", "flat", "small"; AssM = "average"; AssL = "big"; AssH = "huge"
So an example would be "Dragonkin Teen Blond TitsM SkinT AssL AssH"
The two Butt sizes are because it could be either. The tags can be in any order too I think. Mod will assume a portrait is female unless the word male is present, so you don't need to write female. Will assume Adult unless either the word Teen or Child is present, so don't need to write Adult on a portrait
If you really wanted to add eye color tags. I'd suggest EyeBK for black EyeBE for blue EyeBN for brown EyeG for green etc.
"redeyes" would still work, It just might take a little more work from Kyler, because as you surmised, there would could be a conflict. I know that when searching male it disregards that part of the word in female. But don't know if the colors work the same way, yet.
(Sorry if i'm coming across critical, pulling my hair out trying to get around the button image files for races, so we can add "Mimicekin")
Foe eyes I'll most likely scan for both RedEyes and EyesR. I'm already scanning for BlueSkin and SkinB.
Per question above, when/if I add Eyes, for any ambiguity, color without qualifier == hair. If qualifier, then it's not hair but whatever the qualifier is.
RedRedEyes.png = Red Hair Red Eyes
RedHairRedEyes.png = Red Hair Red Eyes
RedEyes.png = Red Eyes
Red.png = Red hair
BrownBrownSkin.png = Brown Hair Brown Skin
I could also add alternative tags, but <color>Eyes is the simplest to implement.
Looking forward to it then. Don't really want to try manually renaming 1700+ images in my pack again to remove the extra tags with windows alone lol.
Want to also ask since my pack right now has no teens and not planning to update anytime soon if you can add in portrait script that if there are no teens then it'll choose one of loli.
v0.1 of the PortraitPackEditor is linked in top post. Of note, it scans things alphabetically. Could move all existing portraits into a _Rename subfolder under Portraits and Bodies, then they'll always be at the top of the list until renamed/moved.
It does impose it's own structuring to the name,
<races>\<genders>\<ages>\<hair colors> <Skin colors> <tit sizes> <ass sizes> <custom text> #.ext
The # starts at 1, then if there's already a file with the exact same name, it increments to 2, and so on till it finds one that isn't in use.
For the age selection, it is a bit of an issue, as no teens, right now means it falls back to everything. I don't think making it fall back to loli is the answer though. Partially depends on your definition for those.
