Dragon Age Toolset Wiki - User contributions [en]

Creating recolors of existing items tutorial

2010-06-05T07:24:10Z

Imkilo: put in some details on how to get the new item from scratch, or how to open the item from within the game

This tutorial describes how to create a custom [[Item]] by recoloring an existing item. It is assumed that the reader is familiar with the Toolset. These instructions are based on a forum post by Dylbot.

__TOC__

=Getting Started=

Open the item you want to recolor. For the purposes of this tutorial, we're going to go for heavy chainmail.

If creating a new item, to select heavy chainmail, in the toolset click File>New>Item and change the "Base Item Type" to "Armor - Heavy" and the "Item Variation" should be set to "Heavy Armor C".
To modify all heavy chainmail worn by every character, in the toolset, click either "Item" (sword icon) or "All" (icon with the word: All) in the [[Resource palette]] then in the tree of folders below expand "_Global" > "Armour, Chest" > "Heavy", then right click the item "gen_im_arm_cht_hvy_hch.uti (Heavy Chainmail)" and choose "Check Out".

[[File:HeavyChainmail.jpg]]

=Create a new material=

[[File:CreateNewMaterial.jpg]]

=Add a new tint library to Root=

[[File:NewTintLibrary.jpg]]

=Add a new tint object to that library=

[[File:NewTintObject.jpg]]

=Enable the red, green and blue channels=

[[File:EnableRGBChannels.jpg]]

=Open the tint file for the object you are recoloring=

You'll need to know what you're changing when you color the channels. You can do this with WTV (Windows Texture Viewer). WTV is available on the [[DDS]] page, provided for free by Nvidia.

Using the Toolset, open up texturepack.erf in (Dragon Age directory)/packages/core/textures/high/, and scroll down to the texture you need (in this case, it's pm_arm_hvyc_0t.dds, signifying male, armor, heavy, type c, tint map). Right-click and open resource. At this point, you may want to hide the alpha channel in WTV, or all you're going to see is a pink square.

[[File:RedGreenBlueChannels.jpg]]

What you're seeing is the armor texture, divided into three channels; red, blue, and green. As you may have guessed, each of the channels corresponds to the equivalent colored area on the tint map.

=Change the colors as desired=

If you do this:

[[File:ChangeGreenChannel.jpg]]

All of the green areas on the tint map (the chainmail and the belts) will become red on the model when you apply the tint. A little tip: the Diffuse color changes the base color, and the Specular color changes the reflection color. Change colors as you please.

=Name and save the tint file=

Once you're happy, give your material a name (I'd suggest sticking to the naming convention of the game, so something like arm_xyz, it'll add the T3 itself) save the matproj, and right click on Root - Post Selection to Local.

=Add the new tint to your tint_override m2da=

Now, the next bit is a bit more complicated. In the item settings, you may notice an option called Tint Override.

[[File:TintOverride.jpg]]

What we're going to do now is tell the game that our new tint is one of these overrides. This comes with the added bonus that the armor can be set as any material and still have the custom color. You'll need a spreadsheet program, so if you don't have MS Office, go pick up OpenOffice (if you don't have it already, naturally). Done? Right. Navigate to (Dragon Age directory)/tools/Source/2DA, and copy Tints.xls to your documents area, or wherever. Open up the copy, and choose the tint_override sheet. Add your new tint in at the next available blank line (put whatever you want as the label, something like "My Custom Tint 1" or something that makes it obvious what it is, and the file name in the tintfile box, which, in the case of our example, would be t3_arm_xyz. Star out the last column like the other tints). Save the worksheet and close it. Now, you're going to need to export that to the 2DA format. There's a handy tutorial over at the DA Builder wiki - [[Compiling 2DAs]] - which looks a bit scary at first, but is nothing to be worried about. If you don't know how to create a batch file, all you do is create a new text document, and change the extension from .txt to .bat. Once you've exported, chuck the tint_override.gda file into the game's override folder, as described in the 2da tutorial.
Now, close the toolset and open it again. Check out your piece of armor, and check the tint overrides. Lo and behold, your new tint is there. Apply that sucker and admire your handiwork.

[[File:RecoloredItem.jpg]]

Save, check in, and export the armor. If you've got gloves and boots (and you should have, we're going for a matching set here), check them out and apply the tint too. You can even apply it to weapons and shields if you want. Once everything is checked out and exported, load up your game and take a look at your shiny new equipment (if you've set up your loading script, or already have the equipment. If not, check the custom item tutorial, it'll tell you what you need to know).

[[File:AlistairInArmor.jpg]]

Alastair wearing the new armor.

= Related Links =

[[Material editor|Material Editor]]

[[Texture Formats]]

[[Material Tint System]]

[[Category:Textures]]
[[Category:Tutorials]]

Creating recolors of existing items tutorial

2010-06-05T06:58:35Z

Imkilo: it's good policy to only link externally on one page, so reworded this sentance to link to the DDS page and refer to WTV there

This tutorial describes how to create a custom [[Item]] by recoloring an existing item. It is assumed that the reader is familiar with the Toolset. These instructions are based on a forum post by Dylbot.

__TOC__

=Getting Started=

Open the item you want to recolor. For the purposes of this tutorial, we're going to go for heavy chainmail.

[[File:HeavyChainmail.jpg]]

=Create a new material=

[[File:CreateNewMaterial.jpg]]

=Add a new tint library to Root=

[[File:NewTintLibrary.jpg]]

=Add a new tint object to that library=

[[File:NewTintObject.jpg]]

=Enable the red, green and blue channels=

[[File:EnableRGBChannels.jpg]]

=Open the tint file for the object you are recoloring=

You'll need to know what you're changing when you color the channels. You can do this with WTV (Windows Texture Viewer). WTV is available on the [[DDS]] page, provided for free by Nvidia.

Using the Toolset, open up texturepack.erf in (Dragon Age directory)/packages/core/textures/high/, and scroll down to the texture you need (in this case, it's pm_arm_hvyc_0t.dds, signifying male, armor, heavy, type c, tint map). Right-click and open resource. At this point, you may want to hide the alpha channel in WTV, or all you're going to see is a pink square.

[[File:RedGreenBlueChannels.jpg]]

What you're seeing is the armor texture, divided into three channels; red, blue, and green. As you may have guessed, each of the channels corresponds to the equivalent colored area on the tint map.

=Change the colors as desired=

If you do this:

[[File:ChangeGreenChannel.jpg]]

All of the green areas on the tint map (the chainmail and the belts) will become red on the model when you apply the tint. A little tip: the Diffuse color changes the base color, and the Specular color changes the reflection color. Change colors as you please.

=Name and save the tint file=

Once you're happy, give your material a name (I'd suggest sticking to the naming convention of the game, so something like arm_xyz, it'll add the T3 itself) save the matproj, and right click on Root - Post Selection to Local.

=Add the new tint to your tint_override m2da=

Now, the next bit is a bit more complicated. In the item settings, you may notice an option called Tint Override.

[[File:TintOverride.jpg]]

What we're going to do now is tell the game that our new tint is one of these overrides. This comes with the added bonus that the armor can be set as any material and still have the custom color. You'll need a spreadsheet program, so if you don't have MS Office, go pick up OpenOffice (if you don't have it already, naturally). Done? Right. Navigate to (Dragon Age directory)/tools/Source/2DA, and copy Tints.xls to your documents area, or wherever. Open up the copy, and choose the tint_override sheet. Add your new tint in at the next available blank line (put whatever you want as the label, something like "My Custom Tint 1" or something that makes it obvious what it is, and the file name in the tintfile box, which, in the case of our example, would be t3_arm_xyz. Star out the last column like the other tints). Save the worksheet and close it. Now, you're going to need to export that to the 2DA format. There's a handy tutorial over at the DA Builder wiki - [[Compiling 2DAs]] - which looks a bit scary at first, but is nothing to be worried about. If you don't know how to create a batch file, all you do is create a new text document, and change the extension from .txt to .bat. Once you've exported, chuck the tint_override.gda file into the game's override folder, as described in the 2da tutorial.
Now, close the toolset and open it again. Check out your piece of armor, and check the tint overrides. Lo and behold, your new tint is there. Apply that sucker and admire your handiwork.

[[File:RecoloredItem.jpg]]

Save, check in, and export the armor. If you've got gloves and boots (and you should have, we're going for a matching set here), check them out and apply the tint too. You can even apply it to weapons and shields if you want. Once everything is checked out and exported, load up your game and take a look at your shiny new equipment (if you've set up your loading script, or already have the equipment. If not, check the custom item tutorial, it'll tell you what you need to know).

[[File:AlistairInArmor.jpg]]

Alastair wearing the new armor.

= Related Links =

[[Material editor|Material Editor]]

[[Texture Formats]]

[[Material Tint System]]

[[Category:Textures]]
[[Category:Tutorials]]

Module

2010-03-16T02:28:55Z

Imkilo: /* Modular File structure */

{{Infobox module}}
Modules are the campaigns that players can embark on. They contain the resources needed for the adventure they encompass (though you can also have modules inherit the resources of other modules).

__TOC__
== Overview ==

A Module is a single collection of Resources, that can be the building block for another Module (Addin) or function on its own (Standalone). A set of Properties tell the game how to integrate the Resources it inherits. A Resource tells the game how it finally behaves.

The Single Player Campaign and Core Game Resources are each one of such modules. Modules can be setup hierarchical, for example the Singleplayer Module is connected to the Core Game Resources and thus can use its resources. Custom Modules can be connected to any other Module.

Core Game Resources is however special in a way, that it is the foundation of any other Module, and any Module can use its Resources.

== Working with a Module ==

What are the possible options you have when creating the basis for your Content? Generally one can say a Module can either be standalone, or addon to the existing Campaign. Standalone is a Module which from hitting "custom campaign" in the main menu starts completely fresh into a custom campaign (like the Demo module for example). A Module is an addon, if content is added or perhaps changed to the existing campaign so that it influences the existing campaign but doesnt remove it (like Shale for example).

*Standalone is pretty straightforward, in that you need at least a starting Area and a Waypoint in which the Player spawns. You can use any Core Game Resource while making this Module, basically the premade Houses, the Monsters, mostly anything. But the Area still has to be created ,NPCs placed, Dialogues written etc..
*Addon is something initially tricky to do and perhaps unknown to most, even when doing something simple. You need at least one entry point that hooks into the main campaign, and from there it can be a simple added weapon, or unfold into big things. And that entry point is called "PRCSCR". See below.

A slightly dirty method is changing a Resource of the Main Campaign. This is plainly achieved by editing a Designer Resource from the Toolset and export it under the same name, which is then a override Mod, and undesired effects can potentially reflect back at the Main campaign and other Modules. This should be left for when you know really well what the consequences are.

=== PRCSCR - Post Release Content Script ===

'''(Also known as "Adding content into an existing Area")'''

Bioware with their Addin Modules uses a functionality called PRCSCR, which enables them to insert any content u heard about into the Main Campaign. This as well is the prefered Method for Modders to add Content. PRCSCR stands for "Post Release Content Script", but isnt all that complicated as "Script" may sound.

:''See Main Article: [[PRCSCR]]''

=== Modular File structure ===

Modules are organized in the Filestructure as such the Game can read the correct files, and to allow a modular environment. The Singleplayer Campaign and Core Game Resources use a fixed set of Filefolders.

The Singleplayer Module and the Game Core Resources respecivtly (this is the actual installed content) are located in:
<pre>*DragonAgeInstallDir*\modules\single player\
*DragonAgeInstallDir*\packages\core\</pre>
These base Folders accompany all Resourcetypes specific to that Module. However this is a fixed set, and should be of value to modders only when extracting Resources.

Modularity is made in your users folder, where the Toolset exporter distributes Resources into the respective Modules override Folder, as well as creates or stores "builder to player" packages from those Folders. A 3rd Moduletype called Addin is created there which similarily has a "module" Folder for any Resources for that Module alone, and a "core" Folder for any Resource to be accessible by other modules. It looks like this:

<pre>*My Documents*\BioWare\Dragon Age\AddIns\*Modulename*\module\
*My Documents*\BioWare\Dragon Age\AddIns\*Modulename*\core\

alongside a double of

*My Documents*\BioWare\Dragon Age\modules\Single Player\
*My Documents*\BioWare\Dragon Age\packages\core\</pre>

The Toolset exports any Resource into each of these Folders, or specifically the override Folder beneath it, depending on which Module the Resource belongs to. When packing the Resources into an installable [[DAZIP]] file, you have to specify any of those folders to include. Thus it is to great part important where Resources are located, and especially where files shouldnt be located.

Resources will be read from any Override folder, but organizing files to adhere to this structure will help when working with the Toolset.

== Properties ==

{{inspector start}}
{{inspector section|General }}
{{inspector row|Client Script | Client scripts simulate user input }}
{{inspector row|Include In Resource Build| This was used internally in the development of Dragon Age to determine whether a module in the designer database was automatically included in builds.}}
{{inspector row|Name| The name of the module, used internally in the toolset title bar and as a fallback in the game if a description string ID has not been set.}}
{{inspector row|Script | Event script assigned to the resource }}
{{inspector row|Starting Area | The area that the player starts in when the campaign begins. }}
{{inspector row|Starting Waypoint | The waypoint within the starting area that the player appears at when the campaign begins. This property is not used if the module is an add-on to an existing module. }}
{{inspector row|StringID Begin | The line number in the [[String editor | talk table]] at which this module's text strings begins. Set to a very large random number to reduce the risk of conflict between modules. When building as a team, each builder needs to work with a different range and be aware of a potential [[Bug:_Builder_to_Builder_Load_may_not_reproduce_resource_detail_correctly | bug]].}}
{{inspector row|StringID End | The end of the talk table line number range allowed for this module.}}
{{inspector row|StringID Last Used | The last line number used by this module in the talk table. Determines the line number of the next text string created.}}
{{inspector row|Type | Only the "Addin" type is supported by the end user toolset. The name "Addin" can be misleading, it's possible to create a stand-alone addin that appears as a new campaign. }}
{{inspector row|UID| "Unique ID", this is not seen by the player. It is used in various configuration files and as the name of the directory that the module is stored in when exported.}}

{{inspector section|Info}}
{{inspector row|Content Module| If this module is a PRC "offer" module, this indicates the module that it is offering for download. This is not likely to be used outside of BioWare.}}
{{inspector row|Description | This property can't be set directly, it displays the contents of the description string ID set below. }}
{{inspector row|DescriptionStringID | A [[string ID]] pointing to a short description of your module}}
{{inspector row|DisplayName | This property can't be set directly, it displays the contents of the display name string ID set below. }}
{{inspector row|DisplayNameStringID | A [[string ID]] pointing to the name of your module.}}
{{inspector row|Extended Module | If the module is an add-on to an existing module (such as Single Player), select it from the drop-down list here. When this is set the module will be added to addins.xml when it is exported. }}
{{inspector row|Game Version|}}
{{inspector row|Image| An icon that's displayed in the installed content page }}
{{inspector row|Presentation| If the module is an offer this bitmask indicates the various ways that the "hook" for the addin will be presented to the player in-game. 1: [[Chanter's board]], 2: [[journal entry]], 4: [[merchant]], 8: [[world map]], 16: [[NPC]], 32: loot. You can logically OR multiple types together.}}
{{inspector row|Price|The price of the module in points. This is only meaningful for modules offered by BioWare.}}
{{inspector row|Priority|}}
{{inspector row|ProductID|}}
{{inspector row|Publisher|This property can't be set directly, it displays the contents of the publisher string ID set below.}}
{{inspector row|PublisherStringID|}}
{{inspector row|Rating|This property can't be set directly, it displays the contents of the rating string ID set below.}}
{{inspector row|Rating Description|This property can't be set directly, it displays the contents of the rating description string ID set below.}}
{{inspector row|RatingDescriptionStringID|}}
{{inspector row|RatingStringID|}}
{{inspector row|Release Date|The date the module was released in its current form}}
{{inspector row|URL|}}
{{inspector row|URLStringID|}}
{{inspector row|Version|The version number you've assigned to the module's current state.}}

{{inspector section|Localization and VO Production }}
{{inspector row|Requires Localization | {{undocumented}}}}
{{inspector row|Requires VO (Voice-Over) | {{undocumented}}}}

{{inspector section|Modification History }}
{{inspector row|Created By | User who created this module. }}
{{inspector row|Created On | The date it was created on. }}
{{inspector row|Last Modified By | The user who last modified the module. }}
{{inspector row|Last Modified On | The date it was last modified on. }}

{{inspector section|Variables }}
{{inspector row|Variable 2da | 2da file containing a variable table. Only the values in the table can be set and retrieved by scripting. }}
{{inspector row|Variables | Opens the variable table for editing, allows the initial values of the variables to be defined. }}
{{inspector end}}

=== Variables ===

The module_var variables 2da contains a number of variables that are only used by the original main campaign for Dragon Age. Most of these can be ignored when creating other modules. In fact, the vast majority of the variables in this table are only referred to by core scripts; most modders will likely not need to worry about these.

{{variable table start}}
{{Variable table row
|name= ABILITY_ALLY_NUMBER
|type= int
|default= 4
|description=
}}
{{Variable table row
|name= AI_DISABLE_TABLES
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= AI_PARTY_CLEAR_TO_ATTACK
|type= int
|default= 0
|description= 0 - non controlled followers should not attack yet. (can still run other non-offensive AI actions).
1 - non controlled followers are allowed to attack.
}}
{{Variable table row
|name= AI_USE_GUI_TABLES_FOR_FOLLOWERS
|type= int
|default= 1
|description=
}}
{{Variable table row
|name= ALISTAIR_FRIEND_TRACK
|type= int
|default= 0
|description= A variable related to one of the main party followers in Dragon Age: Origins.
}}
{{Variable table row
|name= AMB_SYSTEM_DIALOG
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= APP_APPROVAL_GIFT_COUNT_*
|type= int
|default= 0
|description= A set of variables, one named for each of the possible main party followers in Dragon Age: Origins, for tracking how many gifts they've each been given.
}}
{{Variable table row
|name= APP_APPROVAL_RATE_*
|type= int
|default= 0
|description= A set of variables, one named for each of the possible main party followers in Dragon Age: Origins, for tracking their approval score.
}}
{{Variable table row
|name= APP_RANGE_VALUE_*
|type= int
|default= 0
|description= A set of threshold values for dividing party member approval scores up into "friendly", "warm", "neutral", "hostile" and "crisis".
}}
{{Variable table row
|name= AREA_LOAD_HINT
|type= int
|default= 0
|description= Related to the text shown on the load screen between areas
}}
{{Variable table row
|name= CHARGEN_MODE
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= CIR_FADE_FOLLOWER_*
|type= int
|default= -1
|description= A set of three variables related to a specific plot within the original campaign of Dragon Age: Origins
}}
{{Variable table row
|name= CLIMAX_ARMY_CURRENT_AREA_BUFFER_SIZE
|type= int
|default= 0
|description= A variable related to a specific plot within the original campaign of Dragon Age: Origins. The current number of living army members in the current area of army deployment.
}}
{{Variable table row
|name= CLI_ALISTAIR_AGREE_LEVEL
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= COUNTER_MAIN_PLOTS_DONE
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= CUTSCENE_SET_PLOT
|type= string
|default= NONE
|description= Cutscene function will store a plot flag to be set after the cutscene plays.
}}
{{Variable table row
|name= CUTSCENE_SET_PLOT_FLAG
|type= int
|default= -1
|description= Cutscene function will store a plot flag to be set after the cutscene plays.
}}
{{Variable table row
|name= CUTSCENE_TALK_SPEAKER
|type= string
|default=
|description= Cutscene function will store a talk speaker who will speak after the cutscene plays.
}}
{{Variable table row
|name= DEATH_HINT
|type= int
|default= 0
|description= related to the text shown on the screen after the player's death
}}
{{Variable table row
|name= DEBUG_ENABLE_PARTY_ITEM_SCALING
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= DEBUG_SKILL_CHECK_OVERRIDE
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= DEMO_ACTIVE
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= DISABLE_APPEARANCE_LEVEL_LIMITS
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= DISABLE_FOLLOWER_DIALOG
|type= int
|default= 0
|description= Make followers trigger soundsets instead of dialog when the leader is not the hero and clicked on (for example: climax defense)
}}
{{Variable table row
|name= DISABLE_WORLD_MAP_ENCOUNTER
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= DOG_WARLIKE_COUNTER
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= HANDLE_EVENT_RETURN
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= LOG_ACTIVE
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= LOG_AI_CURRENT_LEVEL
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= LOG_PLOT_CURRENT_LEVEL
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= LOG_RULES_CURRENT_LEVEL
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= LOG_SYSTEMS_CURRENT_LEVEL
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= MODULE_COUNTER_*
|type= int
|default= 0
|description= Three generic "counter" variables
}}
{{Variable table row
|name= MODULE_WORLD_MAP_ENABLED
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= NRD_BANDIT_BELT_COUNT
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= NRD_DIVINE_COIN_COUNT
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= NTB_*
|type= int
|default= 0
|description= Variables related to a specific plot within Dragon Age: Origins
}}
{{Variable table row
|name= ORZ_*
|type= int
|default= 0
|description= Variables related to a specific plot within Dragon Age: Origins
}}
{{Variable table row
|name= PARTY_BANTER_DIALOG_FILE
|type= resource
|default= NONE
|description=
}}
{{Variable table row
|name= PARTY_BANTER_ROTATION_COUNTER
|type= int
|default= 0
|description=
}}
{{Variable table row
|name=PARTY_LEADER_STORE
|type=object
|default=0
|description=stores the object ID of the leader that was chosen for being a leader, before it is switched (used in the climax)
}}
{{Variable table row
|name= PARTY_OVERRIDE_DIALOG
|type= resource
|default= NONE
|description=
}}
{{Variable table row
|name= PARTY_OVERRIDE_DIALOG_ACTIVE
|type= int
|default= NONE
|description=
}}
{{Variable table row
|name= PARTY_PICKER_GUI_ALLOWED_TO_POP_UP
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= PARTY_TRIGGER_DIALOG_FILE
|type= resource
|default= NONE
|description=
}}
{{Variable table row
|name= PARTY_TRIGGER_PLOT
|type= string
|default=
|description=
}}
{{Variable table row
|name= PROVING_FIGHT_ID
|type= int
|default= 0
|description= Variable related to a specific plot in Dragon Age: Origins
}}
{{Variable table row
|name= RAND_*_SET
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= RUNSCRIPT_VAR
|type= string
|default=
|description= When the [[console]] command "runscript" is used, this variable will contain a string with any parameters that the script was given. The script will need to retrieve and parse these itself.
}}
{{Variable table row
|name= STEALING_*_COUNTER
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= TRACKING_GAME_ID
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= TRACKING_SEQ_NO
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= TUTORIAL_ENABLED
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= TUTORIAL_HAVE_SEEN_LEVEL_UP
|type= int
|default= 0
|description=
}}
{{Variable table row
|name= WM_STORED_AREA
|type= string
|default=
|description= last used area - will be triggered when returning from a random encounter
}}
{{Variable table row
|name= WM_STORED_WP
|type= string
|default=
|description= last used transition wp - will be used when returning from a random encounter
}}
{{Variable table row
|name= WORLD_MAP_STORED_PRE_CAMP_AREA
|type= string
|default=
|description= The WIDE OPEN WORLD area that was visited last. Used when leaving the camp so we can know if the player returns to it from the camp and then just directly transition there instead of travel.
}}
{{Variable table row
|name= WORLD_MAPS_TRIP_COUNT
|type= int
|default= 0
|description= counting the number of trips the player did in the world map, on any map in the game. Used to determine when to trigger random encounters.
}}
{{Variable table row
|name= WRD_*
|type= int
|default= 0
|description=
}}
{{variable table end}}

[[category:modules]]

Reskinning an item tutorial

2010-03-03T01:05:21Z

Imkilo: /* Locating the Model Textures the Hard Way */

__TOC__

This tutorial describes how to reskin, or change the default texture, of items that already exist in-game. As an example, the default textures of the human female mage's apprentice robes will be changed.

Tools needed are the Dragon Age Toolset, and a grafic editing Applications capable of Opening, Editing and Saving DDS Texture Files.

'''Note:''' The game utilizes Tints, which reuse the same Texture in colorized or tinted versions. Thus the texture in our example doesnt look quiet as it does in game. And vice versa, if you edit the Texture, it wont look quiet like that when back into the game. The difference is merely color differences. So this process is limited. However you can only change Tints, or both. See below for further tutorials.

== Locating the Model Textures the Hard Way==

At the beginning, you only know how the [[Model]] looks and what its called. A somewhat difficult task will be, finding out which files are tied to the model so that you can edit them.

'''Note:''' You may want to read it once, to understand alternative ways.

First and foremost, you are looking for DDS Files. How DDS Files are referenced by an Item you see in Game is a long list of database references.

A quick rundown on references we need to be aware of

#A DDS File is referenced by the Material Properties of a [[Model]]
#A [[Model]] is then referenced by the "ItemVariation" type of files. In our example, the sub "clothing_variation.gda"
#The different Clothing Variations are then referenced by the Item Type made via the Toolset
#The Item Type is lastly referenced by the Game, when choosing which gender and race this item is worn. And then displays the final version in your game.

-----

To track back to the DDS File, you need to run up this list in reverse. Starting up our example, the mages apprentice robe, as it is worn by human females.

#Open up the Toolset and in the Resource Palette on the upperright click on "Items" (appears as a sword icon). Now comes guessing where this piece is to be found there. These Items are pretty well sorted thou, it is to be found under _global / Clothing / Mage Robes / Unique. In the following list you see the ResourceName followed by ItemName "gen_im_cth_mag_app (Apprentice Robes)". Any Item can be found in the "Item" Category. Doubleclick that entry to look inside.
#In the listing of information that appears to the left of the item, note that the "Base Item Type" is "Clothing", which is branching off into the Item Variation. The robe has a "Item Variation" called "Robe, Apprentice". Variation in mind, onto the next step.
#Open up the "ItemVariations.xls" File located under "(dragon age install directory)/tools/Source/2da/rules". It has many pages, locate page "clothing_variation" since we know our "Base Item Type" is of "Clothing". In there, locate the Row called whatever Item Variation your Item had. "Robe, Apprentice" has Namestrings followed by "rob" "app" "a".
#With these 3 Strings, and Dragon Age's [[Naming conventions|Naming Scheme]] you can find the binary [[MMH]] Main Modelfile.
#'''In this File is a hidden reference to the [[MAO]] Material file.'''
#And inside the [[MAO]] File is the references to the Textures Filenames.

Step 4 requires some understanding in completing the Filename. Each [[Model]] File (and [[Art Resources|Art Resource]] too) has a prefix and a suffix. The Prefix sorts the Models into whole Categories, the Suffix into small Variations. The Category for Playerworn Armor by Human Females here is "HF". After the Prefix come the Namestrings noted in Step 3 ,separated by underscores "_" with the exception of the last one. The Suffix here as a variation is the LOD Versions of the same Model, which all have their own LOD texture.

The Models Filename here is then "hf_rob_appa_0.mmh" to "hf_rob_appa_3.mmh". However unless you can work with the MMH, the hidden reference of Step 6 wont be found. It is there in binary form, and u would need for example "tazpn's commandline tools" to convert them into FBX and then into MMH.XML which is a text format of the [[MMH]]. The reference here is called "pf_rob_appa.mao", "pf_rob_appa_l2.mao" and "pf_rob_appa_l3.mao" for their respective LOD Version.

See that effectivly hf got replaced by pf, which is simply another Prefix for only Female Gear. "hf" however was Female Human, but since the Textures get applied to all Female's versions, it is separated. This is arbitrary, but since the same applies to other armor ,it is sometimes "guessable"

The MAO Files reference these textures

<pre>pf_rob_appa_0d.dds
to
pf_rob_appa_0tl3.dds
</pre>

=== Alternatives ===

However you can take shortcuts, by guessing which ItemVariation it is under which category, and start by opening the "Itemvariations.xls" file directly. Or by browsing texture files with a Picture Viewer. Since pf_rob*** are only Robes, and its not so many.

DATools also provides a quick way of browsing thru Models, and seeing their Texturenames. You may not catch all Models, but its a possibility.

Guessing examples for the Mage Robe:
*It is female player gear. So prefix for textures is "pf_"
*It is a Robe, so any Texture File containing "rob" may be our File.
*Open the ItemVariations.xls, and by Clothing find Robe, Apprentice and its strings "rob" "app" "a" ,and you may find the filename.

== Extracting the Texture from the Package ==

Model textures are located in two "texturepack.erf" [[ERF]] packages, corresponding to high resolution and medium resolution textures. These packages can be found in the (dragon age install directory)\packages\core\textures\ folder. For example, the packages might be:

<pre>C:\Program Files\Dragon Age\packages\core\textures\high\texturepack.erf
C:\Program Files\Dragon Age\packages\core\textures\medium\texturepack.erf</pre>

Drag and drop these ERF Files onto the Toolset to browse and extract their content. If you have the Name, finding the Files will be easy. The Files will be in both "high" and "medium" and the quality setting in the game will decide which to choose. To make it compatible enough, taking them all may be neccessary.

To prepare for extracting the textures, we must create a directory mimicking the structure of the Dragon Age packages folder. To do this, create a new folder named "textures" in a convenient location (for example, on your desktop). Inside this folder, create two new folders, named "high" and "medium". The "high" folder will be where the high-resolution textures are extracted to, and the "medium" folder will be where the medium-resolution textures are extracted to.

For this tutorial, we are interested in the mage's robes. To locate the textures of the mage's robes, scroll down to "pf_rob_appa_0d.dds" in one of the two texturepack ERFs. In each texturepack.erf, select all of the image files prefixed with "pf_rob_appa" (from "pf_rob_appa_0d.dds" to "pf_rob_appa_0tl3.dds"). For the high-resolution texturepack.erf, extract these images to the "textures\high\" folder just created. Extract the medium-resolution textures to the "textures\medium\" folder.

The Suffixes for Texturefiles are describing their Formats, which is described under [[Textureformats]].

To extract one of the textures, right-click on it and select "Extract Resource."

== Editing the Textures ==

At this stage, if we wanted to edit the existing robe textures, we could do so by changing these files. See [[Textureformats]].

Once this has been done for all of the robe textures (in both the "High" and "Medium" folders), we'll be ready to override the default textures in Dragon Age.

== Overriding the Existing Textures ==
[[Image:Demo-retexture.jpg|thumb|The end result: reskinned default mage robes.]]
To override the existing textures, copy the "textures" folder containing the modified textures, and paste this folder into the Dragon Age override folder. The override folder is found in:
*Documents\BioWare\Dragon Age\packages\core\override\
for Windows Vista and 7, and in a similar location on Windows XP.

So, after pasting in the modified textures, the structure of the override folder should look like this:

*Documents\BioWare\Dragon Age\packages\core\override\
**textures
***high
****pf_rob_appa_0d.dds
****(...)
****pf_rob_appa_0tl3.dds
***medium
****pf_rob_appa_0d.dds
****(...)
****pf_rob_appa_0tl3.dds

== Further Tutorials ==

[[Tutorial: Creating recolors of existing items]] - A way to change the tint of the new texture

== Related Links ==

[[Texture Formats]] - Texture formats in detail.

[[Art Resources]] - Broad topic of Art Resources, which textures are a part of.

[[category:tutorials]]
[[Category:Textures]]

Reskinning an item tutorial

2010-03-03T00:58:35Z

Imkilo: /* Locating the Model Textures the Hard Way */

__TOC__

This tutorial describes how to reskin, or change the default texture, of items that already exist in-game. As an example, the default textures of the human female mage's apprentice robes will be changed.

Tools needed are the Dragon Age Toolset, and a grafic editing Applications capable of Opening, Editing and Saving DDS Texture Files.

'''Note:''' The game utilizes Tints, which reuse the same Texture in colorized or tinted versions. Thus the texture in our example doesnt look quiet as it does in game. And vice versa, if you edit the Texture, it wont look quiet like that when back into the game. The difference is merely color differences. So this process is limited. However you can only change Tints, or both. See below for further tutorials.

== Locating the Model Textures the Hard Way==

At the beginning, you only know how the [[Model]] looks and what its called. A somewhat difficult task will be, finding out which files are tied to the model so that you can edit them.

'''Note:''' You may want to read it once, to understand alternative ways.

First and foremost, you are looking for DDS Files. How DDS Files are referenced by an Item you see in Game is a long list of database references.

A quick rundown on references we need to be aware of

#A DDS File is referenced by the Material Properties of a [[Model]]
#A [[Model]] is then referenced by the "ItemVariation" type of files. In our example, the sub "clothing_variation.gda"
#The different Clothing Variations are then referenced by the Item Type made via the Toolset
#The Item Type is lastly referenced by the Game, when choosing which gender and race this item is worn. And then displays the final version in your game.

-----

To track back to the DDS File, you need to run up this list in reverse. Starting up our example, the mages apprentice robe, as it is worn by human females.

#Open up the Toolset and in the Resource Palette on the upperright click on "Items" (appears as a sword icon). Now comes guessing where this piece is to be found there. These Items are pretty well sorted thou, it is to be found under _global / Clothing / Mage Robes / Unique. In the following list you see the ResourceName followed by ItemName "gen_im_cth_mag_app (Apprentice Robes)". Any Item can be found in the "Item" Category. Doubleclick that entry to look inside.
#In the listing of information that appears to the left of the item, note that the "Base Item Type" is "Clothing", which is branching off into the Item Variation. The robe has a "Item Variation" called "Robe, Apprentice". Variation in mind, onto the next step.
#Open up the "ItemVariations.xls" File located under "(dragon age install directory)/tools/Source/2da/rules". It has many pages, locate Page "clothing variation" since we know our Item is of Clothing Item Type. In there, locate the Row called whatever Item Variation your Item had. "Robe, Apprentice" has Namestrings followed by "rob" "app" "a".
#With these 3 Strings, and Dragon Age's [[Naming conventions|Naming Scheme]] you can find the binary [[MMH]] Main Modelfile.
#'''In this File is a hidden reference to the [[MAO]] Material file.'''
#And inside the [[MAO]] File is the references to the Textures Filenames.

Step 4 requires some understanding in completing the Filename. Each [[Model]] File (and [[Art Resources|Art Resource]] too) has a prefix and a suffix. The Prefix sorts the Models into whole Categories, the Suffix into small Variations. The Category for Playerworn Armor by Human Females here is "HF". After the Prefix come the Namestrings noted in Step 3 ,separated by underscores "_" with the exception of the last one. The Suffix here as a variation is the LOD Versions of the same Model, which all have their own LOD texture.

The Models Filename here is then "hf_rob_appa_0.mmh" to "hf_rob_appa_3.mmh". However unless you can work with the MMH, the hidden reference of Step 6 wont be found. It is there in binary form, and u would need for example "tazpn's commandline tools" to convert them into FBX and then into MMH.XML which is a text format of the [[MMH]]. The reference here is called "pf_rob_appa.mao", "pf_rob_appa_l2.mao" and "pf_rob_appa_l3.mao" for their respective LOD Version.

See that effectivly hf got replaced by pf, which is simply another Prefix for only Female Gear. "hf" however was Female Human, but since the Textures get applied to all Female's versions, it is separated. This is arbitrary, but since the same applies to other armor ,it is sometimes "guessable"

The MAO Files reference these textures

<pre>pf_rob_appa_0d.dds
to
pf_rob_appa_0tl3.dds
</pre>

=== Alternatives ===

However you can take shortcuts, by guessing which ItemVariation it is under which category, and start by opening the "Itemvariations.xls" file directly. Or by browsing texture files with a Picture Viewer. Since pf_rob*** are only Robes, and its not so many.

DATools also provides a quick way of browsing thru Models, and seeing their Texturenames. You may not catch all Models, but its a possibility.

Guessing examples for the Mage Robe:
*It is female player gear. So prefix for textures is "pf_"
*It is a Robe, so any Texture File containing "rob" may be our File.
*Open the ItemVariations.xls, and by Clothing find Robe, Apprentice and its strings "rob" "app" "a" ,and you may find the filename.

== Extracting the Texture from the Package ==

Model textures are located in two "texturepack.erf" [[ERF]] packages, corresponding to high resolution and medium resolution textures. These packages can be found in the (dragon age install directory)\packages\core\textures\ folder. For example, the packages might be:

<pre>C:\Program Files\Dragon Age\packages\core\textures\high\texturepack.erf
C:\Program Files\Dragon Age\packages\core\textures\medium\texturepack.erf</pre>

Drag and drop these ERF Files onto the Toolset to browse and extract their content. If you have the Name, finding the Files will be easy. The Files will be in both "high" and "medium" and the quality setting in the game will decide which to choose. To make it compatible enough, taking them all may be neccessary.

To prepare for extracting the textures, we must create a directory mimicking the structure of the Dragon Age packages folder. To do this, create a new folder named "textures" in a convenient location (for example, on your desktop). Inside this folder, create two new folders, named "high" and "medium". The "high" folder will be where the high-resolution textures are extracted to, and the "medium" folder will be where the medium-resolution textures are extracted to.

For this tutorial, we are interested in the mage's robes. To locate the textures of the mage's robes, scroll down to "pf_rob_appa_0d.dds" in one of the two texturepack ERFs. In each texturepack.erf, select all of the image files prefixed with "pf_rob_appa" (from "pf_rob_appa_0d.dds" to "pf_rob_appa_0tl3.dds"). For the high-resolution texturepack.erf, extract these images to the "textures\high\" folder just created. Extract the medium-resolution textures to the "textures\medium\" folder.

The Suffixes for Texturefiles are describing their Formats, which is described under [[Textureformats]].

To extract one of the textures, right-click on it and select "Extract Resource."

== Editing the Textures ==

At this stage, if we wanted to edit the existing robe textures, we could do so by changing these files. See [[Textureformats]].

Once this has been done for all of the robe textures (in both the "High" and "Medium" folders), we'll be ready to override the default textures in Dragon Age.

== Overriding the Existing Textures ==
[[Image:Demo-retexture.jpg|thumb|The end result: reskinned default mage robes.]]
To override the existing textures, copy the "textures" folder containing the modified textures, and paste this folder into the Dragon Age override folder. The override folder is found in:
*Documents\BioWare\Dragon Age\packages\core\override\
for Windows Vista and 7, and in a similar location on Windows XP.

So, after pasting in the modified textures, the structure of the override folder should look like this:

*Documents\BioWare\Dragon Age\packages\core\override\
**textures
***high
****pf_rob_appa_0d.dds
****(...)
****pf_rob_appa_0tl3.dds
***medium
****pf_rob_appa_0d.dds
****(...)
****pf_rob_appa_0tl3.dds

== Further Tutorials ==

[[Tutorial: Creating recolors of existing items]] - A way to change the tint of the new texture

== Related Links ==

[[Texture Formats]] - Texture formats in detail.

[[Art Resources]] - Broad topic of Art Resources, which textures are a part of.

[[category:tutorials]]
[[Category:Textures]]

Reskinning an item tutorial

2010-03-03T00:53:35Z

Imkilo: /* Locating the Model Textures the Hard Way */

__TOC__

This tutorial describes how to reskin, or change the default texture, of items that already exist in-game. As an example, the default textures of the human female mage's apprentice robes will be changed.

Tools needed are the Dragon Age Toolset, and a grafic editing Applications capable of Opening, Editing and Saving DDS Texture Files.

'''Note:''' The game utilizes Tints, which reuse the same Texture in colorized or tinted versions. Thus the texture in our example doesnt look quiet as it does in game. And vice versa, if you edit the Texture, it wont look quiet like that when back into the game. The difference is merely color differences. So this process is limited. However you can only change Tints, or both. See below for further tutorials.

== Locating the Model Textures the Hard Way==

At the beginning, you only know how the [[Model]] looks and what its called. A somewhat difficult task will be, finding out which files are tied to the model so that you can edit them.

'''Note:''' You may want to read it once, to understand alternative ways.

First and foremost, you are looking for DDS Files. How DDS Files are referenced by an Item you see in Game is a long list of database references.

A quick rundown on references we need to be aware of

#A DDS File is referenced by the Material Properties of a [[Model]]
#A [[Model]] is then referenced by the "ItemVariation" type of files. In our example, the sub "clothing_variation.gda"
#The different Clothing Variations are then referenced by the Item Type made via the Toolset
#The Item Type is lastly referenced by the Game, when choosing which gender and race this item is worn. And then displays the final version in your game.

-----

To track back to the DDS File, you need to run up this list in reverse. Starting up our example, the mages apprentice robe, as it is worn by human females.

#Open up the Toolset and in the Resource Palette on the upperright click on "Items" (sword icon). Now comes guessing where this piece is to be found there. These Items are pretty well sorted thou, it is to be found under _global / Clothing / Mage Robes / Unique. In the following list you see the ResourceName followed by ItemName "gen_im_cth_mag_app (Apprentice Robes)". Any Item can be found in the "Item" Category. Doubleclick that entry to look inside.
#In the listing of information that appears to the left of the item, note that the "Base Item Type" is "Clothing", which is branching off into the Item Variation. The Robe has a Item Variation called "Robe, Apprentice". Variation in mind, onto the next step.
#Open up the "ItemVariations.xls" File located under "(dragon age install directory)/tools/Source/2da/rules". It has many pages, locate Page "clothing variation" since we know our Item is of Clothing Item Type. In there, locate the Row called whatever Item Variation your Item had. "Robe, Apprentice" has Namestrings followed by "rob" "app" "a".
#With these 3 Strings, and Dragon Age's [[Naming conventions|Naming Scheme]] you can find the binary [[MMH]] Main Modelfile.
#'''In this File is a hidden reference to the [[MAO]] Material file.'''
#And inside the [[MAO]] File is the references to the Textures Filenames.

Step 4 requires some understanding in completing the Filename. Each [[Model]] File (and [[Art Resources|Art Resource]] too) has a prefix and a suffix. The Prefix sorts the Models into whole Categories, the Suffix into small Variations. The Category for Playerworn Armor by Human Females here is "HF". After the Prefix come the Namestrings noted in Step 3 ,separated by underscores "_" with the exception of the last one. The Suffix here as a variation is the LOD Versions of the same Model, which all have their own LOD texture.

The Models Filename here is then "hf_rob_appa_0.mmh" to "hf_rob_appa_3.mmh". However unless you can work with the MMH, the hidden reference of Step 6 wont be found. It is there in binary form, and u would need for example "tazpn's commandline tools" to convert them into FBX and then into MMH.XML which is a text format of the [[MMH]]. The reference here is called "pf_rob_appa.mao", "pf_rob_appa_l2.mao" and "pf_rob_appa_l3.mao" for their respective LOD Version.

See that effectivly hf got replaced by pf, which is simply another Prefix for only Female Gear. "hf" however was Female Human, but since the Textures get applied to all Female's versions, it is separated. This is arbitrary, but since the same applies to other armor ,it is sometimes "guessable"

The MAO Files reference these textures

<pre>pf_rob_appa_0d.dds
to
pf_rob_appa_0tl3.dds
</pre>

=== Alternatives ===

However you can take shortcuts, by guessing which ItemVariation it is under which category, and start by opening the "Itemvariations.xls" file directly. Or by browsing texture files with a Picture Viewer. Since pf_rob*** are only Robes, and its not so many.

DATools also provides a quick way of browsing thru Models, and seeing their Texturenames. You may not catch all Models, but its a possibility.

Guessing examples for the Mage Robe:
*It is female player gear. So prefix for textures is "pf_"
*It is a Robe, so any Texture File containing "rob" may be our File.
*Open the ItemVariations.xls, and by Clothing find Robe, Apprentice and its strings "rob" "app" "a" ,and you may find the filename.

== Extracting the Texture from the Package ==

Model textures are located in two "texturepack.erf" [[ERF]] packages, corresponding to high resolution and medium resolution textures. These packages can be found in the (dragon age install directory)\packages\core\textures\ folder. For example, the packages might be:

<pre>C:\Program Files\Dragon Age\packages\core\textures\high\texturepack.erf
C:\Program Files\Dragon Age\packages\core\textures\medium\texturepack.erf</pre>

Drag and drop these ERF Files onto the Toolset to browse and extract their content. If you have the Name, finding the Files will be easy. The Files will be in both "high" and "medium" and the quality setting in the game will decide which to choose. To make it compatible enough, taking them all may be neccessary.

To prepare for extracting the textures, we must create a directory mimicking the structure of the Dragon Age packages folder. To do this, create a new folder named "textures" in a convenient location (for example, on your desktop). Inside this folder, create two new folders, named "high" and "medium". The "high" folder will be where the high-resolution textures are extracted to, and the "medium" folder will be where the medium-resolution textures are extracted to.

For this tutorial, we are interested in the mage's robes. To locate the textures of the mage's robes, scroll down to "pf_rob_appa_0d.dds" in one of the two texturepack ERFs. In each texturepack.erf, select all of the image files prefixed with "pf_rob_appa" (from "pf_rob_appa_0d.dds" to "pf_rob_appa_0tl3.dds"). For the high-resolution texturepack.erf, extract these images to the "textures\high\" folder just created. Extract the medium-resolution textures to the "textures\medium\" folder.

The Suffixes for Texturefiles are describing their Formats, which is described under [[Textureformats]].

To extract one of the textures, right-click on it and select "Extract Resource."

== Editing the Textures ==

At this stage, if we wanted to edit the existing robe textures, we could do so by changing these files. See [[Textureformats]].

Once this has been done for all of the robe textures (in both the "High" and "Medium" folders), we'll be ready to override the default textures in Dragon Age.

== Overriding the Existing Textures ==
[[Image:Demo-retexture.jpg|thumb|The end result: reskinned default mage robes.]]
To override the existing textures, copy the "textures" folder containing the modified textures, and paste this folder into the Dragon Age override folder. The override folder is found in:
*Documents\BioWare\Dragon Age\packages\core\override\
for Windows Vista and 7, and in a similar location on Windows XP.

So, after pasting in the modified textures, the structure of the override folder should look like this:

*Documents\BioWare\Dragon Age\packages\core\override\
**textures
***high
****pf_rob_appa_0d.dds
****(...)
****pf_rob_appa_0tl3.dds
***medium
****pf_rob_appa_0d.dds
****(...)
****pf_rob_appa_0tl3.dds

== Further Tutorials ==

[[Tutorial: Creating recolors of existing items]] - A way to change the tint of the new texture

== Related Links ==

[[Texture Formats]] - Texture formats in detail.

[[Art Resources]] - Broad topic of Art Resources, which textures are a part of.

[[category:tutorials]]
[[Category:Textures]]

Reskinning an item tutorial

2010-03-03T00:47:44Z

Imkilo: /* Locating the Model Textures the Hard Way */

__TOC__

This tutorial describes how to reskin, or change the default texture, of items that already exist in-game. As an example, the default textures of the human female mage's apprentice robes will be changed.

Tools needed are the Dragon Age Toolset, and a grafic editing Applications capable of Opening, Editing and Saving DDS Texture Files.

'''Note:''' The game utilizes Tints, which reuse the same Texture in colorized or tinted versions. Thus the texture in our example doesnt look quiet as it does in game. And vice versa, if you edit the Texture, it wont look quiet like that when back into the game. The difference is merely color differences. So this process is limited. However you can only change Tints, or both. See below for further tutorials.

== Locating the Model Textures the Hard Way==

At the beginning, you only know how the [[Model]] looks and what its called. A somewhat difficult task will be, finding out which files are tied to the model so that you can edit them.

'''Note:''' You may want to read it once, to understand alternative ways.

First and foremost, you are looking for DDS Files. How DDS Files are referenced by an Item you see in Game is a long list of database references.

A quick rundown on references we need to be aware of

#A DDS File is referenced by the Material Properties of a [[Model]]
#A [[Model]] is then referenced by the "ItemVariation" type of files. In our example, the sub "clothing_variation.gda"
#The different Clothing Variations are then referenced by the Item Type made via the Toolset
#The Item Type is lastly referenced by the Game, when choosing which gender and race this item is worn. And then displays the final version in your game.

-----

To track back to the DDS File, you need to run up this list in reverse. Starting up our example, the mages apprentice robe, as it is worn by human females.

#Open up the Toolset and in the Resource Palette on the upperright click on "Items" (sword icon). Now comes guessing where this piece is to be found there. These Items are pretty well sorted thou, it is to be found under _global / Clothing / Mage Robes / Unique. In the following list you see the ResourceName followed by ItemName "gen_im_cth_mag_app (Apprentice Robes)". Any Item can be found in the "Item" Category. Doubleclick that entry to look inside.
#Base Item Type is Clothing, which is branching off into the Item Variation. The Robe has a Item Variation called "Robe, Apprentice". Variation in mind, onto the next step.
#Open up the "ItemVariations.xls" File located under "(dragon age install directory)/tools/Source/2da/rules". It has many pages, locate Page "clothing variation" since we know our Item is of Clothing Item Type. In there, locate the Row called whatever Item Variation your Item had. "Robe, Apprentice" has Namestrings followed by "rob" "app" "a".
#With these 3 Strings, and Dragon Age's [[Naming conventions|Naming Scheme]] you can find the binary [[MMH]] Main Modelfile.
#'''In this File is a hidden reference to the [[MAO]] Material file.'''
#And inside the [[MAO]] File is the references to the Textures Filenames.

Step 4 requires some understanding in completing the Filename. Each [[Model]] File (and [[Art Resources|Art Resource]] too) has a prefix and a suffix. The Prefix sorts the Models into whole Categories, the Suffix into small Variations. The Category for Playerworn Armor by Human Females here is "HF". After the Prefix come the Namestrings noted in Step 3 ,separated by underscores "_" with the exception of the last one. The Suffix here as a variation is the LOD Versions of the same Model, which all have their own LOD texture.

The Models Filename here is then "hf_rob_appa_0.mmh" to "hf_rob_appa_3.mmh". However unless you can work with the MMH, the hidden reference of Step 6 wont be found. It is there in binary form, and u would need for example "tazpn's commandline tools" to convert them into FBX and then into MMH.XML which is a text format of the [[MMH]]. The reference here is called "pf_rob_appa.mao", "pf_rob_appa_l2.mao" and "pf_rob_appa_l3.mao" for their respective LOD Version.

See that effectivly hf got replaced by pf, which is simply another Prefix for only Female Gear. "hf" however was Female Human, but since the Textures get applied to all Female's versions, it is separated. This is arbitrary, but since the same applies to other armor ,it is sometimes "guessable"

The MAO Files reference these textures

<pre>pf_rob_appa_0d.dds
to
pf_rob_appa_0tl3.dds
</pre>

=== Alternatives ===

However you can take shortcuts, by guessing which ItemVariation it is under which category, and start by opening the "Itemvariations.xls" file directly. Or by browsing texture files with a Picture Viewer. Since pf_rob*** are only Robes, and its not so many.

DATools also provides a quick way of browsing thru Models, and seeing their Texturenames. You may not catch all Models, but its a possibility.

Guessing examples for the Mage Robe:
*It is female player gear. So prefix for textures is "pf_"
*It is a Robe, so any Texture File containing "rob" may be our File.
*Open the ItemVariations.xls, and by Clothing find Robe, Apprentice and its strings "rob" "app" "a" ,and you may find the filename.

== Extracting the Texture from the Package ==

Model textures are located in two "texturepack.erf" [[ERF]] packages, corresponding to high resolution and medium resolution textures. These packages can be found in the (dragon age install directory)\packages\core\textures\ folder. For example, the packages might be:

<pre>C:\Program Files\Dragon Age\packages\core\textures\high\texturepack.erf
C:\Program Files\Dragon Age\packages\core\textures\medium\texturepack.erf</pre>

Drag and drop these ERF Files onto the Toolset to browse and extract their content. If you have the Name, finding the Files will be easy. The Files will be in both "high" and "medium" and the quality setting in the game will decide which to choose. To make it compatible enough, taking them all may be neccessary.

To prepare for extracting the textures, we must create a directory mimicking the structure of the Dragon Age packages folder. To do this, create a new folder named "textures" in a convenient location (for example, on your desktop). Inside this folder, create two new folders, named "high" and "medium". The "high" folder will be where the high-resolution textures are extracted to, and the "medium" folder will be where the medium-resolution textures are extracted to.

For this tutorial, we are interested in the mage's robes. To locate the textures of the mage's robes, scroll down to "pf_rob_appa_0d.dds" in one of the two texturepack ERFs. In each texturepack.erf, select all of the image files prefixed with "pf_rob_appa" (from "pf_rob_appa_0d.dds" to "pf_rob_appa_0tl3.dds"). For the high-resolution texturepack.erf, extract these images to the "textures\high\" folder just created. Extract the medium-resolution textures to the "textures\medium\" folder.

The Suffixes for Texturefiles are describing their Formats, which is described under [[Textureformats]].

To extract one of the textures, right-click on it and select "Extract Resource."

== Editing the Textures ==

At this stage, if we wanted to edit the existing robe textures, we could do so by changing these files. See [[Textureformats]].

Once this has been done for all of the robe textures (in both the "High" and "Medium" folders), we'll be ready to override the default textures in Dragon Age.

== Overriding the Existing Textures ==
[[Image:Demo-retexture.jpg|thumb|The end result: reskinned default mage robes.]]
To override the existing textures, copy the "textures" folder containing the modified textures, and paste this folder into the Dragon Age override folder. The override folder is found in:
*Documents\BioWare\Dragon Age\packages\core\override\
for Windows Vista and 7, and in a similar location on Windows XP.

So, after pasting in the modified textures, the structure of the override folder should look like this:

*Documents\BioWare\Dragon Age\packages\core\override\
**textures
***high
****pf_rob_appa_0d.dds
****(...)
****pf_rob_appa_0tl3.dds
***medium
****pf_rob_appa_0d.dds
****(...)
****pf_rob_appa_0tl3.dds

== Further Tutorials ==

[[Tutorial: Creating recolors of existing items]] - A way to change the tint of the new texture

== Related Links ==

[[Texture Formats]] - Texture formats in detail.

[[Art Resources]] - Broad topic of Art Resources, which textures are a part of.

[[category:tutorials]]
[[Category:Textures]]