But I have one thing to ask. I was thinking about using the same numbers that appear on the ITEM_PID list.
that would be
1 PID_LEATHER_ARMOR
2 PID_METAL_ARMOR
3 PID_POWERED_ARMOR
[...]
I was thinking similarly for the filenames of the models and textures - currently there's no "standard format", I have been particularly guilty of this when naming each file with no consistency, i.e. "ncr10_coat.png, male_cljacket_clothing.png, f_clj_jacket4.png" which has nothing to connect models, textures, in-game codes etc
So was wondering whether we should decide on a sort of "format" to stick to with model / texture naming, for example something like :
001_0_leather_armour_male_body
001_1_leather_armour_female_body
001_2_leather_armour_coat_part_1
001_3_leather_armour_coat_part_2
001_4_leather_armour_helmet
002_0_metal_armour_male_body
002_1_metal_armour_female_body
etc
This is just as an example, but perhaps something similar, which uses the ID number of the object, followed by other numbers / words to clarify everything. Obviously all the items which don't currently exist in game would need new numbers, but if it's consistent throughout, it would be much easier than trying to connect "Armor_male_cmbleatherJacket.X" and "Armor_Female_cmbleatherJacket.X", with "cljacket_texture.tga" and "f_clj_jacket4.png" for example - in a way similar to how the original has names like "HMLTHRCH.FRM", which once you could read the code, made connecting / locating specific files much easier.
I'm aware this may involve a lot of re-exporting work, but perhaps if it was done or agreed upon sooner rather than later, this would only be 100 to re-export, rather than 1000 - and if all future models used this, it could save a lot of work at a later date.
On the other hand, maybe we've done too much already to do this easily, and will just have to cope with our (my) inconsistent naming of files.
