More flexible path/name conventions for custom content
Soylent_green
Join Date: 2002-12-20 Member: 11220Members, Reinforced - Shadow
Join Date: 2002-12-20 Member: 11220Members, Reinforced - Shadow
<div class="IPBDescription">Reduces bandwidth and hard-drive wastage for reused art assets</div>The mapping guidelines for NS1 specifically told you to stick custom art assets into a folder with your map's name(some minor exceptions like textures which could also be compiled into the .bsp).
Assume there is a really popular texture pack released for NS2. If NS1 rules apply you must re-dowload all used textures for each and every map, instead of just the ones you don't already have.
I propose instead that arbitrary folder names may be used provided that a GUID is tacked onto the end of it. GUIDs are 128-bit integers that specifically designed to have an extremely low probability of causing collisions, hence there is no need for any kind of centralized registry or coordination; you just make up a name, generate a GUID and stick it on the end of the folder name.
Like so: NS2/Materials/Refinery - b8948dc5-39d6-481c-9164-e553469e061f/.
It is also necessary to have the social convention that you never copy an existing GUID, generate your own, just like it is a social convention to not make a map named ns_eclipse for NS1.
Assume there is a really popular texture pack released for NS2. If NS1 rules apply you must re-dowload all used textures for each and every map, instead of just the ones you don't already have.
I propose instead that arbitrary folder names may be used provided that a GUID is tacked onto the end of it. GUIDs are 128-bit integers that specifically designed to have an extremely low probability of causing collisions, hence there is no need for any kind of centralized registry or coordination; you just make up a name, generate a GUID and stick it on the end of the folder name.
Like so: NS2/Materials/Refinery - b8948dc5-39d6-481c-9164-e553469e061f/.
It is also necessary to have the social convention that you never copy an existing GUID, generate your own, just like it is a social convention to not make a map named ns_eclipse for NS1.