2 réponses à ce sujet

[Anroth56]

I will try to explain what I wish to accomplish as best as I can.
 
I have two Modules: X and Y. X is a custom Module with custom content, while Module Y created with the Toolset and utilizes basic toolset resources.
 
There is an item within Module X (sword and/or armor) which has its own custom model and texture, along with an assigned name, stats, etc. Module X is completely finished, and is fully functional once implemented into DA: O.
 
I want to extract the item in Module X and place it into Module Y, to utilize its model and texture. I wish to execute this process in a manner that allows me to create a new version of the item, permitting me to assign a new name, statistics, etc.
 
I am not an experienced user of the Toolset; I have created custom items using resources within the toolset and created a module to give the player these items, but have done little beyond this.

I have searched for information in accomplishing this process, but I have found none which offers a clear means of doing so. If anyone can offer an explanation or point me to a tutorial, I would greatly appreciate it.

Modifié par Anroth56, 07 juillet 2010 - 06:25 .

[Proleric]

Module X has two components - the toolset source, and the executable files in your Documents folder.
 
The latter are often found in Addins/Module X/module/override and/or Addins/Module X/core/override. If you can't find them, look in the other sub-folders, including packages/core/override.

Assuming you know which model and texture files you need, copy them from Module X's folder to Addins/Module Y/module/override (you'll need to create Module Y for this to exist).

Also, there should be a file called (item)_variation_xxx.gda, where (item) is the base item type (e.g. armor_heavy_variation_xxx.gda) and xxx is a suffix chosen by the author of module X. Copy that, too. 

If you have the toolset source, it will probably be in Builder-to-Builder format (.dadbdata). In the toolset, do a Builder-to-Builder load from that file into module Y, selecting only the item you want. You'll probably want to read the wiki page on Builder-to-Builder load first.

You should now have an item in module Y which is everything you want, but it will have the wrong resource name - probably the original name, but if that already exists in module Y, it will be called (original name)_1. 

So, duplicate the item in Module Y, assigning the resource name you actually want.

Finally, check in the item you don't want any more, and delete it.

Edit : if you don't have the toolset source, you will have to make a new item in the toolset. You'll find that the custom item variation is available once you've copied the files from module X's folders and reopened the toolset.

Modifié par Proleric1, 08 juillet 2010 - 06:33 .

[Anroth56]

I forgot to mention that the information was not in the dadbdata format, and was fragmented into two erf files and one cif.



However, I was able to incorporate the information I sought into the Toolset, and I have the custom item variation available.



Thank you for the information; I appreciate it.