This is true, the ideal way I've found though is to do certain things:
A top hak
Male Clothing
Female Clothing
Robes and Cloaks (and any associated MDL's for different phenotypes such as riding or ACP)
Heads
baseitems and icons
Tilesets (if you have many small ones)
Creatures
Placables
In this way you sort of isolate the number of files you have to search for any specific resource. Clothing haks can all be combined together but the textures tend to make them quite sizable and models for all races tend to push you to upper limits of hak size if you have a lot of pieces.
The more haks the server has to search through to find a resource, the longer the load time. It starts at the top of the list and goes down looking for a specific resource, it's not a huge deal of time, algorithms are fairly complete and concise for doing that sort of thing, but it does add up. Converseley having a lot of small haks or one big one with the same number of files is going to amount to the same difference I think.
And as for CC author's permission, I always try to obtain that if I'm using their work alone or merging, it's just common courtesy. I've had some like CTP wish for their stuff to remain standing alone and others simply are happy to have their work used.
Somewhere in my earlier post I stressed keeping it as easy for the end user as possible. Too many haks is intimidating to plenty, even if they're much smaller in size. The fact that Project Q and CEP both have an exe version available should demonstrate end users desire for ease and simplicity.
Modifié par Calvinthesneak, 01 août 2010 - 02:41 .