abot wrote: nice, but having a standard .esp with standard/official static ids so we have no different ids for any modder using the resources and some example cells (those displayed in the screenshots would be ok if they come from a .esp) to ease understanding what piece goes with the other for people not used to interior making would make the resource much more valuable.
I can add an esp with the examples from screenshot. Naming convention was just intended as just dropping models straight to CS.
yeah, what I did, but I bet 2 different modders could have used 2 different aaa_ or @@_ prefixes, better to have standards already defined if possible in a resource pack, also drag and drop of meshes in CS may not work if you are not running Morrowind with administrator privileges so having them ready could simplify things for some people
nice, but having a standard .esp with standard/official static ids so we have no different ids for any modder using the resources and some example cells (those displayed in the screenshots would be ok if they come from a .esp) to ease understanding what piece goes with the other for people not used to interior making would make the resource much more valuable.
Give Feedback
10 comments
yeah, what I did, but I bet 2 different modders could have used 2 different aaa_ or @@_ prefixes, better to have standards already defined if possible in a resource pack, also drag and drop of meshes in CS may not work if you are not running Morrowind with administrator privileges so having them ready could simplify things for some people
Naming convention was just intended as just dropping models straight to CS.