Most of the new equipment is now being added to DATA3(Bartuk), DATA4(Kruxena), DATA5(Turan), and DATA6(Xenoa). In each of these folders is already a different equipment with the following convention [Race]_[Sex]_M_R74_[Equipment Slot].
I suggest moving the new equipment under their respective VDKs with your own easy to remember naming convention that does not conflict with pre-established naming conventions. Such as [Race]_[Sex]_[Magic/Fighter]_[Equipment Name]_[Equipment Slot]. For instance, the Bartuk Male upper equipment would be in DATA3.vdk as 'B_M_M_Glacial_U.nif' and 'B_M_F_Glacial_U.nif'. Trying to adhere to the previous naming convention might be difficult considering the changes it has had since 2005. B-Beginner, C-Caster, D-Dungeon, E-Event, F-Fighter, GM-Game Master, INS-Instance, M-Melee/Magic, N-NPC, R-Raid, S-Special/Costume, Theme-Theme
I would also seriously consider using a better folder structure. The OS operation to find a specific file in a VDK on a hard drive and load it into memory can be cut down to 1/40th the time it currently takes in the most extreme case by recreating the folder setup to '[DATA].vdk\ITEMS\WEAR\[RACE]\[SEX]\[SET]'. I am not sure of the specifics on how the game sees VDK files or how its loaded into memory. Iit could load all the assets into memory immediately and make the folder setup moot, although I find that implausible for a 32-bit game that has around 2GB of data, or a game running in real time. It could also create a virtual folder structure from the VDKs so the several DATA.vdk may be visible simply as \DATA folder. If that is not the case, than a lot more operations could be cut down by changing the structure of the VDK further to simply '[RACE].VDK\[SEX]\[SET]'. Or better yet do away with VDKs entirely except for extremely sensitive data and use a folder structure for simpler patching and quicker file look ups.
Edited by Cleffy, 20 February 2014 - 09:59 PM.
