Dragon Age Toolset Wiki - User contributions [en]

User:Apolyon6k/Class tutorial extended (Draft)

2011-01-16T07:49:20Z

Apolyon6k: /* Create new abilities */

This is just a draft, throwing together some ideas. I will flesh it out over time and make a real tutorial out of it...

The "Add a new class" tutorial was good to start with but to basic for my taste so I have to create my own tutorial to cover all the aspects of a custom class I need.
==The Basics==
Follow the [[Add_A_New_Class_Tutorial|"Add A New Class" tutorial]]. After that tutorial you have a new class by name only. You will still have the vanilla abilities, for magic users those are the four "schools"(Creation, Primal, Entropy, Spirit) and for non-magicians there are two-weapon fighting and archery.

==Create new abilities==
There is a tutorial for that out there.
So far I was able to create spells and talents.

Skills on the other hand are a little resistent, the basics are the same but when I implemented them they interfered with the overall skills.
===Editing needed GDAs===
The tables that need editing are ''ABI_base'' and ''guitypes''.

The ''guitypes'' table is needed for headlines like the different spell categories or the combat styles as well as for any class related headlines.
It is here where the class name will be added and can later be referenced in ''ABI_base''.

The ''ABI_base'' table...

==Putting it together==
If the new abilities are designed they are put into the AL*your classname*.xls and processed to get the gda.
That gda is put into the ...\module\override\ folder and hopefully the game recognises it and you can use your abilites.

User:Apolyon6k/Class tutorial extended (Draft)

2011-01-16T07:48:25Z

Apolyon6k: /* Create new abilities */

This is just a draft, throwing together some ideas. I will flesh it out over time and make a real tutorial out of it...

The "Add a new class" tutorial was good to start with but to basic for my taste so I have to create my own tutorial to cover all the aspects of a custom class I need.
==The Basics==
Follow the [[Add_A_New_Class_Tutorial|"Add A New Class" tutorial]]. After that tutorial you have a new class by name only. You will still have the vanilla abilities, for magic users those are the four "schools"(Creation, Primal, Entropy, Spirit) and for non-magicians there are two-weapon fighting and archery.

==Create new abilities==
There is a tutorial for that out there.
So far I was able to create spells and talents.
Skills on the other hand are a little resistent, the basics are the same but when I implemented them they interfered with the overall skills.
===Editing needed GDAs===
The tables that need editing are ''ABI_base'' and ''guitypes''.

The ''guitypes'' table is needed for headlines like the different spell categories or the combat styles as well as for any class related headlines.
It is here where the class name will be added and can later be referenced in ''ABI_base''.

The ''ABI_base'' table...

==Putting it together==
If the new abilities are designed they are put into the AL*your classname*.xls and processed to get the gda.
That gda is put into the ...\module\override\ folder and hopefully the game recognises it and you can use your abilites.

User:Apolyon6k

2010-12-21T01:33:43Z

Apolyon6k:

User:Apolyon6k/Class tutorial extended (Draft)

2010-12-21T01:32:42Z

Apolyon6k: /* The Basics */

User:Apolyon6k/Class tutorial extended (Draft)

2010-12-21T01:31:41Z

Apolyon6k: moved User:Apolyon6k/Class tutorial extented to User:Apolyon6k/Class tutorial extended (Draft)

User:Apolyon6k/Class tutorial extented

2010-12-21T01:31:41Z

Apolyon6k: moved User:Apolyon6k/Class tutorial extented to User:Apolyon6k/Class tutorial extended (Draft)

#REDIRECT [[User:Apolyon6k/Class tutorial extended (Draft)]]

User:Apolyon6k/Class tutorial extended (Draft)

2010-12-21T01:31:08Z

Apolyon6k: Created page with 'This is just a draft, throwing together some ideas. I will flesh it out over time and make a real tutorial out of it... The "Add a new class" tutorial was good to start with but ...'

User:Apolyon6k

2010-12-21T01:19:20Z

Apolyon6k:

simple user with some wiki experience

likes to edit tables and tries to remove horizontal scrolling from webpages...

----

[[/Class_tutorial_extented|tutorial for advanced classes]]

Talk:Conversation

2010-12-14T22:40:57Z

Apolyon6k: /* NPC saying more than one line */

== NPC saying more than one line ==

In-game you'll notice that NPCs will have multiple lines before the player can respond. They'll say one line, with a slight break, then say another line, and so on until its time for the player to speak up. My first attempt at this was just to have multiple OWNER lines in a row, but each line is a branch, and of course didnt work. My second attempt was to add empty player lines. If you have an owner reply to the empty line, the END DIALOGUE becomes CONTINUE. Tho, I had to add text to the line then clear it for the change to happen. But in game, the only button I could press that would continue the conversation was ESC. What is the proper way to make this happen? [[User:Interitus3841|Interitus3841]] 10:22, 29 November 2009 (UTC)

Update: Instead of a blank response, or making that CONTINUE line, I just make the only dialogue choice to be "<desc>continue</desc>". Seems to work, tho I figured there would be a more seemless way to do this.

Yes, there is:
After the OWNER line set a PLAYER line and change the Fast Pass option in the lower right corner to fast pass. The PLAYER lines will be automatically skipped and the NPC seems to speak multiple lines without much break. But think about the amount of text you confront the player with in those cases maybe a codex entry would be better. It is a good way to use henchmen interjections though or if you want other people standing near the OWNER to speak one or two lines without giving them their own conversation. [[User:Apolyon6k|Apolyon6k]] 22:40, 14 December 2010 (UTC)

Talk:Add A New Class Tutorial

2010-12-11T03:59:39Z

Apolyon6k: /* Cleaning up errors? */

== Initial edit ==
I have started to edit this page at the author's request to try and fix up some of the formatting. It was prety much a cut and paste from the forum. I think it has a way to go yet. I would recommend replacing all the capitalised text with appropriate markup such as '''bold'''. Also the structure could perhaps be improved and some of the content organised better in sentences rather than point form. Please help out if you have the time and incliniation. [[User:Stuntpope|Stuntpope]]

=== edit ===
Embedded all images and added dascript tages

--[[User:Rigortauri|Rigortauri]] 13:12, 2 December 2009 (UTC)

did some table formating

--[[User:Apolyon6k|Apolyon6k]] 09:14, 2 January 2010 (UTC)

== Errors ==

The following section is incorrect:

Next goto "// Undo Class and Race selection" and add the 4th CharGen_ClearAbilityList

<dascript>
// Note: This wipes the ability list clear
CharGen_ClearAbilityList(oChar,1);
CharGen_ClearAbilityList(oChar,2);
CharGen_ClearAbilityList(oChar,3);
CharGen_ClearAbilityList(oChar,4);
</dascript>

Next goto "// enabling proper tactics presets" and add the ValidForClass4 parts

<dascript>
nForClass1 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass1", nCurrentRow);
nForClass2 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass2", nCurrentRow);
nForClass3 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass3", nCurrentRow);
nForClass4 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass4", nCurrentRow);
if(nCoreClass == nForClass1 || nCoreClass == nForClass2 || nCoreClass == nForClass3 || nCoreClass == nForClass4)
AddTacticPresetID(oCreature, nCurrentRow);
</dascript>

The author has misunderstood the purpose of these methods. There is no need to modify the first of these. The int parameter in CharGen_ClearAbilityList is actually the ability type - not a class id. In the second part there is no point modifying this unless you also modify user tactics 2da table. The three columns allow up to three classes to be listed and since the third column is not used already there is really no need to add a fourth column anyway.

I considered removing this but it really needs to be replaced with the correct approach. I suspect that there are other aspects of AI that need to be dealt with too. [[User:Stuntpope|Stuntpope]] 13:13, 7 December 2009 (UTC)

: I went ahead and deleted it, as those should really be part of an advanced tutorial, rather than a basic one; I also went ahead and added some new data that I've been testing that eliminates the need to provide files in packages\core\override. [[User:Ladydesire|Ladydesire]] 21:48, 29 January 2010 (UTC)
==="Cleaning up" errors?===
I'm not sure but there seems to be an error in the section about cleaning up. If you delete all files you also delete your edited core files (2ds_constants_h and chargen_h). Without those files the new class wouldn't work. It should be mentioned after the export section that those files are needed and that they should be moved to module/core/override.[[User:Apolyon6k|Apolyon6k]] 03:46, 11 December 2010 (UTC)

== String IDs above 8.3 million don't work? ==

There is a discrepancy between the current tutorial and the actual functionality of the toolset with regards to the string table entries; it is no longer necessary to manually set a range for the string tables, as ExcelProcessor now handles up to at least 650,000,000. [[User:Ladydesire|Ladydesire]] 20:18, 16 January 2010 (UTC)

:Heh. I just spent a bit of time asking around the office about this bug too, the line's been in the tutorial since November. And then I posted here on the talk page without reading it completely first, is my face red. I'm going to provisionally remove the line from the "creating a module" section and store it here:

::Make sure your string sets go from in between 8,000,000 - 8,300,000, if it goes above that range the strings will not work. BioWare has already posted about this SQL problem.

:I'm pretty sure this has been fixed now, unless this is a separate bug that we weren't aware of. [[User:BryanDerksen|BryanDerksen]] 23:28, 2 February 2010 (UTC)

:: I've been using a class built with string tables as I indicated in my comment, so I'd say it's safe to remove it. [[User:Ladydesire|Ladydesire]] 22:22, 3 February 2010 (UTC)

== Will there be an advanced class tutorial? ==

This is a basic tutorial for quickly creating new classes, but those classes are rather basic themselves. They use standard spells, talents and abilities but those are not really the right ones for costum classes. In the forum there were questions about custom spells and such, wouldn't it be nice to have a page here that combined or even linked to all the tutorials required to create a full customized class? [[User:Apolyon6k|Apolyon6k]] 03:59, 11 December 2010 (UTC)

Talk:Add A New Class Tutorial

2010-12-11T03:59:07Z

Apolyon6k: /* Will there be an advanced class tutorial? */ new section

== Initial edit ==
I have started to edit this page at the author's request to try and fix up some of the formatting. It was prety much a cut and paste from the forum. I think it has a way to go yet. I would recommend replacing all the capitalised text with appropriate markup such as '''bold'''. Also the structure could perhaps be improved and some of the content organised better in sentences rather than point form. Please help out if you have the time and incliniation. [[User:Stuntpope|Stuntpope]]

=== edit ===
Embedded all images and added dascript tages

--[[User:Rigortauri|Rigortauri]] 13:12, 2 December 2009 (UTC)

did some table formating

--[[User:Apolyon6k|Apolyon6k]] 09:14, 2 January 2010 (UTC)

== Errors ==

The following section is incorrect:

Next goto "// Undo Class and Race selection" and add the 4th CharGen_ClearAbilityList

<dascript>
// Note: This wipes the ability list clear
CharGen_ClearAbilityList(oChar,1);
CharGen_ClearAbilityList(oChar,2);
CharGen_ClearAbilityList(oChar,3);
CharGen_ClearAbilityList(oChar,4);
</dascript>

Next goto "// enabling proper tactics presets" and add the ValidForClass4 parts

<dascript>
nForClass1 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass1", nCurrentRow);
nForClass2 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass2", nCurrentRow);
nForClass3 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass3", nCurrentRow);
nForClass4 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass4", nCurrentRow);
if(nCoreClass == nForClass1 || nCoreClass == nForClass2 || nCoreClass == nForClass3 || nCoreClass == nForClass4)
AddTacticPresetID(oCreature, nCurrentRow);
</dascript>

The author has misunderstood the purpose of these methods. There is no need to modify the first of these. The int parameter in CharGen_ClearAbilityList is actually the ability type - not a class id. In the second part there is no point modifying this unless you also modify user tactics 2da table. The three columns allow up to three classes to be listed and since the third column is not used already there is really no need to add a fourth column anyway.

I considered removing this but it really needs to be replaced with the correct approach. I suspect that there are other aspects of AI that need to be dealt with too. [[User:Stuntpope|Stuntpope]] 13:13, 7 December 2009 (UTC)

: I went ahead and deleted it, as those should really be part of an advanced tutorial, rather than a basic one; I also went ahead and added some new data that I've been testing that eliminates the need to provide files in packages\core\override. [[User:Ladydesire|Ladydesire]] 21:48, 29 January 2010 (UTC)
===Cleaning up errors?===
I'm not sure but there seems to be an error in the section about cleaning up. If you delete all files you also delete your edited core files (2ds_constants_h and chargen_h). Without those files the new class wouldn't work. It should be mentioned after the export section that those files are needed and that they should be moved to module/core/override.[[User:Apolyon6k|Apolyon6k]] 03:46, 11 December 2010 (UTC)

== String IDs above 8.3 million don't work? ==

There is a discrepancy between the current tutorial and the actual functionality of the toolset with regards to the string table entries; it is no longer necessary to manually set a range for the string tables, as ExcelProcessor now handles up to at least 650,000,000. [[User:Ladydesire|Ladydesire]] 20:18, 16 January 2010 (UTC)

:Heh. I just spent a bit of time asking around the office about this bug too, the line's been in the tutorial since November. And then I posted here on the talk page without reading it completely first, is my face red. I'm going to provisionally remove the line from the "creating a module" section and store it here:

::Make sure your string sets go from in between 8,000,000 - 8,300,000, if it goes above that range the strings will not work. BioWare has already posted about this SQL problem.

:I'm pretty sure this has been fixed now, unless this is a separate bug that we weren't aware of. [[User:BryanDerksen|BryanDerksen]] 23:28, 2 February 2010 (UTC)

:: I've been using a class built with string tables as I indicated in my comment, so I'd say it's safe to remove it. [[User:Ladydesire|Ladydesire]] 22:22, 3 February 2010 (UTC)

== Will there be an advanced class tutorial? ==

This is a basic tutorial for quickly creating new classes, but those classes are rather basic themselves. They use standard spells, talents and abilities but those are not really the right ones for costum classes. In the forum there were questions about custom spells and such, wouldn't it be nice to have a page here that combined or even linked to all the tutorials required to create a full customized class? [[User:Apolyon6k|Apolyon6k]] 03:59, 11 December 2010 (UTC)

Talk:Add A New Class Tutorial

2010-12-11T03:46:25Z

Apolyon6k: /* Cleaning up errors? */

== Initial edit ==
I have started to edit this page at the author's request to try and fix up some of the formatting. It was prety much a cut and paste from the forum. I think it has a way to go yet. I would recommend replacing all the capitalised text with appropriate markup such as '''bold'''. Also the structure could perhaps be improved and some of the content organised better in sentences rather than point form. Please help out if you have the time and incliniation. [[User:Stuntpope|Stuntpope]]

=== edit ===
Embedded all images and added dascript tages

--[[User:Rigortauri|Rigortauri]] 13:12, 2 December 2009 (UTC)

did some table formating

--[[User:Apolyon6k|Apolyon6k]] 09:14, 2 January 2010 (UTC)

== Errors ==

The following section is incorrect:

Next goto "// Undo Class and Race selection" and add the 4th CharGen_ClearAbilityList

<dascript>
// Note: This wipes the ability list clear
CharGen_ClearAbilityList(oChar,1);
CharGen_ClearAbilityList(oChar,2);
CharGen_ClearAbilityList(oChar,3);
CharGen_ClearAbilityList(oChar,4);
</dascript>

Next goto "// enabling proper tactics presets" and add the ValidForClass4 parts

<dascript>
nForClass1 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass1", nCurrentRow);
nForClass2 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass2", nCurrentRow);
nForClass3 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass3", nCurrentRow);
nForClass4 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass4", nCurrentRow);
if(nCoreClass == nForClass1 || nCoreClass == nForClass2 || nCoreClass == nForClass3 || nCoreClass == nForClass4)
AddTacticPresetID(oCreature, nCurrentRow);
</dascript>

The author has misunderstood the purpose of these methods. There is no need to modify the first of these. The int parameter in CharGen_ClearAbilityList is actually the ability type - not a class id. In the second part there is no point modifying this unless you also modify user tactics 2da table. The three columns allow up to three classes to be listed and since the third column is not used already there is really no need to add a fourth column anyway.

I considered removing this but it really needs to be replaced with the correct approach. I suspect that there are other aspects of AI that need to be dealt with too. [[User:Stuntpope|Stuntpope]] 13:13, 7 December 2009 (UTC)

: I went ahead and deleted it, as those should really be part of an advanced tutorial, rather than a basic one; I also went ahead and added some new data that I've been testing that eliminates the need to provide files in packages\core\override. [[User:Ladydesire|Ladydesire]] 21:48, 29 January 2010 (UTC)
===Cleaning up errors?===
I'm not sure but there seems to be an error in the section about cleaning up. If you delete all files you also delete your edited core files (2ds_constants_h and chargen_h). Without those files the new class wouldn't work. It should be mentioned after the export section that those files are needed and that they should be moved to module/core/override.[[User:Apolyon6k|Apolyon6k]] 03:46, 11 December 2010 (UTC)

== String IDs above 8.3 million don't work? ==

There is a discrepancy between the current tutorial and the actual functionality of the toolset with regards to the string table entries; it is no longer necessary to manually set a range for the string tables, as ExcelProcessor now handles up to at least 650,000,000. [[User:Ladydesire|Ladydesire]] 20:18, 16 January 2010 (UTC)

:Heh. I just spent a bit of time asking around the office about this bug too, the line's been in the tutorial since November. And then I posted here on the talk page without reading it completely first, is my face red. I'm going to provisionally remove the line from the "creating a module" section and store it here:

::Make sure your string sets go from in between 8,000,000 - 8,300,000, if it goes above that range the strings will not work. BioWare has already posted about this SQL problem.

:I'm pretty sure this has been fixed now, unless this is a separate bug that we weren't aware of. [[User:BryanDerksen|BryanDerksen]] 23:28, 2 February 2010 (UTC)

:: I've been using a class built with string tables as I indicated in my comment, so I'd say it's safe to remove it. [[User:Ladydesire|Ladydesire]] 22:22, 3 February 2010 (UTC)

Talk:Add A New Class Tutorial

2010-12-11T03:45:49Z

Apolyon6k: /* Errors */

== Initial edit ==
I have started to edit this page at the author's request to try and fix up some of the formatting. It was prety much a cut and paste from the forum. I think it has a way to go yet. I would recommend replacing all the capitalised text with appropriate markup such as '''bold'''. Also the structure could perhaps be improved and some of the content organised better in sentences rather than point form. Please help out if you have the time and incliniation. [[User:Stuntpope|Stuntpope]]

=== edit ===
Embedded all images and added dascript tages

--[[User:Rigortauri|Rigortauri]] 13:12, 2 December 2009 (UTC)

did some table formating

--[[User:Apolyon6k|Apolyon6k]] 09:14, 2 January 2010 (UTC)

== Errors ==

The following section is incorrect:

Next goto "// Undo Class and Race selection" and add the 4th CharGen_ClearAbilityList

<dascript>
// Note: This wipes the ability list clear
CharGen_ClearAbilityList(oChar,1);
CharGen_ClearAbilityList(oChar,2);
CharGen_ClearAbilityList(oChar,3);
CharGen_ClearAbilityList(oChar,4);
</dascript>

Next goto "// enabling proper tactics presets" and add the ValidForClass4 parts

<dascript>
nForClass1 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass1", nCurrentRow);
nForClass2 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass2", nCurrentRow);
nForClass3 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass3", nCurrentRow);
nForClass4 = GetM2DAInt(TABLE_TACTICS_USER_PRESETS, "ValidForClass4", nCurrentRow);
if(nCoreClass == nForClass1 || nCoreClass == nForClass2 || nCoreClass == nForClass3 || nCoreClass == nForClass4)
AddTacticPresetID(oCreature, nCurrentRow);
</dascript>

The author has misunderstood the purpose of these methods. There is no need to modify the first of these. The int parameter in CharGen_ClearAbilityList is actually the ability type - not a class id. In the second part there is no point modifying this unless you also modify user tactics 2da table. The three columns allow up to three classes to be listed and since the third column is not used already there is really no need to add a fourth column anyway.

I considered removing this but it really needs to be replaced with the correct approach. I suspect that there are other aspects of AI that need to be dealt with too. [[User:Stuntpope|Stuntpope]] 13:13, 7 December 2009 (UTC)

: I went ahead and deleted it, as those should really be part of an advanced tutorial, rather than a basic one; I also went ahead and added some new data that I've been testing that eliminates the need to provide files in packages\core\override. [[User:Ladydesire|Ladydesire]] 21:48, 29 January 2010 (UTC)
===Cleaning up errors?===
I'm not sure but there seems to be an error in the section about cleaning up. If you delete all files you also delete your edited core files (2ds_constants_h and chargen_h). Without those files the new class wouldn't work. It should be mentioned after the export section that those files are needed and that they should be moved to module/core/override.

== String IDs above 8.3 million don't work? ==

There is a discrepancy between the current tutorial and the actual functionality of the toolset with regards to the string table entries; it is no longer necessary to manually set a range for the string tables, as ExcelProcessor now handles up to at least 650,000,000. [[User:Ladydesire|Ladydesire]] 20:18, 16 January 2010 (UTC)

:Heh. I just spent a bit of time asking around the office about this bug too, the line's been in the tutorial since November. And then I posted here on the talk page without reading it completely first, is my face red. I'm going to provisionally remove the line from the "creating a module" section and store it here:

::Make sure your string sets go from in between 8,000,000 - 8,300,000, if it goes above that range the strings will not work. BioWare has already posted about this SQL problem.

:I'm pretty sure this has been fixed now, unless this is a separate bug that we weren't aware of. [[User:BryanDerksen|BryanDerksen]] 23:28, 2 February 2010 (UTC)

:: I've been using a class built with string tables as I indicated in my comment, so I'd say it's safe to remove it. [[User:Ladydesire|Ladydesire]] 22:22, 3 February 2010 (UTC)

Add A New Class Tutorial

2010-02-01T22:30:39Z

Apolyon6k: /* Open up background.xls */

== Editing the 2das ==
You will need to edit the following 2DA's.
*[[2da_base.xls]]
*[[abi_base.xls]]
*[[ALclassname_default.xls]] (ex ALshaman_default.xls) Copy from ALWizard_default.xls
*[[background.xls]]
*[[cla_base.xls]]
*[[guitypes.xls]]
=== Open up 2da_base.xls ===
Add the following to the end of M2DA_base TAB
{| rules="all" cellpadding="2" style="border: 2pt solid black"
|-
|ID above 100000 ||ALShaman_default ||ALShaman_default
|-
|}
Now SAVE your file
=== Open up guitypes.xls ===
At bottom of list paste this:

{| rules="all" cellpadding="2" style="border: 2pt solid black"
|-
!ID|| Label|| StringId|| Ability|| ProgressBar|| CombatTraining|| SpecialGraphic|| TintColor|| Orphanage|| Flags|| BlendTree
|-
|500|| Class: Shaman|| 8000000|| 5000|| 0|| 0|| 1|| 0x9B0F00|| 0|| 0|| ****
|-
|}
Now SAVE your file
=== Open up CLA_base.xls ===
Paste this AFTER line 3: (Move all down 1)

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:80%"
|-
|4 ||Shaman ||8000000 ||8000001 ||**** ||8000002 ||8000003 ||classico_spirithealer ||CLASS_Shaman ||2 ||95 ||1 ||100 ||5 ||2 ||2 ||2 ||2 ||2 ||0 ||0 ||0 ||55 ||50 ||1 ||5 ||1 ||3 ||0.3 ||4035 ||**** ||1 ||Shaman ||****
|-
|}

Now SAVE your file
{{TutorialRef|2DA|2DA base.xls|Guitypes.xls|CLA base.xls}}
=== Open up background.xls ===
On backgrounds tab: You need to insert a section between mage and skill 1, see screenshot

[[Image:Background.jpg]]

On background_defaults there are several section you need to note here regarding the screenshot:

[[Image:Class tut bgdef.jpg]]

How the ID's work, 1 = dwarf, 4 = shaman, 5 = noble, the rest of the pattern is easy.

On lines 12,15,17,19 you need to add these in. What I recommend is just copying these lines

:10 ==> 12
:13 ==> 15
:16 ==> 17
:18 ==> 19

The template string is the default_shaman.utc you will need to create in the toolset later on for these to have a base model
The Ability is the starting ability tied to this class, in my case it just references a different one then what you will have

On chargen_preload there are several section you need to note here regarding the screenshot:

[[Image:Class tut chardef.jpg]]

These ID's must match what is on the background_defaults otherwise the game WILL crash.

Now SAVE your file
{{TutorialRef|2DA|Background.xls}}

=== Open up abi_base.xls ===
in the ABI_Base tab add the following to the bottom of the list

There are several columns that very are important

abilitytype - define what type of ability. melee, spell, skill etc..---> links with abilitytype.xls

prereqability - defines what is needed to have this ability. To add a new class these need to be changed on existing classes.

guitypes - referenced what class this links too ---> links with guitypes.xls

AFTER LINE 119 ==> 4034 HIDDEN_DOG insert a new row and put in the following

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:100%"
|-
|5000||HIDDEN_SHAMAN||0||0||380405||330716||hidden||2||0||0||0||0||0||0||0||1||0||0||12||0||0||0||0||3||1.5||0||0||0||0||0||0||0||0||0||0||0||0||0||0||1||7||0||2||33||0||0||0||0
|-
|}

Add the bottom paste these

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:100%"
|-
|300000||HEROIC_OFFENSE2||380003 ||379523 ||367458 ||379231 ||spl_ico_heroic_offense ||2 ||1 ||0 ||0 ||0 ||20 ||0 ||5000 ||0 ||0 ||0 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||5 ||90215 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90109 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300001 ||HEROIC_AURA2 ||380000 ||379520 ||367458 ||379214 ||spl_ico_heroic_aura ||2 ||1 ||0 ||0 ||0 ||30 ||0 ||300000 ||0 ||4 ||15 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||5 ||90213 ||244 ||247 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||90110 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300002 ||HEROIC_DEFENSE2 ||380001 ||379521 ||367458 ||379256 ||spl_ico_heroic_defense ||2 ||1 ||0 ||0 ||0 ||40 ||0 ||300001 ||0 ||4 ||20 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||10 ||90214 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90111 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300003 ||HASTE2 ||380005 ||379525 ||398957 ||379229 ||spl_ico_agility ||2 ||0 ||0 ||0 ||0 ||0 ||60 ||300002 ||0 ||4 ||30 ||500 ||1 ||1 ||18 ||1 ||2 ||spell_modal.ncs ||30 ||90216 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90112 ||192 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||10
|-
|}

-------------------------------------------------

NOW HERE IS THE TRICKY PART, MAKE SURE YOU DO THIS RIGHT OR KISS YOUR MODULE GOODBYE

HIGHLIGHT LINE 3 ALL THE WAY DOWN TO 558 (BOTTOM OF THE WORKSHEET)

NOW GOTO DATA --> SORT BY COLUMN S (guitypes) Now they should all be sorted by guitype

Now we need to seperate the mage spells from our new shaman spells.

For guitype spells 1-4, you need to look at the prereqability section for these spells, for those that have 0, replace with 4023
This will make these appear only on the mage from now on. (Which means we need to make seperate skills for our new class)
Ok this will now prevent duplicate of skills

HIGHLIGHT LINE 3 ALL THE WAY DOWN TO 558 (BOTTOM OF THE WORKSHEET)

NOW GOTO DATA --> SORT BY COLUMN A (ID) Now we are back to normal

-------------------------------------------------
Now goto passive_abilities

Paste the following at the bottom of the list
{| rules="all" cellpadding="2" style="border: 2pt solid black;"
|-
|9000||HIDDEN_SHAMAN||1||2||4||2||6||1||str +2,mag +2,con +1
|-
|}

Now SAVE your file :)
{{TutorialRef|2DA|ABI base.xls}}
=== Open up ALShaman_default.xls ===
Should look like this

[[Image:Class tut alshaman.jpg]]
{{TutorialRef|2DA|ALWizard_Default.xls}}
== Converting the files from 2DA to GDA ==
Create a directory called '''2DA''' on C:, inside that dir create one called override.

In your C:\2da put the following files:

* [[2da_base.xls]]
* [[abi_base.xls]]
* [[background.xls]]
* [[cla_base.xls]]
* [[guitypes.xls]]
* [[ALShaman_default.xls]]

Also: ExcelProcessor.exe from the tool converter in your toolset section.

Next you need to make a batch file to run to convert these.
Simply open notepad, copy and paste below and save as convert.bat

:C:\2DA\ExcelProcessor.exe 2DA_base.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe background.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe CLA_base.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe ALShaman_Default.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe guitypes.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe ABI_base.xls -outdir=C:\2DA\override\

NOTE: YOU MAY NEED TO "RUN AS ADMINISTRATOR" CONVERT.BAT IN VISTA / W7

VOILA YOU NOW HAVE YOUR GDA FILES FOR THE MODULE
{{TutorialRef|Compiling 2DAs}}
== Creating a module ==
Now we begin editing inside the toolset

Create a new module, similiar to the picture below

'''MAKE SURE YOUR STRING SETS GO FROM IN BETWEEN 8,000,000 - 8,300,000 IF IT GOES ABOVE THAT RANGE THE STRINGS WILL NOT WORK.BIOWARE HAS ALREADY POSTED ABOUT THIS SQL PROBLEM'''

[[Image:Class tut module1.jpg]]

After making it go back to the module screen and select heirarchy and make sure single player is checked

[[Image:Class_tut_hier.jpg]]

Now that your module is created we need to add the appropriate GDA to the override section.

look in name/mydocuments/bioware/dragonage/addins/modulename

Put these GDA files in: name/mydocuments/bioware/dragonage/addins/modulename/core/override directory
{{TutorialRef|Module|Creating a module}}
== Editing the scripts==
You now need to edit some scripts.
=== Edit the 2da_constants_h file ===
find the 2da_constants_h file under Core scripts

right click on 2DA_CONSTANTS_H, select CHECK OUT

Go down to the following sections and edit it like below:

<dascript>
const int ABILITY_TALENT_HIDDEN_DUELIST = 4030;
const int ABILITY_TALENT_HIDDEN_RANGER = 4029;
const int ABILITY_TALENT_HIDDEN_REAVER = 4019;
const int ABILITY_TALENT_HIDDEN_ROGUE = 4020;
const int ABILITY_TALENT_HIDDEN_SHALE = 4033;
const int ABILITY_TALENT_HIDDEN_TEMPLAR = 4021;
const int ABILITY_TALENT_HIDDEN_WARRIOR = 4022;
const int ABILITY_TALENT_HIDDEN_SHAMAN = 5000;
const int ABILITY_TALENT_HURLOCK_PROPERTIES = 90080;
const int ABILITY_TALENT_INDOMITABLE = 28;
</dascript>

and

<dascript>
//Class Constants
const int CLASS_WARRIOR = 1;
const int CLASS_WIZARD = 2;
const int CLASS_ROGUE = 3;
const int CLASS_SHAMAN = 4;
const int CLASS_SHAPESHIFTER = 5;
const int CLASS_SPIRITHEALER = 6;
const int CLASS_CHAMPION = 7;
const int CLASS_TEMPLAR = 8;
const int CLASS_BERSERKER = 9;
const int CLASS_REAVER = 10;
const int CLASS_ARCANE_WARRIOR = 11;
const int CLASS_ASSASSIN = 12;
const int CLASS_BLOOD_MAGE = 13;
const int CLASS_BARD = 14;
const int CLASS_RANGER = 15;
const int CLASS_DUELIST = 16;
const int CLASS_SHALE = 17;
const int CLASS_DOG = 18;
const int CLASS_MONSTER_ANIMAL = 19;
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
=== Edit the sys_chargen_h file ===
Find the sys_chargen_h file under _Systems ==> _Includes

right click on sys_chargen_h, select CHECK OUT

Go down to the starting skills section and edit it like below:

<dascript>
// -------------------------------------------------------------------------
// Starting Skills
// -------------------------------------------------------------------------
if (nClass == CLASS_WARRIOR)
{
_AddAbility(oChar, 100100);
}
else if (nClass == CLASS_ROGUE)
{
_AddAbility(oChar, ABILITY_SKILL_POISON_1);
}
else if (nClass == CLASS_WIZARD)
{
_AddAbility(oChar, ABILITY_SKILL_HERBALISM_1);
}
else if (nClass == CLASS_SHAMAN)
{
_AddAbility(oChar, ABILITY_SKILL_HERBALISM_1);
}
}
</dascript>

Next goto starting ability

<dascript>
// ---------------------------------------------------------------------
// Load the starting ability for the background
// ---------------------------------------------------------------------
int nAbility = GetM2DAInt(TABLE_STARTING_EQUIPMENT,"Ability", nIdx);
_AddAbility(oCreature, nAbility);
}
else
{
string sTemplate = "default_player.utc";
switch (nClass)
{
case CLASS_WARRIOR: sTemplate = "default_warrior.utc";
break;
case CLASS_ROGUE: sTemplate = "default_rogue.utc";
break;
case CLASS_WIZARD: sTemplate = "default_wizard.utc";
break;
case CLASS_SHAMAN: sTemplate = "default_shaman.utc";
break;
}
LoadItemsFromTemplate(oCreature, sTemplate, TRUE);
}
}
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
=== Edit the sys_chargen file ===
Find the sys_chargen ==> under _Systems

right click on sys_chargen, select Duplicate; name the file something like wd_sys_chargen.

Change this line:

<dascript>
const int MAX_CLASS_INDEX = 4; // Last index of available base classes in cla_base.
</dascript>
This value does not have to be limited to the minimum number of base classes in the file; it simply has to be higher than the default value.

Go down to the special handling section and edit it like below:

<dascript>
// special handling for aluvian
if (nQuickStart == 0 )
{
Log_Trace(LOG_CHANNEL_CHARACTER,"sys_chargen","Setting default values for player character");
int nRandClass = abs((GetLowResTimer()%3)+1);
if(nRandClass == CLASS_ROGUE || nRandClass == CLASS_WARRIOR || nRandClass == CLASS_SHAMAN)
{
_RunChargen(RACE_HUMAN, nRandClass, oChar, BACKGROUND_NOBLE );
WR_SetPlotFlag(PLT_GEN00PT_BACKGROUNDS, GEN_BACK_HUMAN_NOBLE, TRUE);
}
else // mage
{
_RunChargen(RACE_HUMAN, nRandClass, oChar, BACKGROUND_MAGI );
WR_SetPlotFlag(PLT_GEN00PT_BACKGROUNDS, GEN_BACK_CIRCLE, TRUE);
}
Chargen_SetNumTactics(oChar);
SetCanLevelUp(oChar,Chargen_HasPointsToSpend(oChar));

SendEventModuleChargenDone("", "");
}
</dascript>

next go down to the tactics sections and add the following:
<dascript>
// associate some tactics preset table
int nPresetTable;
if(GetCreatureCoreClass(oChar) == CLASS_WARRIOR)
nPresetTable = 1; // tank
else if(GetCreatureCoreClass(oChar) == CLASS_ROGUE)
nPresetTable = 2; // damage dealer
else if(GetCreatureCoreClass(oChar) == CLASS_SHAMAN)
nPresetTable = 1; // damage dealer
else // mage
nPresetTable = 5; // nuker
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
=== Create the module script ===
Create a new script and give it a descriptive name like "loadscript". This script will intercept the Chargen events and redirect them to the custom version of the sys_chargen script you just created. It can also be used to intercept other events if you want to alter other things or add items to a newly created character's inventory.

<dascript>
#include "utility_h"
#include "wrappers_h"
#include "events_h"
void main()
{
event ev = GetCurrentEvent();
int nEvent = GetEventType(ev);
Log_Events("", ev);
switch (nEvent)
{
default:
{
// -----------------------------------------------------------------
// Handle character generation events sent by the engine.
// -----------------------------------------------------------------
if ((nEvent >= EVENT_TYPE_CHARGEN_START && nEvent <= EVENT_TYPE_CHARGEN_END) || nEvent == EVENT_TYPE_PLAYERLEVELUP )
{
HandleEvent(ev, R"ld_sys_chargen.ncs");
}
else
{
Log_Trace(LOG_CHANNEL_EVENTS, GetCurrentScriptName(), Log_GetEventNameById(nEvent) + " (" + ToString(nEvent) + ") *** Unhandled event ***");
}
break;
}
}
}
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
{{TutorialRef|Script}}
== Creating the UTC template file==
Back in the toolset we need to do the following:

Click on the "creature tab" (red head icon)

Right click on default_mage ==> duplicate
Do like the following:

[[Image:Class tut dfs1.jpg]]

Now we need to edit the values and give them some armor and weapons, like so:

Class: Shaman (from dropdown)
Name: Default Male Shaman

[[Image:Class tut dfs2.jpg]]

Now at the top and click SAVE ==> CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
{{TutorialRef|Designer Resources#Creating new resources|Creature|Exporting a module}}
== Creating some strings ==
Start the String editor and right click and insert.

You will be setting up like this

:Table = module talk base
:Owner = module name
:TYPE = GUI

:8000000 - Shaman
:8000001 - Shamans
:8000002 - Shamans commune with spirits to get thier other worldly powers.
:8000004 - Shaman
:8000005 - Shaman Male Name
:8000006 - Shaman Female Name

When all is said close string editor
{{TutorialRef|String editor}}
== Putting it all together ==
Up on top ON THE EXPORT TAB

"EXPORT WITHOUT DEPENDENT RESOURCES"

"GENERATE MODULE XML"

"GENERATE MANIFEST XML"

"EXPORT TALK TABLE"
{{TutorialRef|Exporting a module}}
== Cleaning up ==
DON'T SKIP THIS PART

Delete all files in the name/mydocuments/bioware/dragonage/packages/core/override/toolset; these are not needed.
== Trying it out ==
Start up your game (It may take a min) and start a new game.

*WARNING* IF ANYTHING HAS GONE WRONG HERE YOUR GAME WILL BE SEVERELY DAMAGED

Select MALE ==> HUMAN ==> SHAMAN ==> MAGI

YOU SHOULD SEE YOUR NEW CHARACTER

IF SOMETHING HAPPENED QUIT AND DOUBLE CHECK YOUR STEPS

Make sure you did not miss ANY ";" or "{ }" as a single one of these missed can destroy the game.
== Troubleshooting ==
MY SPELLS ARE NOT SHOWING UP IN THE CREATION SCREEN, HELP!!

* You may not have sort your ability file back to ID. It has to be sorted by ID in order to show up.
* You may not have assigned the new abilities to your new class "5000" in the prereqability column

MY MODEL IS NOT SHOWING UP WHEN I GOTO MALE ==> HUMAN ==> SHAMAN ==> MAGI

* It is very likely you did not EXPORT your default_shaman.utc model
* Double check the background file to make sure you are using default_shaman.utc for the template
* Try rebooting your computer.
[[Category:Character generation]]
[[Category:Tutorials]]

Add A New Class Tutorial

2010-02-01T22:29:33Z

Apolyon6k:

== Editing the 2das ==
You will need to edit the following 2DA's.
*[[2da_base.xls]]
*[[abi_base.xls]]
*[[ALclassname_default.xls]] (ex ALshaman_default.xls) Copy from ALWizard_default.xls
*[[background.xls]]
*[[cla_base.xls]]
*[[guitypes.xls]]
=== Open up 2da_base.xls ===
Add the following to the end of M2DA_base TAB
{| rules="all" cellpadding="2" style="border: 2pt solid black"
|-
|ID above 100000 ||ALShaman_default ||ALShaman_default
|-
|}
Now SAVE your file
=== Open up guitypes.xls ===
At bottom of list paste this:

{| rules="all" cellpadding="2" style="border: 2pt solid black"
|-
!ID|| Label|| StringId|| Ability|| ProgressBar|| CombatTraining|| SpecialGraphic|| TintColor|| Orphanage|| Flags|| BlendTree
|-
|500|| Class: Shaman|| 8000000|| 5000|| 0|| 0|| 1|| 0x9B0F00|| 0|| 0|| ****
|-
|}
Now SAVE your file
=== Open up CLA_base.xls ===
Paste this AFTER line 3: (Move all down 1)

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:80%"
|-
|4 ||Shaman ||8000000 ||8000001 ||**** ||8000002 ||8000003 ||classico_spirithealer ||CLASS_Shaman ||2 ||95 ||1 ||100 ||5 ||2 ||2 ||2 ||2 ||2 ||0 ||0 ||0 ||55 ||50 ||1 ||5 ||1 ||3 ||0.3 ||4035 ||**** ||1 ||Shaman ||****
|-
|}

Now SAVE your file
{{TutorialRef|2DA|2DA base.xls|Guitypes.xls|CLA base.xls}}
=== Open up background.xls ===
On backgrounds tab: You need to insert a section between mage and skill 1, see screenshot
[[Image:Background.jpg]]
On background_defaults there are several section you need to note here regarding the screenshot:
[[Image:Class tut bgdef.jpg]]
How the ID's work, 1 = dwarf, 4 = shaman, 5 = noble, the rest of the pattern is easy.

On lines 12,15,17,19 you need to add these in. What I recommend is just copying these lines

:10 ==> 12
:13 ==> 15
:16 ==> 17
:18 ==> 19

The template string is the default_shaman.utc you will need to create in the toolset later on for these to have a base model
The Ability is the starting ability tied to this class, in my case it just references a different one then what you will have

On chargen_preload there are several section you need to note here regarding the screenshot:

[[Image:Class tut chardef.jpg]]

These ID's must match what is on the background_defaults otherwise the game WILL crash.

Now SAVE your file
{{TutorialRef|2DA|Background.xls}}
=== Open up abi_base.xls ===
in the ABI_Base tab add the following to the bottom of the list

There are several columns that very are important

abilitytype - define what type of ability. melee, spell, skill etc..---> links with abilitytype.xls

prereqability - defines what is needed to have this ability. To add a new class these need to be changed on existing classes.

guitypes - referenced what class this links too ---> links with guitypes.xls

AFTER LINE 119 ==> 4034 HIDDEN_DOG insert a new row and put in the following

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:100%"
|-
|5000||HIDDEN_SHAMAN||0||0||380405||330716||hidden||2||0||0||0||0||0||0||0||1||0||0||12||0||0||0||0||3||1.5||0||0||0||0||0||0||0||0||0||0||0||0||0||0||1||7||0||2||33||0||0||0||0
|-
|}

Add the bottom paste these

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:100%"
|-
|300000||HEROIC_OFFENSE2||380003 ||379523 ||367458 ||379231 ||spl_ico_heroic_offense ||2 ||1 ||0 ||0 ||0 ||20 ||0 ||5000 ||0 ||0 ||0 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||5 ||90215 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90109 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300001 ||HEROIC_AURA2 ||380000 ||379520 ||367458 ||379214 ||spl_ico_heroic_aura ||2 ||1 ||0 ||0 ||0 ||30 ||0 ||300000 ||0 ||4 ||15 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||5 ||90213 ||244 ||247 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||90110 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300002 ||HEROIC_DEFENSE2 ||380001 ||379521 ||367458 ||379256 ||spl_ico_heroic_defense ||2 ||1 ||0 ||0 ||0 ||40 ||0 ||300001 ||0 ||4 ||20 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||10 ||90214 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90111 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300003 ||HASTE2 ||380005 ||379525 ||398957 ||379229 ||spl_ico_agility ||2 ||0 ||0 ||0 ||0 ||0 ||60 ||300002 ||0 ||4 ||30 ||500 ||1 ||1 ||18 ||1 ||2 ||spell_modal.ncs ||30 ||90216 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90112 ||192 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||10
|-
|}

-------------------------------------------------

NOW HERE IS THE TRICKY PART, MAKE SURE YOU DO THIS RIGHT OR KISS YOUR MODULE GOODBYE

HIGHLIGHT LINE 3 ALL THE WAY DOWN TO 558 (BOTTOM OF THE WORKSHEET)

NOW GOTO DATA --> SORT BY COLUMN S (guitypes) Now they should all be sorted by guitype

Now we need to seperate the mage spells from our new shaman spells.

For guitype spells 1-4, you need to look at the prereqability section for these spells, for those that have 0, replace with 4023
This will make these appear only on the mage from now on. (Which means we need to make seperate skills for our new class)
Ok this will now prevent duplicate of skills

HIGHLIGHT LINE 3 ALL THE WAY DOWN TO 558 (BOTTOM OF THE WORKSHEET)

NOW GOTO DATA --> SORT BY COLUMN A (ID) Now we are back to normal

-------------------------------------------------
Now goto passive_abilities

Paste the following at the bottom of the list
{| rules="all" cellpadding="2" style="border: 2pt solid black;"
|-
|9000||HIDDEN_SHAMAN||1||2||4||2||6||1||str +2,mag +2,con +1
|-
|}

Now SAVE your file :)
{{TutorialRef|2DA|ABI base.xls}}
=== Open up ALShaman_default.xls ===
Should look like this

[[Image:Class tut alshaman.jpg]]
{{TutorialRef|2DA|ALWizard_Default.xls}}
== Converting the files from 2DA to GDA ==
Create a directory called '''2DA''' on C:, inside that dir create one called override.

In your C:\2da put the following files:

* [[2da_base.xls]]
* [[abi_base.xls]]
* [[background.xls]]
* [[cla_base.xls]]
* [[guitypes.xls]]
* [[ALShaman_default.xls]]

Also: ExcelProcessor.exe from the tool converter in your toolset section.

Next you need to make a batch file to run to convert these.
Simply open notepad, copy and paste below and save as convert.bat

:C:\2DA\ExcelProcessor.exe 2DA_base.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe background.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe CLA_base.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe ALShaman_Default.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe guitypes.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe ABI_base.xls -outdir=C:\2DA\override\

NOTE: YOU MAY NEED TO "RUN AS ADMINISTRATOR" CONVERT.BAT IN VISTA / W7

VOILA YOU NOW HAVE YOUR GDA FILES FOR THE MODULE
{{TutorialRef|Compiling 2DAs}}
== Creating a module ==
Now we begin editing inside the toolset

Create a new module, similiar to the picture below

'''MAKE SURE YOUR STRING SETS GO FROM IN BETWEEN 8,000,000 - 8,300,000 IF IT GOES ABOVE THAT RANGE THE STRINGS WILL NOT WORK.BIOWARE HAS ALREADY POSTED ABOUT THIS SQL PROBLEM'''

[[Image:Class tut module1.jpg]]

After making it go back to the module screen and select heirarchy and make sure single player is checked

[[Image:Class_tut_hier.jpg]]

Now that your module is created we need to add the appropriate GDA to the override section.

look in name/mydocuments/bioware/dragonage/addins/modulename

Put these GDA files in: name/mydocuments/bioware/dragonage/addins/modulename/core/override directory
{{TutorialRef|Module|Creating a module}}
== Editing the scripts==
You now need to edit some scripts.
=== Edit the 2da_constants_h file ===
find the 2da_constants_h file under Core scripts

right click on 2DA_CONSTANTS_H, select CHECK OUT

Go down to the following sections and edit it like below:

<dascript>
const int ABILITY_TALENT_HIDDEN_DUELIST = 4030;
const int ABILITY_TALENT_HIDDEN_RANGER = 4029;
const int ABILITY_TALENT_HIDDEN_REAVER = 4019;
const int ABILITY_TALENT_HIDDEN_ROGUE = 4020;
const int ABILITY_TALENT_HIDDEN_SHALE = 4033;
const int ABILITY_TALENT_HIDDEN_TEMPLAR = 4021;
const int ABILITY_TALENT_HIDDEN_WARRIOR = 4022;
const int ABILITY_TALENT_HIDDEN_SHAMAN = 5000;
const int ABILITY_TALENT_HURLOCK_PROPERTIES = 90080;
const int ABILITY_TALENT_INDOMITABLE = 28;
</dascript>

and

<dascript>
//Class Constants
const int CLASS_WARRIOR = 1;
const int CLASS_WIZARD = 2;
const int CLASS_ROGUE = 3;
const int CLASS_SHAMAN = 4;
const int CLASS_SHAPESHIFTER = 5;
const int CLASS_SPIRITHEALER = 6;
const int CLASS_CHAMPION = 7;
const int CLASS_TEMPLAR = 8;
const int CLASS_BERSERKER = 9;
const int CLASS_REAVER = 10;
const int CLASS_ARCANE_WARRIOR = 11;
const int CLASS_ASSASSIN = 12;
const int CLASS_BLOOD_MAGE = 13;
const int CLASS_BARD = 14;
const int CLASS_RANGER = 15;
const int CLASS_DUELIST = 16;
const int CLASS_SHALE = 17;
const int CLASS_DOG = 18;
const int CLASS_MONSTER_ANIMAL = 19;
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
=== Edit the sys_chargen_h file ===
Find the sys_chargen_h file under _Systems ==> _Includes

right click on sys_chargen_h, select CHECK OUT

Go down to the starting skills section and edit it like below:

<dascript>
// -------------------------------------------------------------------------
// Starting Skills
// -------------------------------------------------------------------------
if (nClass == CLASS_WARRIOR)
{
_AddAbility(oChar, 100100);
}
else if (nClass == CLASS_ROGUE)
{
_AddAbility(oChar, ABILITY_SKILL_POISON_1);
}
else if (nClass == CLASS_WIZARD)
{
_AddAbility(oChar, ABILITY_SKILL_HERBALISM_1);
}
else if (nClass == CLASS_SHAMAN)
{
_AddAbility(oChar, ABILITY_SKILL_HERBALISM_1);
}
}
</dascript>

Next goto starting ability

<dascript>
// ---------------------------------------------------------------------
// Load the starting ability for the background
// ---------------------------------------------------------------------
int nAbility = GetM2DAInt(TABLE_STARTING_EQUIPMENT,"Ability", nIdx);
_AddAbility(oCreature, nAbility);
}
else
{
string sTemplate = "default_player.utc";
switch (nClass)
{
case CLASS_WARRIOR: sTemplate = "default_warrior.utc";
break;
case CLASS_ROGUE: sTemplate = "default_rogue.utc";
break;
case CLASS_WIZARD: sTemplate = "default_wizard.utc";
break;
case CLASS_SHAMAN: sTemplate = "default_shaman.utc";
break;
}
LoadItemsFromTemplate(oCreature, sTemplate, TRUE);
}
}
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
=== Edit the sys_chargen file ===
Find the sys_chargen ==> under _Systems

right click on sys_chargen, select Duplicate; name the file something like wd_sys_chargen.

Change this line:

<dascript>
const int MAX_CLASS_INDEX = 4; // Last index of available base classes in cla_base.
</dascript>
This value does not have to be limited to the minimum number of base classes in the file; it simply has to be higher than the default value.

Go down to the special handling section and edit it like below:

<dascript>
// special handling for aluvian
if (nQuickStart == 0 )
{
Log_Trace(LOG_CHANNEL_CHARACTER,"sys_chargen","Setting default values for player character");
int nRandClass = abs((GetLowResTimer()%3)+1);
if(nRandClass == CLASS_ROGUE || nRandClass == CLASS_WARRIOR || nRandClass == CLASS_SHAMAN)
{
_RunChargen(RACE_HUMAN, nRandClass, oChar, BACKGROUND_NOBLE );
WR_SetPlotFlag(PLT_GEN00PT_BACKGROUNDS, GEN_BACK_HUMAN_NOBLE, TRUE);
}
else // mage
{
_RunChargen(RACE_HUMAN, nRandClass, oChar, BACKGROUND_MAGI );
WR_SetPlotFlag(PLT_GEN00PT_BACKGROUNDS, GEN_BACK_CIRCLE, TRUE);
}
Chargen_SetNumTactics(oChar);
SetCanLevelUp(oChar,Chargen_HasPointsToSpend(oChar));

SendEventModuleChargenDone("", "");
}
</dascript>

next go down to the tactics sections and add the following:
<dascript>
// associate some tactics preset table
int nPresetTable;
if(GetCreatureCoreClass(oChar) == CLASS_WARRIOR)
nPresetTable = 1; // tank
else if(GetCreatureCoreClass(oChar) == CLASS_ROGUE)
nPresetTable = 2; // damage dealer
else if(GetCreatureCoreClass(oChar) == CLASS_SHAMAN)
nPresetTable = 1; // damage dealer
else // mage
nPresetTable = 5; // nuker
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
=== Create the module script ===
Create a new script and give it a descriptive name like "loadscript". This script will intercept the Chargen events and redirect them to the custom version of the sys_chargen script you just created. It can also be used to intercept other events if you want to alter other things or add items to a newly created character's inventory.

<dascript>
#include "utility_h"
#include "wrappers_h"
#include "events_h"
void main()
{
event ev = GetCurrentEvent();
int nEvent = GetEventType(ev);
Log_Events("", ev);
switch (nEvent)
{
default:
{
// -----------------------------------------------------------------
// Handle character generation events sent by the engine.
// -----------------------------------------------------------------
if ((nEvent >= EVENT_TYPE_CHARGEN_START && nEvent <= EVENT_TYPE_CHARGEN_END) || nEvent == EVENT_TYPE_PLAYERLEVELUP )
{
HandleEvent(ev, R"ld_sys_chargen.ncs");
}
else
{
Log_Trace(LOG_CHANNEL_EVENTS, GetCurrentScriptName(), Log_GetEventNameById(nEvent) + " (" + ToString(nEvent) + ") *** Unhandled event ***");
}
break;
}
}
}
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
{{TutorialRef|Script}}
== Creating the UTC template file==
Back in the toolset we need to do the following:

Click on the "creature tab" (red head icon)

Right click on default_mage ==> duplicate
Do like the following:

[[Image:Class tut dfs1.jpg]]

Now we need to edit the values and give them some armor and weapons, like so:

Class: Shaman (from dropdown)
Name: Default Male Shaman

[[Image:Class tut dfs2.jpg]]

Now at the top and click SAVE ==> CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"
{{TutorialRef|Designer Resources#Creating new resources|Creature|Exporting a module}}
== Creating some strings ==
Start the String editor and right click and insert.

You will be setting up like this

:Table = module talk base
:Owner = module name
:TYPE = GUI

:8000000 - Shaman
:8000001 - Shamans
:8000002 - Shamans commune with spirits to get thier other worldly powers.
:8000004 - Shaman
:8000005 - Shaman Male Name
:8000006 - Shaman Female Name

When all is said close string editor
{{TutorialRef|String editor}}
== Putting it all together ==
Up on top ON THE EXPORT TAB

"EXPORT WITHOUT DEPENDENT RESOURCES"

"GENERATE MODULE XML"

"GENERATE MANIFEST XML"

"EXPORT TALK TABLE"
{{TutorialRef|Exporting a module}}
== Cleaning up ==
DON'T SKIP THIS PART

Delete all files in the name/mydocuments/bioware/dragonage/packages/core/override/toolset; these are not needed.
== Trying it out ==
Start up your game (It may take a min) and start a new game.

*WARNING* IF ANYTHING HAS GONE WRONG HERE YOUR GAME WILL BE SEVERELY DAMAGED

Select MALE ==> HUMAN ==> SHAMAN ==> MAGI

YOU SHOULD SEE YOUR NEW CHARACTER

IF SOMETHING HAPPENED QUIT AND DOUBLE CHECK YOUR STEPS

Make sure you did not miss ANY ";" or "{ }" as a single one of these missed can destroy the game.
== Troubleshooting ==
MY SPELLS ARE NOT SHOWING UP IN THE CREATION SCREEN, HELP!!

* You may not have sort your ability file back to ID. It has to be sorted by ID in order to show up.
* You may not have assigned the new abilities to your new class "5000" in the prereqability column

MY MODEL IS NOT SHOWING UP WHEN I GOTO MALE ==> HUMAN ==> SHAMAN ==> MAGI

* It is very likely you did not EXPORT your default_shaman.utc model
* Double check the background file to make sure you are using default_shaman.utc for the template
* Try rebooting your computer.
[[Category:Character generation]]
[[Category:Tutorials]]

Classes

2010-02-01T22:23:45Z

Apolyon6k:

''Work in progress''
=== Overview ===
Dragon Age: Origins is a strongly class based RPG featuring 3 distinct character classes with exclusive abilities and progressions.
=== Description ===
This page explains the technical implementation and role of character classes in Dragon Age: Origins and is aimed at people wishing to create new content, modifications or adventures using the Dragon Age ruleset.

The classes of the game are defined in '''[[CLA_base.xls]]'''.
The following is an excerpt of the game rules and systems relevant columns in the file and illustrates how data relating to character class is stored.

{| border="1" width="100%" style="font-size:xx-small"
|-
|'''ID'''||'''Label'''||'''BaseHealth'''||'''BaseManaStamina'''||'''DepletableProgression'''||'''StrAdjust'''||'''ConAdjust'''||'''WillAdjust'''||'''MagAdjust'''||'''CunAdjust'''||'''DexAdjust'''||'''BaseAttack'''||'''BaseDefense'''||'''DefensePerLevel'''||'''HealthPerLevel'''||'''LevelsPerAbility'''||'''LevelsPerSkill'''||'''DamagePerLevel'''
|-
|0||INVALID||****||****||****||****||****||****||****||****||****||****||****||****||****||****||****||****|
|-
|1||Warrior||100||100||5||4||3||0||0||0||3||60||45||1||6||1||3||0.4
|-
|2||Wizard||85||115||6||0||0||4||5||1||0||50||40||1||4||1||3||0.1
|-
|3||Rogue||90||90||4||0||0||2||0||4||4||55||50||1||5||1||2||0.2
|-|
|}
For details on the meaning of each column, please refer to '''[[CLA_base.xls]]'''.
=== Character Creation Scripting ===
Dragon Age characters are 'blank' when the game starts, with all their [[Creature Properties]] initialized to default values.

The character generation scripts, through interaction with the Character Creation UIs, use the data in [[CLA_base.xls]] to construct the character based on the player's choices. They are also responsible for any modification to the character's base stats during the Levelup process.

Note that major party members will use the character creation scripts, hostile enemies use a speed optimized and abreviated algorithm to determine their attributes based on rank, AI package and level.
==== Scripts ====
The scripts that handle most of character creation and levelup are:

* sys_chargen - Entry point for all character creation based [[Event]]s that get routed into this file from module_core.nss.
* sys_chargen_h - Library containing most of the underlying logic for modifying [[Creature Properties]] based on the game rules.
* sys_chargen_engine - Include defining a few constants and containing some snippets of relevant engine code for reference.
* sys_autolevelup_h - File defining the logic used by Party Member NPCs to level up when they are hired. After that, they use normal levelup.
* sys_autoscale_h - Contains shared logic used for determining levelup condition and code for creature autoscaling.
* sys_rewards_h - File containing XP reward entry point and levelup checks.

[[Category: Scripts]]
[[Category: Character_generation]]

Add A New Class Tutorial

2010-02-01T22:18:36Z

Apolyon6k: /* Creating a module */

== Editing the 2das ==
You will need to edit the following 2DA's.
*[[2da_base.xls]]
*[[abi_base.xls]]
*[[ALclassname_default.xls]] (ex ALshaman_default.xls) Copy from ALWizard_default.xls
*[[background.xls]]
*[[cla_base.xls]]
*[[guitypes.xls]]

=== Open up 2da_base.xls ===

Add the following to the end of M2DA_base TAB
{| rules="all" cellpadding="2" style="border: 2pt solid black"
|-
|ID above 100000 ||ALShaman_default ||ALShaman_default
|-
|}
Now SAVE your file

=== Open up guitypes.xls ===
At bottom of list paste this:

{| rules="all" cellpadding="2" style="border: 2pt solid black"
|-
!ID|| Label|| StringId|| Ability|| ProgressBar|| CombatTraining|| SpecialGraphic|| TintColor|| Orphanage|| Flags|| BlendTree
|-
|500|| Class: Shaman|| 8000000|| 5000|| 0|| 0|| 1|| 0x9B0F00|| 0|| 0|| ****
|-
|}
Now SAVE your file

=== Open up CLA_base.xls ===
Paste this AFTER line 3: (Move all down 1)

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:80%"
|-
|4 ||Shaman ||8000000 ||8000001 ||**** ||8000002 ||8000003 ||classico_spirithealer ||CLASS_Shaman ||2 ||95 ||1 ||100 ||5 ||2 ||2 ||2 ||2 ||2 ||0 ||0 ||0 ||55 ||50 ||1 ||5 ||1 ||3 ||0.3 ||4035 ||**** ||1 ||Shaman ||****
|-
|}

Now SAVE your file

{{TutorialRef|2DA|2DA base.xls|Guitypes.xls|CLA base.xls}}

=== Open up background.xls ===
On backgrounds tab: You need to insert a section between mage and skill 1, see screenshot

[[Image:Background.jpg]]

On background_defaults there are several section you need to note here regarding the screenshot:

[[Image:Class tut bgdef.jpg]]

How the ID's work, 1 = dwarf, 4 = shaman, 5 = noble, the rest of the pattern is easy.

On lines 12,15,17,19 you need to add these in. What I recommend is just copying these lines

:10 ==> 12
:13 ==> 15
:16 ==> 17
:18 ==> 19

The template string is the default_shaman.utc you will need to create in the toolset later on for these to have a base model
The Ability is the starting ability tied to this class, in my case it just references a different one then what you will have

On chargen_preload there are several section you need to note here regarding the screenshot:

[[Image:Class tut chardef.jpg]]

These ID's must match what is on the background_defaults otherwise the game WILL crash.

Now SAVE your file

{{TutorialRef|2DA|Background.xls}}

=== Open up abi_base.xls ===

in the ABI_Base tab add the following to the bottom of the list

There are several columns that very are important

abilitytype - define what type of ability. melee, spell, skill etc..---> links with abilitytype.xls

prereqability - defines what is needed to have this ability. To add a new class these need to be changed on existing classes.

guitypes - referenced what class this links too ---> links with guitypes.xls

AFTER LINE 119 ==> 4034 HIDDEN_DOG insert a new row and put in the following

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:100%"
|-
|5000||HIDDEN_SHAMAN||0||0||380405||330716||hidden||2||0||0||0||0||0||0||0||1||0||0||12||0||0||0||0||3||1.5||0||0||0||0||0||0||0||0||0||0||0||0||0||0||1||7||0||2||33||0||0||0||0
|-
|}

Add the bottom paste these

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:100%"
|-
|300000||HEROIC_OFFENSE2||380003 ||379523 ||367458 ||379231 ||spl_ico_heroic_offense ||2 ||1 ||0 ||0 ||0 ||20 ||0 ||5000 ||0 ||0 ||0 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||5 ||90215 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90109 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300001 ||HEROIC_AURA2 ||380000 ||379520 ||367458 ||379214 ||spl_ico_heroic_aura ||2 ||1 ||0 ||0 ||0 ||30 ||0 ||300000 ||0 ||4 ||15 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||5 ||90213 ||244 ||247 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||90110 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300002 ||HEROIC_DEFENSE2 ||380001 ||379521 ||367458 ||379256 ||spl_ico_heroic_defense ||2 ||1 ||0 ||0 ||0 ||40 ||0 ||300001 ||0 ||4 ||20 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||10 ||90214 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90111 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300003 ||HASTE2 ||380005 ||379525 ||398957 ||379229 ||spl_ico_agility ||2 ||0 ||0 ||0 ||0 ||0 ||60 ||300002 ||0 ||4 ||30 ||500 ||1 ||1 ||18 ||1 ||2 ||spell_modal.ncs ||30 ||90216 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90112 ||192 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||10
|-
|}

-------------------------------------------------

NOW HERE IS THE TRICKY PART, MAKE SURE YOU DO THIS RIGHT OR KISS YOUR MODULE GOODBYE

HIGHLIGHT LINE 3 ALL THE WAY DOWN TO 558 (BOTTOM OF THE WORKSHEET)

NOW GOTO DATA --> SORT BY COLUMN S (guitypes) Now they should all be sorted by guitype

Now we need to seperate the mage spells from our new shaman spells.

For guitype spells 1-4, you need to look at the prereqability section for these spells, for those that have 0, replace with 4023
This will make these appear only on the mage from now on. (Which means we need to make seperate skills for our new class)
Ok this will now prevent duplicate of skills

HIGHLIGHT LINE 3 ALL THE WAY DOWN TO 558 (BOTTOM OF THE WORKSHEET)

NOW GOTO DATA --> SORT BY COLUMN A (ID) Now we are back to normal

-------------------------------------------------
Now goto passive_abilities

Paste the following at the bottom of the list
{| rules="all" cellpadding="2" style="border: 2pt solid black;"
|-
|9000||HIDDEN_SHAMAN||1||2||4||2||6||1||str +2,mag +2,con +1
|-
|}

Now SAVE your file :)

{{TutorialRef|2DA|ABI base.xls}}

=== Open up ALShaman_default.xls ===

Should look like this

[[Image:Class tut alshaman.jpg]]

{{TutorialRef|2DA|ALWizard_Default.xls}}

== Converting the files from 2DA to GDA ==

Create a directory called '''2DA''' on C:, inside that dir create one called override.

In your C:\2da put the following files:

* [[2da_base.xls]]
* [[abi_base.xls]]
* [[background.xls]]
* [[cla_base.xls]]
* [[guitypes.xls]]
* [[ALShaman_default.xls]]

Also: ExcelProcessor.exe from the tool converter in your toolset section.

Next you need to make a batch file to run to convert these.
Simply open notepad, copy and paste below and save as convert.bat

:C:\2DA\ExcelProcessor.exe 2DA_base.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe background.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe CLA_base.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe ALShaman_Default.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe guitypes.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe ABI_base.xls -outdir=C:\2DA\override\

NOTE: YOU MAY NEED TO "RUN AS ADMINISTRATOR" CONVERT.BAT IN VISTA / W7

VOILA YOU NOW HAVE YOUR GDA FILES FOR THE MODULE

{{TutorialRef|Compiling 2DAs}}

== Creating a module ==
Now we begin editing inside the toolset

Create a new module, similiar to the picture below

'''MAKE SURE YOUR STRING SETS GO FROM IN BETWEEN 8,000,000 - 8,300,000 IF IT GOES ABOVE THAT RANGE THE STRINGS WILL NOT WORK.BIOWARE HAS ALREADY POSTED ABOUT THIS SQL PROBLEM'''

[[Image:Class tut module1.jpg]]

After making it go back to the module screen and select heirarchy and make sure single player is checked

[[Image:Class_tut_hier.jpg]]

Now that your module is created we need to add the appropriate GDA to the override section.

look in name/mydocuments/bioware/dragonage/addins/modulename

Put these GDA files in: name/mydocuments/bioware/dragonage/addins/modulename/core/override directory

{{TutorialRef|Module|Creating a module}}

== Editing the scripts==
You now need to edit some scripts.

=== Edit the 2da_constants_h file ===

find the 2da_constants_h file under Core scripts

right click on 2DA_CONSTANTS_H, select CHECK OUT

Go down to the following sections and edit it like below:

<dascript>
const int ABILITY_TALENT_HIDDEN_DUELIST = 4030;
const int ABILITY_TALENT_HIDDEN_RANGER = 4029;
const int ABILITY_TALENT_HIDDEN_REAVER = 4019;
const int ABILITY_TALENT_HIDDEN_ROGUE = 4020;
const int ABILITY_TALENT_HIDDEN_SHALE = 4033;
const int ABILITY_TALENT_HIDDEN_TEMPLAR = 4021;
const int ABILITY_TALENT_HIDDEN_WARRIOR = 4022;
const int ABILITY_TALENT_HIDDEN_SHAMAN = 5000;
const int ABILITY_TALENT_HURLOCK_PROPERTIES = 90080;
const int ABILITY_TALENT_INDOMITABLE = 28;
</dascript>

and

<dascript>
//Class Constants
const int CLASS_WARRIOR = 1;
const int CLASS_WIZARD = 2;
const int CLASS_ROGUE = 3;
const int CLASS_SHAMAN = 4;
const int CLASS_SHAPESHIFTER = 5;
const int CLASS_SPIRITHEALER = 6;
const int CLASS_CHAMPION = 7;
const int CLASS_TEMPLAR = 8;
const int CLASS_BERSERKER = 9;
const int CLASS_REAVER = 10;
const int CLASS_ARCANE_WARRIOR = 11;
const int CLASS_ASSASSIN = 12;
const int CLASS_BLOOD_MAGE = 13;
const int CLASS_BARD = 14;
const int CLASS_RANGER = 15;
const int CLASS_DUELIST = 16;
const int CLASS_SHALE = 17;
const int CLASS_DOG = 18;
const int CLASS_MONSTER_ANIMAL = 19;
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

=== Edit the sys_chargen_h file ===
Find the sys_chargen_h file under _Systems ==> _Includes

right click on sys_chargen_h, select CHECK OUT

Go down to the starting skills section and edit it like below:

<dascript>
// -------------------------------------------------------------------------
// Starting Skills
// -------------------------------------------------------------------------
if (nClass == CLASS_WARRIOR)
{
_AddAbility(oChar, 100100);
}
else if (nClass == CLASS_ROGUE)
{
_AddAbility(oChar, ABILITY_SKILL_POISON_1);
}
else if (nClass == CLASS_WIZARD)
{
_AddAbility(oChar, ABILITY_SKILL_HERBALISM_1);
}
else if (nClass == CLASS_SHAMAN)
{
_AddAbility(oChar, ABILITY_SKILL_HERBALISM_1);
}
}
</dascript>

Next goto starting ability

<dascript>
// ---------------------------------------------------------------------
// Load the starting ability for the background
// ---------------------------------------------------------------------
int nAbility = GetM2DAInt(TABLE_STARTING_EQUIPMENT,"Ability", nIdx);
_AddAbility(oCreature, nAbility);

}
else
{
string sTemplate = "default_player.utc";
switch (nClass)
{
case CLASS_WARRIOR: sTemplate = "default_warrior.utc";
break;
case CLASS_ROGUE: sTemplate = "default_rogue.utc";
break;
case CLASS_WIZARD: sTemplate = "default_wizard.utc";
break;
case CLASS_SHAMAN: sTemplate = "default_shaman.utc";
break;
}

LoadItemsFromTemplate(oCreature, sTemplate, TRUE);
}
}
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

=== Edit the sys_chargen file ===
Find the sys_chargen ==> under _Systems

right click on sys_chargen, select Duplicate; name the file something like wd_sys_chargen.

Change this line:

<dascript>
const int MAX_CLASS_INDEX = 4; // Last index of available base classes in cla_base.
</dascript>
This value does not have to be limited to the minimum number of base classes in the file; it simply has to be higher than the default value.

Go down to the special handling section and edit it like below:

<dascript>
// special handling for aluvian
if (nQuickStart == 0 )
{
Log_Trace(LOG_CHANNEL_CHARACTER,"sys_chargen","Setting default values for player character");

int nRandClass = abs((GetLowResTimer()%3)+1);

if(nRandClass == CLASS_ROGUE || nRandClass == CLASS_WARRIOR || nRandClass == CLASS_SHAMAN)
{
_RunChargen(RACE_HUMAN, nRandClass, oChar, BACKGROUND_NOBLE );
WR_SetPlotFlag(PLT_GEN00PT_BACKGROUNDS, GEN_BACK_HUMAN_NOBLE, TRUE);
}
else // mage
{
_RunChargen(RACE_HUMAN, nRandClass, oChar, BACKGROUND_MAGI );
WR_SetPlotFlag(PLT_GEN00PT_BACKGROUNDS, GEN_BACK_CIRCLE, TRUE);
}

Chargen_SetNumTactics(oChar);
SetCanLevelUp(oChar,Chargen_HasPointsToSpend(oChar));

SendEventModuleChargenDone("", "");

}
</dascript>

next go down to the tactics sections and add the following:
<dascript>
// associate some tactics preset table
int nPresetTable;
if(GetCreatureCoreClass(oChar) == CLASS_WARRIOR)
nPresetTable = 1; // tank
else if(GetCreatureCoreClass(oChar) == CLASS_ROGUE)
nPresetTable = 2; // damage dealer
else if(GetCreatureCoreClass(oChar) == CLASS_SHAMAN)
nPresetTable = 1; // damage dealer
else // mage
nPresetTable = 5; // nuker
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

=== Create the module script ===

Create a new script and give it a descriptive name like "loadscript". This script will intercept the Chargen events and redirect them to the custom version of the sys_chargen script you just created. It can also be used to intercept other events if you want to alter other things or add items to a newly created character's inventory.

<dascript>
#include "utility_h"
#include "wrappers_h"
#include "events_h"
void main()
{
event ev = GetCurrentEvent();
int nEvent = GetEventType(ev);
Log_Events("", ev);
switch (nEvent)
{

default:
{
// -----------------------------------------------------------------
// Handle character generation events sent by the engine.
// -----------------------------------------------------------------
if ((nEvent >= EVENT_TYPE_CHARGEN_START && nEvent <= EVENT_TYPE_CHARGEN_END) || nEvent == EVENT_TYPE_PLAYERLEVELUP )
{
HandleEvent(ev, R"ld_sys_chargen.ncs");
}
else
{
Log_Trace(LOG_CHANNEL_EVENTS, GetCurrentScriptName(), Log_GetEventNameById(nEvent) + " (" + ToString(nEvent) + ") *** Unhandled event ***");
}
break;
}
}
}
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

{{TutorialRef|Script}}

== Creating the UTC template file==
Back in the toolset we need to do the following:

Click on the "creature tab" (red head icon)

Right click on default_mage ==> duplicate
Do like the following:

[[Image:Class tut dfs1.jpg]]

Now we need to edit the values and give them some armor and weapons, like so:

Class: Shaman (from dropdown)
Name: Default Male Shaman

[[Image:Class tut dfs2.jpg]]

Now at the top and click SAVE ==> CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

{{TutorialRef|Designer Resources#Creating new resources|Creature|Exporting a module}}

== Creating some strings ==

Start the String editor and right click and insert.

You will be setting up like this

:Table = module talk base
:Owner = module name
:TYPE = GUI

:8000000 - Shaman
:8000001 - Shamans
:8000002 - Shamans commune with spirits to get thier other worldly powers.
:8000004 - Shaman
:8000005 - Shaman Male Name
:8000006 - Shaman Female Name

When all is said close string editor

{{TutorialRef|String editor}}

== Putting it all together ==

Up on top ON THE EXPORT TAB

"EXPORT WITHOUT DEPENDENT RESOURCES"

"GENERATE MODULE XML"

"GENERATE MANIFEST XML"

"EXPORT TALK TABLE"

{{TutorialRef|Exporting a module}}

== Cleaning up ==

DON'T SKIP THIS PART

Delete all files in the name/mydocuments/bioware/dragonage/packages/core/override/toolset; these are not needed.

== Trying it out ==

Start up your game (It may take a min) and start a new game.

*WARNING* IF ANYTHING HAS GONE WRONG HERE YOUR GAME WILL BE SEVERELY DAMAGED

Select MALE ==> HUMAN ==> SHAMAN ==> MAGI

YOU SHOULD SEE YOUR NEW CHARACTER

IF SOMETHING HAPPENED QUIT AND DOUBLE CHECK YOUR STEPS

Make sure you did not miss ANY ";" or "{ }" as a single one of these missed can destroy the game.

== Troubleshooting ==

MY SPELLS ARE NOT SHOWING UP IN THE CREATION SCREEN, HELP!!

* You may not have sort your ability file back to ID. It has to be sorted by ID in order to show up.
* You may not have assigned the new abilities to your new class "5000" in the prereqability column

MY MODEL IS NOT SHOWING UP WHEN I GOTO MALE ==> HUMAN ==> SHAMAN ==> MAGI

* It is very likely you did not EXPORT your default_shaman.utc model
* Double check the background file to make sure you are using default_shaman.utc for the template
* Try rebooting your computer.

[[Category:Character generation]]
[[Category:Tutorials]]

Add A New Class Tutorial

2010-01-31T19:33:24Z

Apolyon6k: /* Open up abi_base.xls */

== Editing the 2das ==
You will need to edit the following 2DA's.
*[[2da_base.xls]]
*[[abi_base.xls]]
*[[ALclassname_default.xls]] (ex ALshaman_default.xls) Copy from ALWizard_default.xls
*[[background.xls]]
*[[cla_base.xls]]
*[[guitypes.xls]]

=== Open up 2da_base.xls ===

Add the following to the end of M2DA_base TAB
{| rules="all" cellpadding="2" style="border: 2pt solid black"
|-
|ID above 100000 ||ALShaman_default ||ALShaman_default
|-
|}
Now SAVE your file

=== Open up guitypes.xls ===
At bottom of list paste this:

{| rules="all" cellpadding="2" style="border: 2pt solid black"
|-
!ID|| Label|| StringId|| Ability|| ProgressBar|| CombatTraining|| SpecialGraphic|| TintColor|| Orphanage|| Flags|| BlendTree
|-
|500|| Class: Shaman|| 8000000|| 5000|| 0|| 0|| 1|| 0x9B0F00|| 0|| 0|| ****
|-
|}
Now SAVE your file

=== Open up CLA_base.xls ===
Paste this AFTER line 3: (Move all down 1)

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:80%"
|-
|4 ||Shaman ||8000000 ||8000001 ||**** ||8000002 ||8000003 ||classico_spirithealer ||CLASS_Shaman ||2 ||95 ||1 ||100 ||5 ||2 ||2 ||2 ||2 ||2 ||0 ||0 ||0 ||55 ||50 ||1 ||5 ||1 ||3 ||0.3 ||4035 ||**** ||1 ||Shaman ||****
|-
|}

Now SAVE your file

=== Open up background.xls ===
On backgrounds tab: You need to insert a section between mage and skill 1, see screenshot

[[Image:Background.jpg]]

On background_defaults there are several section you need to note here regarding the screenshot:

[[Image:Class tut bgdef.jpg]]

How the ID's work, 1 = dwarf, 4 = shaman, 5 = noble, the rest of the pattern is easy.

On lines 12,15,17,19 you need to add these in. What I recommend is just copying these lines

:10 ==> 12
:13 ==> 15
:16 ==> 17
:18 ==> 19

The template string is the default_shaman.utc you will need to create in the toolset later on for these to have a base model
The Ability is the starting ability tied to this class, in my case it just references a different one then what you will have

On chargen_preload there are several section you need to note here regarding the screenshot:

[[Image:Class tut chardef.jpg]]

These ID's must match what is on the background_defaults otherwise the game WILL crash.

Now SAVE your file

=== Open up abi_base.xls ===

in the ABI_Base tab add the following to the bottom of the list

There are several columns that very are important

abilitytype - define what type of ability. melee, spell, skill etc..---> links with abilitytype.xls

prereqability - defines what is needed to have this ability. To add a new class these need to be changed on existing classes.

guitypes - referenced what class this links too ---> links with guitypes.xls

AFTER LINE 119 ==> 4034 HIDDEN_DOG insert a new row and put in the following

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:100%"
|-
|5000||HIDDEN_SHAMAN||0||0||380405||330716||hidden||2||0||0||0||0||0||0||0||1||0||0||12||0||0||0||0||3||1.5||0||0||0||0||0||0||0||0||0||0||0||0||0||0||1||7||0||2||33||0||0||0||0
|-
|}

Add the bottom paste these

{| rules="all" cellpadding="2" style="border: 2pt solid black; width:100%"
|-
|300000||HEROIC_OFFENSE2||380003 ||379523 ||367458 ||379231 ||spl_ico_heroic_offense ||2 ||1 ||0 ||0 ||0 ||20 ||0 ||5000 ||0 ||0 ||0 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||5 ||90215 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90109 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300001 ||HEROIC_AURA2 ||380000 ||379520 ||367458 ||379214 ||spl_ico_heroic_aura ||2 ||1 ||0 ||0 ||0 ||30 ||0 ||300000 ||0 ||4 ||15 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||5 ||90213 ||244 ||247 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||0 ||90110 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300002 ||HEROIC_DEFENSE2 ||380001 ||379521 ||367458 ||379256 ||spl_ico_heroic_defense ||2 ||1 ||0 ||0 ||0 ||40 ||0 ||300001 ||0 ||4 ||20 ||500 ||3 ||0 ||3 ||1 ||4 ||spell_singletarget.ncs ||10 ||90214 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90111 ||128 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||0
|-
| 300003 ||HASTE2 ||380005 ||379525 ||398957 ||379229 ||spl_ico_agility ||2 ||0 ||0 ||0 ||0 ||0 ||60 ||300002 ||0 ||4 ||30 ||500 ||1 ||1 ||18 ||1 ||2 ||spell_modal.ncs ||30 ||90216 ||244 ||247 ||0 ||0 ||2 ||0 ||0 ||0 ||0 ||0 ||0 ||90112 ||192 ||1 ||7 ||0 ||2 ||33 ||0 ||0 ||0 ||10
|-
|}

-------------------------------------------------

NOW HERE IS THE TRICKY PART, MAKE SURE YOU DO THIS RIGHT OR KISS YOUR MODULE GOODBYE

HIGHLIGHT LINE 3 ALL THE WAY DOWN TO 558 (BOTTOM OF THE WORKSHEET)

NOW GOTO DATA --> SORT BY COLUMN S (guitypes) Now they should all be sorted by guitype

Now we need to seperate the mage spells from our new shaman spells.

For guitype spells 1-4, you need to look at the prereqability section for these spells, for those that have 0, replace with 4023
This will make these appear only on the mage from now on. (Which means we need to make seperate skills for our new class)
Ok this will now prevent duplicate of skills

HIGHLIGHT LINE 3 ALL THE WAY DOWN TO 558 (BOTTOM OF THE WORKSHEET)

NOW GOTO DATA --> SORT BY COLUMN A (ID) Now we are back to normal

-------------------------------------------------
Now goto passive_abilities

Paste the following at the bottom of the list
{| rules="all" cellpadding="2" style="border: 2pt solid black;"
|-
|9000||HIDDEN_SHAMAN||1||2||4||2||6||1||str +2,mag +2,con +1
|-
|}

Now SAVE your file :)

=== Open up ALShaman_default.xls ===

Should look like this

[[Image:Class tut alshaman.jpg]]

== Converting the files from 2DA to GDA ==

Create a directory called '''2DA''' on C:, inside that dir create one called override.

In your C:\2da put the following files:

* [[2da_base.xls]]
* [[abi_base.xls]]
* [[background.xls]]
* [[cla_base.xls]]
* [[guitypes.xls]]
* [[ALShaman_default.xls]]

Also: ExcelProcessor.exe from the tool converter in your toolset section.

Next you need to make a batch file to run to convert these.
Simply open notepad, copy and paste below and save as convert.bat

:C:\2DA\ExcelProcessor.exe 2DA_base.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe background.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe CLA_base.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe ALShaman_Default.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe guitypes.xls -outdir=C:\2DA\override\
:C:\2DA\ExcelProcessor.exe ABI_base.xls -outdir=C:\2DA\override\

NOTE: YOU MAY NEED TO "RUN AS ADMINISTRATOR" CONVERT.BAT IN VISTA / W7

VOILA YOU NOW HAVE YOUR GDA FILES FOR THE MODULE

== Creating a module ==
Now we begin editing inside the toolset

Create a new module, similiar to the picture below

'''MAKE SURE YOUR STRING SETS GO FROM IN BETWEEN 8,000,000 - 8,300,000 IF IT GOES ABOVE THAT RANGE THE STRINGS WILL NOT WORK.BIOWARE HAS ALREADY POSTED ABOUT THIS SQL PROBLEM'''

[[Image:Class tut module1.jpg]]

After making it go back to the module screen and select heirarchy and make sure single player is checked

[[Image:Class tut hier.jpg]]

Now that your module is created we need to add the appropriate GDA to the override section.

look in name/mydocuments/bioware/dragonage/addins/modulename

Put these GDA files in: name/mydocuments/bioware/dragonage/addins/modulename/core/override directory

== Editing the scripts==
You now need to edit some scripts.

=== Edit the 2da_constants_h file ===

find the 2da_constants_h file under Core scripts

right click on 2DA_CONSTANTS_H, select CHECK OUT

Go down to the following sections and edit it like below:

<dascript>
const int ABILITY_TALENT_HIDDEN_DUELIST = 4030;
const int ABILITY_TALENT_HIDDEN_RANGER = 4029;
const int ABILITY_TALENT_HIDDEN_REAVER = 4019;
const int ABILITY_TALENT_HIDDEN_ROGUE = 4020;
const int ABILITY_TALENT_HIDDEN_SHALE = 4033;
const int ABILITY_TALENT_HIDDEN_TEMPLAR = 4021;
const int ABILITY_TALENT_HIDDEN_WARRIOR = 4022;
const int ABILITY_TALENT_HIDDEN_SHAMAN = 5000;
const int ABILITY_TALENT_HURLOCK_PROPERTIES = 90080;
const int ABILITY_TALENT_INDOMITABLE = 28;
</dascript>

and

<dascript>
//Class Constants
const int CLASS_WARRIOR = 1;
const int CLASS_WIZARD = 2;
const int CLASS_ROGUE = 3;
const int CLASS_SHAMAN = 4;
const int CLASS_SHAPESHIFTER = 5;
const int CLASS_SPIRITHEALER = 6;
const int CLASS_CHAMPION = 7;
const int CLASS_TEMPLAR = 8;
const int CLASS_BERSERKER = 9;
const int CLASS_REAVER = 10;
const int CLASS_ARCANE_WARRIOR = 11;
const int CLASS_ASSASSIN = 12;
const int CLASS_BLOOD_MAGE = 13;
const int CLASS_BARD = 14;
const int CLASS_RANGER = 15;
const int CLASS_DUELIST = 16;
const int CLASS_SHALE = 17;
const int CLASS_DOG = 18;
const int CLASS_MONSTER_ANIMAL = 19;
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

=== Edit the sys_chargen_h file ===
Find the sys_chargen_h file under _Systems ==> _Includes

right click on sys_chargen_h, select CHECK OUT

Go down to the starting skills section and edit it like below:

<dascript>
// -------------------------------------------------------------------------
// Starting Skills
// -------------------------------------------------------------------------
if (nClass == CLASS_WARRIOR)
{
_AddAbility(oChar, 100100);
}
else if (nClass == CLASS_ROGUE)
{
_AddAbility(oChar, ABILITY_SKILL_POISON_1);
}
else if (nClass == CLASS_WIZARD)
{
_AddAbility(oChar, ABILITY_SKILL_HERBALISM_1);
}
else if (nClass == CLASS_SHAMAN)
{
_AddAbility(oChar, ABILITY_SKILL_HERBALISM_1);
}
}
</dascript>

Next goto starting ability

<dascript>
// ---------------------------------------------------------------------
// Load the starting ability for the background
// ---------------------------------------------------------------------
int nAbility = GetM2DAInt(TABLE_STARTING_EQUIPMENT,"Ability", nIdx);
_AddAbility(oCreature, nAbility);

}
else
{
string sTemplate = "default_player.utc";
switch (nClass)
{
case CLASS_WARRIOR: sTemplate = "default_warrior.utc";
break;
case CLASS_ROGUE: sTemplate = "default_rogue.utc";
break;
case CLASS_WIZARD: sTemplate = "default_wizard.utc";
break;
case CLASS_SHAMAN: sTemplate = "default_shaman.utc";
break;
}

LoadItemsFromTemplate(oCreature, sTemplate, TRUE);
}
}
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

=== Edit the sys_chargen file ===
Find the sys_chargen ==> under _Systems

right click on sys_chargen, select Duplicate; name the file something like wd_sys_chargen.

Change this line:

<dascript>
const int MAX_CLASS_INDEX = 4; // Last index of available base classes in cla_base.
</dascript>
This value does not have to be limited to the minimum number of base classes in the file; it simply has to be higher than the default value.

Go down to the special handling section and edit it like below:

<dascript>
// special handling for aluvian
if (nQuickStart == 0 )
{
Log_Trace(LOG_CHANNEL_CHARACTER,"sys_chargen","Setting default values for player character");

int nRandClass = abs((GetLowResTimer()%3)+1);

if(nRandClass == CLASS_ROGUE || nRandClass == CLASS_WARRIOR || nRandClass == CLASS_SHAMAN)
{
_RunChargen(RACE_HUMAN, nRandClass, oChar, BACKGROUND_NOBLE );
WR_SetPlotFlag(PLT_GEN00PT_BACKGROUNDS, GEN_BACK_HUMAN_NOBLE, TRUE);
}
else // mage
{
_RunChargen(RACE_HUMAN, nRandClass, oChar, BACKGROUND_MAGI );
WR_SetPlotFlag(PLT_GEN00PT_BACKGROUNDS, GEN_BACK_CIRCLE, TRUE);
}

Chargen_SetNumTactics(oChar);
SetCanLevelUp(oChar,Chargen_HasPointsToSpend(oChar));

SendEventModuleChargenDone("", "");

}
</dascript>

next go down to the tactics sections and add the following:
<dascript>
// associate some tactics preset table
int nPresetTable;
if(GetCreatureCoreClass(oChar) == CLASS_WARRIOR)
nPresetTable = 1; // tank
else if(GetCreatureCoreClass(oChar) == CLASS_ROGUE)
nPresetTable = 2; // damage dealer
else if(GetCreatureCoreClass(oChar) == CLASS_SHAMAN)
nPresetTable = 1; // damage dealer
else // mage
nPresetTable = 5; // nuker
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

=== Create the module script ===

Create a new script and give it a descriptive name like "loadscript". This script will intercept the Chargen events and redirect them to the custom version of the sys_chargen script you just created. It can also be used to intercept other events if you want to alter other things or add items to a newly created character's inventory.

<dascript>
#include "utility_h"
#include "wrappers_h"
#include "events_h"
void main()
{
event ev = GetCurrentEvent();
int nEvent = GetEventType(ev);
Log_Events("", ev);
switch (nEvent)
{

default:
{
// -----------------------------------------------------------------
// Handle character generation events sent by the engine.
// -----------------------------------------------------------------
if ((nEvent >= EVENT_TYPE_CHARGEN_START && nEvent <= EVENT_TYPE_CHARGEN_END) || nEvent == EVENT_TYPE_PLAYERLEVELUP )
{
HandleEvent(ev, R"ld_sys_chargen.ncs");
}
else
{
Log_Trace(LOG_CHANNEL_EVENTS, GetCurrentScriptName(), Log_GetEventNameById(nEvent) + " (" + ToString(nEvent) + ") *** Unhandled event ***");
}
break;
}
}
}
</dascript>

Afterwards on top select SAVE then CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

== Creating the UTC template file==
Back in the toolset we need to do the following:

Click on the "creature tab" (red head icon)

Right click on default_mage ==> duplicate
Do like the following:

[[Image:Class tut dfs1.jpg]]

Now we need to edit the values and give them some armor and weapons, like so:

Class: Shaman (from dropdown)
Name: Default Male Shaman

[[Image:Class tut dfs2.jpg]]

Now at the top and click SAVE ==> CHECK IN

Now at the top and click "EXPORT WITHOUT DEPENDENT RESOURCES"

== Creating some strings ==

Start the String editor and right click and insert.

You will be setting up like this

:Table = module talk base
:Owner = module name
:TYPE = GUI

:8000000 - Shaman
:8000001 - Shamans
:8000002 - Shamans commune with spirits to get thier other worldly powers.
:8000004 - Shaman
:8000005 - Shaman Male Name
:8000006 - Shaman Female Name

When all is said close string editor

== Putting it all together ==

Up on top ON THE EXPORT TAB

"EXPORT WITHOUT DEPENDENT RESOURCES"

"GENERATE MODULE XML"

"GENERATE MANIFEST XML"

"EXPORT TALK TABLE"

== Cleaning up ==

DON'T SKIP THIS PART

Delete all files in the name/mydocuments/bioware/dragonage/packages/core/override/toolset; these are not needed.

== Trying it out ==

Start up your game (It may take a min) and start a new game.

*WARNING* IF ANYTHING HAS GONE WRONG HERE YOUR GAME WILL BE SEVERELY DAMAGED

Select MALE ==> HUMAN ==> SHAMAN ==> MAGI

YOU SHOULD SEE YOUR NEW CHARACTER

IF SOMETHING HAPPENED QUIT AND DOUBLE CHECK YOUR STEPS

Make sure you did not miss ANY ";" or "{ }" as a single one of these missed can destroy the game.

== Troubleshooting ==

MY SPELLS ARE NOT SHOWING UP IN THE CREATION SCREEN, HELP!!

* You may not have sort your ability file back to ID. It has to be sorted by ID in order to show up.
* You may not have assigned the new abilities to your new class "5000" in the prereqability column

MY MODEL IS NOT SHOWING UP WHEN I GOTO MALE ==> HUMAN ==> SHAMAN ==> MAGI

* It is very likely you did not EXPORT your default_shaman.utc model
* Double check the background file to make sure you are using default_shaman.utc for the template
* Try rebooting your computer.

[[Category:Character generation]]
[[Category:Tutorials]]

Head morph tutorial

2010-01-31T17:29:44Z

Apolyon6k:

After browsing through about 20 some pages of the forums, I have noticed that, due to the fact that the search is down, people have been posting a lot of the same questions. I do not have the answer to all of these questions, but I will share what I have done so far. Mind you, it's not alot, but hopefully it will help some other people with their questions. Mind you, this is how I do it. My girlfriend and I will add to this as we figure things out/have the time.

Alright, first thing is first. Most people are saying they think their character's faces are hideous and wants to change them, but aren't sure how. Here's how my girlfriend found our how to do it.
== EDITING YOUR CHARACTER'S HEAD/FACE IN THE TOOLSET ==
You Need to make sure that you have played long enough to save your game and that you have picked everything you want the character to have/be (class, race, gender, voice, etc.).

1. Open your toolset

2. Go to File ->New->Morph

[[File:Step_2.jpg|thumb|left]]

<br clear="all">

3. Choose a base to work with (It must be that of the Gender and Race you picked, althought this is not for certain as I have not messed around with putting a female dwarfs head on a human male or whatever. feel free to try at your own risk) Hm = Human Male, HF = Human Female etc etc

[[File:Step_3.jpg|thumb|left]]

<br clear="all">
4. At this point, messing with the head is up to how you want it to look. You can add facial hair to females and makeup to males.
Something that took use forever to figure out is how to change the angle of the head.

[[File:Step_4.jpg|thumb|left]]

<br clear="all">

As marked in red on the image above, you will see that the Object Orientation is set to 0,0,0

So this is how it works:
:Front View of face (default) = 0,0,0
:Right Side view of face = 75,0,0
:Back of Head view = 180,0,0
:Left Side view of Face = 280,0,0

Also, if you don't feel like typing in numbers, holding down CTRL + the right click button (on your mouse) and moving forward/backwards will zoom in and out. Moving it left to right will turn the camera around the head. CTRL + the left click button seems to give your free movement around the entire plane.

5. Once you're finished Save it. However, try not to name it something generic. Once it has been saved, right click on the face and select "Post To Local".
== changing a savegame file in the toolset ==
6. Remember how I told you to play through the game first to save it when you first got the chance to? Well, now we're going into the save information of that file and putting your face you made in the toolset on the character. Close the face you had been working on. I AM DOING THIS FOR MY CHARACTER FLAEMARU SO ANYWHERE YOU SEE HER NAME, JUST SUBTITUTE IT WITH THE NAME OF THE CHARACTER WHOSE FACE YOU'RE CHANGING. Then, go to File->Open File->owner->documents->bioware->dragonage->characters->Flaemaru->Saves(Since I know how to do this I only has one save for her, but pick the save you want to change)->Slot_1->Flaemaru.das

7. Now this part can be a bit confusing or overwhelming if you're not sure what you're doing. But don't fret, I'll walk you though it.

At this point your screen should look like this:
[[File:Step_7a.jpg|thumb|left]]

<br clear="all">
Now, go to SAVEGAME_PLAYERCHAR->SAVEGAME_PLAYERCHAR_CHAR->SAVEGAME_APPEARANCE->SAVEGAME_APPEARANCE_MORPH_NAME

Confused? That's okay.
Maybe this will help: WARNING LARGE IMAGE
[[File:Step7b.jpg|thumb|left]]
<br clear="all">

What is circled in red is what you need to click on to Navigate to where you need to go. The thing circled in light blue is area you need to type in to change the face. IT MUST HAVE THE PROPER PREFIX OF RACE/GENDER AND MUST CONTAIN THE UNDERSCORE
:hm_ = human male
:hf_ = human female
:em_ = elf male
:ef_ = elf female
:dm_ = dwarf male
:df_= dwarf female

Flaemaru is an elf female thus in the blue circled area I type ef_Flaemaru
So if your character's name is Joe and Joe is a Human male and you saved his face that you morphed as 'Joe' then you would type hm_Joe instead.

8. Now before you get all excited, at this point and after, people start to have problems and errors. Like, starting a New Game. When I had first done this I could not start a new game. It kept giving me the "Unable to Load Module" error whenever I tried. When I loaded a saved game, I could not level up, the AI was messed up as none (even
the main character) would not fight enemies. Fear not if this happens however. After 4 hours of serching through the forums here, I found an topic with multiple solutions which can be found here: [http://social.bioware.com/forum/1/topic/8/index/134178].

However, I have found that just going into owner->documents->Bioware->Dragonage->modules and
completely deleting the "Single Player" Folder always fixes my problem.

9. Go load your game of the character whose face you changed. It should be changed to whatever you made in the morph (Althought I'm told some of the 'debug' features don't work sometimes; I have not encountered this problem). Save your game again, and enjoy! If some of the images are too small or you have any questions, feel free to ask my girlfriend and I would be happy to try and help.

How Flaemaru looked before Head Morph (generic female Dalish and generic female Dalish name is she had already saved over it):
[[File:StupidFlaemaru.png|thumb|left]]
<br clear="all">

How Flaemaru looked after head morph:
[[File:Flaemaru.png|thumb|left]]

<br clear="all">
== '''SPOILER WARNING''' ==
Just so everyone knows who uses this tutorial, there is a part in the game where you (the Main Character) enters 'The Fade'. During this part you receive various (four) transformations to help your friends and defeat the demons within. Changing the head morph of your character will cause these transformations to be deformed/glitched to varying degrees. These transformations still function however (atleast they should), so most do not consider it a big deal. I haven't tried this, but I'm told that during this part (if it bothers you that much), you can just go in and delete the head morph from the character and the Transformations will be fine afterwards. As I've said, I've not tried it since the deformation didn't bother me, but it makes sense.

--[[User:RavenNightsight|RavenNightsight]] 04:23, 26 November 2009 (UTC)This was written by my girlfriend Flaemaru Moonwhisper
This tutorial, among others that will also eventually be posted here by me, can be found here: http://social.bioware.com/forum/1/topic/8/index/176308/
[[category:tutorials]]

Character generation

2010-01-26T02:26:54Z

Apolyon6k: /* Skipping Character Generation */

A [[module]] with no event script will start the player without going through character generation, which will leave the player with an almost unusable character to play with. To send the player through a basic character generation UI use the below script as the module event script. This is done by first creating the below script, and saving it, then opening your module properties (file > manage modules > properties), and changing the "script" field to be whatever you named your script (hit the ellipsis and browse for it).

<dascript>
#include "events_h"
#include "global_objects_h"

void main()
{
// keep track of whether the event has been handled
int nEventHandled = FALSE;

event ev = GetCurrentEvent();
switch(GetEventType(ev))
{
case EVENT_TYPE_MODULE_START:
{
// preloads resources needed for character generation
PreloadCharGen();

// initiates character generation
StartCharGen(GetHero(),0);

break;
}
}

// if this event wasn't handled by this script fall through to the core script
if(!nEventHandled)
{
HandleEvent(ev, RESOURCE_SCRIPT_MODULE_CORE);
}
}
</dascript>
==Skipping Character Generation==
A basic script that skips the character generation interface:

<dascript>
#include "sys_chargen_h"
#include "utility_h"

void main()
{
// keep track of whether the event has been handled
int nEventHandled = FALSE;

event ev = GetCurrentEvent();
switch(GetEventType(ev))
{
case EVENT_TYPE_MODULE_START:
{
object oHero = GetHero();

// skip character generation
Chargen_InitializeCharacter(oHero);
Chargen_SelectGender(oHero, GENDER_MALE);
Chargen_SelectRace(oHero, RACE_HUMAN);
Chargen_SelectCoreClass(oHero, CLASS_WARRIOR);
Chargen_SelectBackground(oHero, BACKGROUND_NOBLE);

// give the player some equipment
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_arm_cht_lgt_rlr.uti"));
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_arm_bot_lgt_rlr.uti"));
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_arm_glv_lgt_rlr.uti"));
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_arm_shd_sml_wdn.uti"));
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_wep_mel_lsw_lsw.uti"));

break;
}
}

// if this event wasn't handled by this script fall through to the core script
if(!nEventHandled)
{
HandleEvent(ev, RESOURCE_SCRIPT_MODULE_CORE);
}
}
</dascript>

Another alternative is to create a template creature with the appropriate starting equipment and then call [[LoadItemsFromTemplate]] to copy it to the player:

<dascript>
case EVENT_TYPE_MODULE_START:
{
object oHero = GetHero();

// skip character generation
Chargen_InitializeCharacter(oHero);
Chargen_SelectRace(oHero, RACE_HUMAN);
Chargen_SelectCoreClass(oHero, CLASS_WARRIOR);
Chargen_SelectBackground(oHero, BACKGROUND_NOBLE);

// give the player some equipment
LoadItemsFromTemplate(oHero, "gcd_hero.utc", TRUE);

break;
}
</dascript>

It should be noted that, by skipping the internal character generation process that way, the character will have the correct stats but will be featureless and bald. To change that Bioware is working on an additional function to change the head morph via script.

==Initial levelup or other modifications==
If you want to increase the starting level a basic script can be created by merging one of the above with the following template:

<dascript>
// [additional includes goes here]
#include "sys_rewards_h"

const int FORCE_AUTOLEVEL = 2;

void main()
{
// keep track of whether the event has been handled
int nEventHandled = FALSE;

event ev = GetCurrentEvent();
switch(GetEventType(ev))
{
case EVENT_TYPE_MODULE_START:
{
object oHero = GetHero();

// [chargen code goes here]

// auto-level the player to level 10
RewardXP(oHero, RW_GetXPNeededForLevel(10), FALSE, FALSE);
SetAutoLevelUp(oHero, FORCE_AUTOLEVEL);

break;
}
}

// if this event wasn't handled by this script fall through to the core script
if(!nEventHandled)
{
HandleEvent(ev, RESOURCE_SCRIPT_MODULE_CORE);
}
}
</dascript>

A more sophisticated script could include other set-up code, for example triggering an introductory cinematic to inform the player of the game's plot.

[[Category:Character generation]]

Character generation

2010-01-26T02:22:13Z

Apolyon6k:

A [[module]] with no event script will start the player without going through character generation, which will leave the player with an almost unusable character to play with. To send the player through a basic character generation UI use the below script as the module event script. This is done by first creating the below script, and saving it, then opening your module properties (file > manage modules > properties), and changing the "script" field to be whatever you named your script (hit the ellipsis and browse for it).

<dascript>
#include "events_h"
#include "global_objects_h"

void main()
{
// keep track of whether the event has been handled
int nEventHandled = FALSE;

event ev = GetCurrentEvent();
switch(GetEventType(ev))
{
case EVENT_TYPE_MODULE_START:
{
// preloads resources needed for character generation
PreloadCharGen();

// initiates character generation
StartCharGen(GetHero(),0);

break;
}
}

// if this event wasn't handled by this script fall through to the core script
if(!nEventHandled)
{
HandleEvent(ev, RESOURCE_SCRIPT_MODULE_CORE);
}
}
</dascript>
==Skipping Character Generation==
A basic script that skips the character generation interface:

<dascript>
#include "sys_chargen_h"
#include "utility_h"

void main()
{
// keep track of whether the event has been handled
int nEventHandled = FALSE;

event ev = GetCurrentEvent();
switch(GetEventType(ev))
{
case EVENT_TYPE_MODULE_START:
{
object oHero = GetHero();

// skip character generation
Chargen_InitializeCharacter(oHero);
Chargen_SelectGender(oHero, GENDER_MALE);
Chargen_SelectRace(oHero, RACE_HUMAN);
Chargen_SelectCoreClass(oHero, CLASS_WARRIOR);
Chargen_SelectBackground(oHero, BACKGROUND_NOBLE);

// give the player some equipment
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_arm_cht_lgt_rlr.uti"));
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_arm_bot_lgt_rlr.uti"));
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_arm_glv_lgt_rlr.uti"));
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_arm_shd_sml_wdn.uti"));
EquipItem(oHero, UT_AddItemToInventory(R"gen_im_wep_mel_lsw_lsw.uti"));

break;
}
}

// if this event wasn't handled by this script fall through to the core script
if(!nEventHandled)
{
HandleEvent(ev, RESOURCE_SCRIPT_MODULE_CORE);
}
}
</dascript>

Another alternative is to create a template creature with the appropriate starting equipment and then call [[LoadItemsFromTemplate]] to copy it to the player:

<dascript>
case EVENT_TYPE_MODULE_START:
{
object oHero = GetHero();

// skip character generation
Chargen_InitializeCharacter(oHero);
Chargen_SelectRace(oHero, RACE_HUMAN);
Chargen_SelectCoreClass(oHero, CLASS_WARRIOR);
Chargen_SelectBackground(oHero, BACKGROUND_NOBLE);

// give the player some equipment
LoadItemsFromTemplate(oHero, "gcd_hero.utc", TRUE);

break;
}
</dascript>
==Initial levelup or other modifications==
If you want to increase the starting level a basic script can be created by merging one of the above with the following template:

<dascript>
// [additional includes goes here]
#include "sys_rewards_h"

const int FORCE_AUTOLEVEL = 2;

void main()
{
// keep track of whether the event has been handled
int nEventHandled = FALSE;

event ev = GetCurrentEvent();
switch(GetEventType(ev))
{
case EVENT_TYPE_MODULE_START:
{
object oHero = GetHero();

// [chargen code goes here]

// auto-level the player to level 10
RewardXP(oHero, RW_GetXPNeededForLevel(10), FALSE, FALSE);
SetAutoLevelUp(oHero, FORCE_AUTOLEVEL);

break;
}
}

// if this event wasn't handled by this script fall through to the core script
if(!nEventHandled)
{
HandleEvent(ev, RESOURCE_SCRIPT_MODULE_CORE);
}
}
</dascript>

A more sophisticated script could include other set-up code, for example triggering an introductory cinematic to inform the player of the game's plot.

[[Category:Character generation]]

Social site suggestions

2010-01-26T02:08:22Z

Apolyon6k: /* Duplicate forum navigation tree */

This page is intended as a collaborative repository for suggestions on how to improve the social site. Create a new section for each specific suggestion or related group of suggestions. Feel free to discuss them to some extent on this page, but bear in mind that discussions should be refactored every once in a while into a summary of the idea - the purpose of this page is to consolidate discussion into a more easily-referenced form.

== Projects ==

=== Project "progress" status ===

* Too hard to tell if a project is done or in progress or abandoned.
* There is no filter option or way to mark your project as completed and ready for use. Would be nice if projects could be given a completion attribute (i.e. planning, building, alpha testing, beta testing, released, etc).
* Abandoned projects clutter up the list enormously. Projects should be automatically disabled or flagged if there is no activity in them for some threshold criteria length of time and they remain incomplete/never started.

=== Other project filter options ===

* Advanced Filter Options button. Currently the drop-down boxes for filtering are all independent of one another. If you want to browse in the groups there are 4 lists. Would be nice to have an advanced filtering options button that will pop up a little dialog box where you can make all your selections at once and then say GO!
** Would be nice to be able to filter out completely all those projects with fewer than X members.
** Would be nice to be able to filter out completely all those projects that haven't had any activity at all for X days.
** I would also like to see the author of the project without opening it up.

* When you click on projects the list can only be viewed 10 items at a time, which is way to few.

* Redundant filters: Some of the drop down options are not something anybody would be interested in listing them by or are duplicated by others (e.g. popularity? most views? what is the difference between those two?). Ordering by most views is unlikely to generate a significantly different ordering than sorting by last updated or popularity. All the older projects are likely to have more views than the any of the newer ones, so ordering by create date isn't going to be significantly different than ordering by most views. This isn't a major problem, frankly more options are better than fewer, but the ones you really need (which projects are "the best" and which are "not worth the effort", which are done which are still in progress) aren't there.

=== Rating projects ===

==== Problems with the current rating system ====

* The modules that have been around the longest will have the most "+" while a brand new awesome module may never get noticed. This encourages builders to do a rush job just so they can be one of the first ones out there. Perhaps a weighted rating system, so that a very large/old mod can sit up their with a brand new smaller mod of equal caliber that just hasn't garnered the high amount of ratings yet.

* Provide a checkbox on a project that a host can check when he/she considers the content "done" and ready to be ranked with the others. This would allow you to post work-in-progress downloads to gather feedback, without the concern of getting low ranks because it is not done yet.

* Once you have given a project a "+", there is no way to remove that again, even if you discover later that the project didn't deserve it at all.

==== Variation and changes to the current rating system ====

* Have two ways to rate projects -- one similar to the NWVault's rating system (is it a good idea, do people like it, etc), and another where people could rate the "buggyness" or "stability" or "ease of setup" type things about the project.?

* Or perhaps just a screen with two or three categories to rate that get computed into some overall rating (e.g. Design/Idea 1-10, Stability/Ease of Use 1-10, Something Else 1-10). For me it would be far more useful to be able to filter and sort on these kinds of peer judged criteria than by "most views" or a generic "popularity" with unclear basis.

* Maybe projects need a sex rating system similar to what hollywood does (e.g. G, PG, PG13...XXX).

* NWVault has a rating system where you give a 0-10 score, but the rating is hidden until a specific minimum number of people have rated the project. The average number may be meaningless - in NWNvault, an absurdly high percentage of modules have a rating above 9.0, but still the relative ranking is pretty good - a module with a high score and a high download count is probably worth looking at..

==== Download counting ====

You cannot update a file without losing the download count - it gets reset back to zero. This would need to be fixed - the ideal solution would be to count the number of people downloading files from the project, but at the very least allow people to update files without losing the download count. As it is, the download count is pointless and actually discourages builders from updating their files.

=== Project classification ===

* If a project got incorrectly classified originally, or if a more appropriate category is added later, there is no way to re-classify the project. Allow module owners to change the category of their projects.

* The list of classifications is a mess, with builder-to-builder and builder-to-player categories mixed up. Also, the categories are not well chosen - the NWN modules category is just a pointless waste of space and several categories seem to be missing.
** Add more project categories (areas, scripts, machinima, tutorials, music, and so on)
** Separate builder-to-player content from builder-to-builder content. The biggest hurdle to mod creation is creating levels, so a level category would be particularly useful.

Categories to potentially remove or change:
* NWN module
* It is a bit confusing to have "Dragon Age Addons" as well as "DA Gameplay mods", as to most people those categories overlap.

* Replace the one-big-list project page with a splash page with links to separate categories. Include an "all mods" button so we can still get to the huge list if we want to. And allow mods to be in more than one category.

The list of project categories, in order, at the time of writing is

* Dragon Age addons
* NWN Modules
* Builder - DA Mods
* Builder - DA Textures
* DA Playable Modules
* Builder - DA Utilities
* Builder - DA VO files
* DA Gameplay Mods
* DA Item/Armor/Weapon Mods
* DA Character Mods

Whether or not these names are final, and even though it may not be all that relevant at the moment, I think the list should be sorted either by category or game, in alphabetical order, and that games only be represented in their short form. E.g.

* ...
* Modules - DA(:O)
* Modules - NWN
* ...
* Textures - DA(:O)
* ...

or

* ...
* DA(:O) - Modules
* DA(:O) - Textures
* DA(:O) - Utilities (what are those anyway?)
* DA(:O) - VO Files
* ...
* NWN - Modules
* ...

==== Alternative approach to classification: tags instead of categories ====

Too many/too unspecific categories can cause similar projects are categorized differently because they fit under too many categories. I would suggest only a very general level of categorization and leave the specifics to tags. For instance, allow only a single category for game modules but let the author assign Gameplay, Item, and Character (and any other) tags as applicable.

Two things that would definitely have to be considered for such a solution are:

* if the tags are gathered in one global list, some tags will not make any sense whatsoever for certain projects. On the other hand, category exclusive lists seems like a lot of database bloat, and what do you do when the tag(s) you're looking for are not (yet) in the category your project is in?

* if only the author can assign tags, risk of vandalism is greatly reduced, not to say eliminated. Meanwhile, allowing all users to add/remove tags to/from projects greatly increases the likelihood of the average project being more appropriately categorized (tagged).

=== Subscribed projects view ===

Under ''View'', add "Subscribed projects" - once I have found projects that are sufficiently interesting to want to follow them, I want to be able to find them again easily. Not everyone knows of http://social.bioware.com/user_bw_projects_subscriptions.php

=== Comments on projects ===

The comments on Projects is horrible. If they can be made so you can have more than 10 per page and be able to jump to any page in the comments they'd be much better.

=== Captchas in project forums ===

Could we drop having to solve a captcha to post in a project forum? It ties into the problem above about the comment system, which is all the captcha system probably reinforces, and seems kind of pointless given how somebody could just spam up the comments anyway.

=== Project comments -- show newest comments first ===

Please show the latest comments FIRST!!

Currently when you go to view comments under a project, it shows the very first comments. It is supposed to show the newest comments first. I have a project that has roughly 190 comments. That means I have to click Next Page 19 times!!!

=== Extend valid file types for projects ===

I created (what is now) a DA Playable Modules project. In addition to uploading the module (DAZIP) file I want to upload the builder-to-builder (DADBDATA) file and the art resources (in this case just LVL files) so that the community could see how we made the module. However the valid types for a DA Playable Modules project do not allow these file types. I am loathe to made another project simply to accommodate these additional file types so I am requesting the project's file types be extended to allow all extensions associated with Dragon Age and ZIP/RAR in addition to the ones already allowed.

See: [http://social.bioware.com/project/334/discussion/586/|Little Red Riding Hood Redux] for the example

== Forums ==

=== Jumping to specific posts off the Feed Page ===

It would be nice to be able to jump directly to the post that was made by the person in my Network (friends, etc.) off the Feed Page. Currently, you can jump to the thread, but when threads are lots of pages long, you often have to go hunting to see what your buddy wrote in that topic. Having a way to jump directly to their specific post in the Topic would be very helpful.

=== Contract/expand social site forums ===

Can you guys add the contract/expand forum section like old BioBoard has? (with the keep settings for next time I open the browser too) I don't want ME forum taking over the whole top of my monitor when I click ''Forums.'' Thank you! (not for now, at least... after I get it, perhaps! =)

=== Forum filtering ===

Please can we have a way of filtering the ''Recent Forum Posts'' section on the home page. People still insist on putting spoilers in titles and being the "most recent" means they appear before a moderator has had chance to edit them.

Related: can we have the ability to filter our recent activity by forum so that we can hide spoiler forums for the same reason (and to hide forums we aren't interested in).

=== Jump directly to ''Your Post'' from the ''Your Posts'' list ===

Heya, I love the ''Your posts'' thing, but is there a way to directly jump to my particular post in the listed topics? Instead of picking a page or going to last post, that is.

=== Edit post => redirect ===

Editing a post takes you to the start of the thread. It should take you to the page in the thread your post is on, ideally the post itself.

=== Recent post entry should go to first unread ===

When there is support for it, assuming there will be, clicking an entry in the ''Recent Forum Posts'' list should take you to the first unread post in the thread. Without proper context the last post is useless anyway.

=== Duplicate forum navigation tree ===

Display the forum navigation tree (e.g. ''Forum Home » BioWare General » Social.bioware.com Site Help'') at the bottom of the forum as well. Currently it exists only at the top, and having to scroll all the way up after reaching the end of a page gets annoying.
===Better search function===
When search for a specific topic the search function only displays posts with the topic in the title but unfortunately most users use "have a problem", "toolset issue" or "need help" as title for their post. The search function should look for the specified word inside the posts to give more results to have a look at.
Because of that limitation there are about 10 or even more topics about changing a head morph which essentially have the same questions with the same answers in them...

== Other ==

=== Make use of ''title'' attributes ===

For anchor and image tags especially, using the ''title'' tags would greatly increase the site's usability. Icons should have their meaning added, entries in the ''Recent Forum Posts'' list should have the full topic.

=== Remove HTML support ===

Comment boxes make mention of very limited HTML tag support. It should be removed in favour of BBCode. There's no point in having both and 1) BBCode is safer/smoother, and 2) likely much better known.

=== Quote box layout ===

The source doesn't stand apart from the quote and a timestamp would be greatly appreciated. Dotted and dashed borders also cause some wonkiness, as illustrated by [http://i36.tinypic.com/jgh2s9.jpg the picture].

=== Navigating group discussion threads ===

Clicking ''Quote'' currently jumps you directly to the reply form at the bottom of the page. This is extremely annoying if you haven't already read the entire page (in which case you would be at the reply form anyway) or need to quote multiple people. Although it serves as feedback to inform the user that the action was registered, and removing it could imply that it's broken, the break in flow there exists now is undesirable.

Additionally, when going back and forth (previous/next page), contents of the reply form should be retained. This will make it easier to reply to multiple posts across several pages.

=== Report XX to moderators ===

Due primarily to timezone obstacles, reporting posts, users, etc. straight to moderators can be very inefficient, which in turn means it is not done as often as it perhaps should be. The ability to make a single report accessible by all moderators, such that it can be dealt with by anyone present, would be a huge boon.

= Social Site Bug Reporting Area =

Initially, let's use this little area on the suggestions page for bug reporting. Ultimately, it would be good to have a separate page like the one that exists for the Toolset.

== Project Discussions, Next Page >> Button leads to 404 Error ==

There are two places to click "Next Page" in the project discussions area. One at the top, and one at the bottom. The one at the top works fine, but the one at the bottom leads to a 404 error page

{{EV|214171|[[User:BryanDerksen|BryanDerksen]]}}

== Private Group Posts showing to non-Group members in Personal Feed ==

OK. Here is a summary of the BUG, in case it hasn't been reported (but I think it has). To reproduce the BUG, do the following:

* In Profile, Privacy Options, enable (check on) "Starting a Project Discussion Topic" and "Posting in a Project Discussion Topic".
* Go to one of your private projects.
* Post a New Discussion Topic
* Ask one of your friends that is not part of the Private Project to review your feed ... they will tell you that they can see both the New Topic and the Reply in your feed.

If you un-flag the two items you had flagged, your friend won't see the topics anymore (new ones)

This tells me that the Privacy Options are working as intended, but they are not being over-ridden by the privacy options on the project profile. In my opinion, you should be able to show project discussions through your feed, however, the privacy of the project should over-ride that setting.

{{EV|214174|[[User:BryanDerksen|BryanDerksen]]}}

[[Category:Feature requests]]

2DA

2010-01-25T17:17:10Z

Apolyon6k: /* Users of Open Office */

Many of the properties of objects in the toolset make reference to 2DAs (two-dimensional arrays). These are read-only arrays containing various data used by scripting and the game engine. For example, the set of local variables that an object supports is defined in a 2DA.

__TOC__
== Overview ==

Simplified the 2DAs can probably be seen as laying the stack of cards which is swords, enemies, and variables to them. In which context the games rules set by the Gameengine and Scripts would tell who can draw which card, and the Gamedesigner distributes these cards to participants.

There is a tight connection between all 3 of those, and linking to and from and inbetween 2DA's is done via ID's. An Designer creating an Item for example links to ID's of [[BITM_base.xls|BITM_base]] and [[ItemVariations.xls|ItemVariations]] giving the Item a Base Type with which the Gameengine can apply rules, and a [[Model]] to display it if Basetype properties allow ,set in a 2DA as well. Also it is the Gameengine who knows what column to look for Values, and it allows setting a Base Type in the first place, so that the link to [[BITM_base.xls|BITM_base]] exists.

Of course it is a bad idea to break any of those links. However, adding anything is possible (preferably via M2DA see below), which requires to stay with the original layout and knowledge about the sources needed. Only a Designer would have to ''"lay the new cards"''. Or creating entirly new 2DA's is also possible, which additionally requires to create Scripts ,so the Gameengine will know the new 2DA exists.

The source files for 2DAs are Microsoft Excel worksheets. This allows a wide variety of sophisticated techniques to be used to generate the values of the 2DA fields, such as macros and formulas. It also makes editing much easier since the columns can be annotated and formatted in helpful ways, and multiple related worksheets can be grouped into one file. Before they can be used by the toolset or the game, 2DAs must be converted from Excel files into a more efficient form. Processed 2DAs are stored in files with the .[[GDA]] extension.

== Excel file formatting ==

{| border="2" cellpadding="5" cellspacing="0" width="700pt" align"left"
|+ '''Example Worksheet "Monsters"'''
| width="30pt" style="background-color:#808080" |'''ID'''
| width="30pt" style="background-color:#AFAFAF" |'''Label'''
| width="50pt" style="background-color:#AFAFAF" |'''Strenght'''
| width="50pt" style="background-color:#AFAFAF" |'''Name'''
| width="50pt" style="background-color:#AFAFAF" |'''ResourceExample'''
| width="50pt" style="background-color:#AFAFAF" |'''Scale'''
| width="50pt" style="background-color:#AFAFAF" |'''disabled'''
| width="50pt" style="background-color:#AFAFAF" |'''Commentexample'''
|-
| style="background-color:#AFAFAF" |'''''int'''''
| style="background-color:#AFAFAF" |'''''string'''''
| style="background-color:#AFAFAF" |'''''int'''''
| style="background-color:#AFAFAF" |'''''string'''''
| style="background-color:#AFAFAF" |'''''resource'''''
| style="background-color:#AFAFAF" |'''''float'''''
| style="background-color:#AFAFAF" |'''''bool'''''
| style="background-color:#AFAFAF" |'''''comment'''''
|-
| style="background-color:#AFAFAF" |0
|Evilmonster1
|23
|Abomination
|prp_barrel01
|1,0
|0
|totally evil
|-
| style="background-color:#AFAFAF" |1
|Evilmonster2
|34
|Shriek
|prp_bucket_01
|1,0
|1
|very bad
|}

Data in a 2DA is identified by a row number, with the first row (row zero) usually being reserved for internal use (undefined value, etc.) by convention. Each row has an arbitrary number of columns identified by strings. The grey fields in this example table are very specific to the 2DA, the white fields are arbitrary data which the Gameengine identifies for that 2DA.

The ID of a Row is the reference for the Game to access and link to them. As such they are unique across the 2DA, and any M2DA that extends it. The contents of each column is specific to the 2DA given, and arbitrary. When extending a 2DA, new ID's have to be given, and Columns have to be exactly the same.

=== Guidelines ===
*Cell A1 will contain "ID". This is checked by the processor and the worksheet will fail if this is not the case.
*Column A starting at line 3 will contain an integer row ID number that is unique to that row across all files (unless creating an M2DA override). Row IDs will be listed from smallest to highest within the same file and do not need to be consecutive.
*A blank row or column will determine the dimension of the spreadsheet in that direction. Everything past that point is ignored by the binarizer.
*Column names are case sensitive. This is because of the CRC32 algorithm used to generate the hash key. Changing the case of a column name after it is in use will break the game. White space before and after a column name will be removed before hashing.
*Row 2 will be a "types" row. Each is a single word: [[int]], [[string]] (single chars as well), [[resource]], [[float]] or [[bool]]. A special type "[[comment]]" can be used to exclude a column from export.
*Any column with string data that refers to files should have a type of "resource" and not "string". This is because the "resource" type is used to determine dependencies for the 2DA file.
*'bool' type may be one of: a zero or non-zero number, Yes or No (case insensitive), or words beginning with T or F (such as True! and False!). NOTE: You cannot use TRUE and FALSE because Excel converts those to a special keyword the binarizer can't parse properly at this time. '''Note:''' the scripting language doesn't have a function for retrieving boolean values from a 2DA, and the behavior of Get2DAInt when retrieving a boolean is untested. It is probably safer to just use an integer for scripting purposes.
*If you wish to leave a cell unfilled, the string "****" (four asterisks) can be inserted instead of a value.
*Any worksheets that are not exportable 2DA data will have an underscore prepended to their name - the resource builder will subsequently ignore them.
*Worksheets need to have unique names among all excel files, duplicates will overwrite each other as each worksheet is exported as a file
*You cannot have the workbook open in Excel at the same time as running the binarizer on it.
*Strings have a maximum length of 768 characters. Anything longer will be truncated.
*ExcelProcessor.exe constrains the name length of a worksheet to 27 characters.

== Extending the game via M2DAs ==

{| border="2" cellpadding="5" cellspacing="0" width="700pt" align"left"
|+ '''Example Worksheet "MonstersCustom"'''
| width="30pt" style="background-color:#808080" |'''ID'''
| width="30pt" style="background-color:#AFAFAF" |'''Label'''
| width="50pt" style="background-color:#AFAFAF" |'''Strenght'''
| width="50pt" style="background-color:#AFAFAF" |'''Name'''
| width="50pt" style="background-color:#AFAFAF" |'''ResourceExample'''
| width="50pt" style="background-color:#AFAFAF" |'''Scale'''
| width="50pt" style="background-color:#AFAFAF" |'''disabled'''
| width="50pt" style="background-color:#AFAFAF" |'''Commentexample'''
|-
| style="background-color:#AFAFAF" |'''''int'''''
| style="background-color:#AFAFAF" |'''''string'''''
| style="background-color:#AFAFAF" |'''''int'''''
| style="background-color:#AFAFAF" |'''''string'''''
| style="background-color:#AFAFAF" |'''''resource'''''
| style="background-color:#AFAFAF" |'''''float'''''
| style="background-color:#AFAFAF" |'''''bool'''''
| style="background-color:#AFAFAF" |'''''comment'''''
|-
| style="background-color:#AFAFAF" |2300000
|Evilmonster3
|32
|Wolf
|c_wolfa
|1,0
|0
|New Monster
|}

An "M2DA" is a "Multiple 2DA" that stacks a number of 2DA files into one larger table. They work much like single 2DA files except they can be patched or expanded later by adding more resources. These are useful for any table that lists other resources, such as appearance tables, so that new resources can be added later without having to modify a monolithic table. 2DAs are merged row by row, keyed on the ID column.

This is especially important for third-party modders, since BioWare might release an update to a core table at a later date that would overwrite any changes third parties had made to it. By using an M2DA with a unique name, and by using a range of ID numbers significantly separated from those already in use, you can ensure that your additions won't conflict with other portions of the M2DA.

A list of all M2DAs used by the game can be found in [[2DA_base.xls]]. Every 2da listed in M2DA_base is treated as a M2DA, except for those with an ID between 10000 and 10999 which are handled as regular 2DAs. Each M2DA has a label that describes the subject covered by the M2DA and a worksheet prefix that all components of that M2DA must use.

Every worksheet listed in the [[2DA_base.xls]] file is actually a prefix. The system reads this prefix and then searches through all the 2DAs for the ones starting with this prefix and merges them together as one 2DA. For example: M2DA ID 0 is "ANIM_". The system looks through its list of 2das and finds "ANIM_base", "ANIM_combat" and "ANIM_walk". It will read and merge all 3 2DAs into an M2DA called "ANIM_".

This example 2DA "MonstersCustom" would be merged into the original 2DA "Monsters", if "Monsters" were one of the worksheets listed in the M2DA_base.

=== Reserved ID Ranges ===

While M2DA files avoid some of the problems associated with ordinary 2DA files, the IDs in each row of the final M2DA must still be unique across all 2DAs associated with it.

To help ensure compatibility between authors' custom content, you should make sure that the ranges you choose don't conflict with ones already in use: [[2DA_ranges_in_use]].

=== Bug with M2DA ===

It should be noted, that currently there is a bug with certain M2DA's, which prevents new ID's above 255 to work in the game. It is unclear which are affected, but most certainly it is [[ItemVariations.xls]] related. See [[Bug: High M2DA ID ranges might work in the toolset, but not in game|Bug report]].

== Converting XLS files into 2DA files ==

In the "Dragon Age\tools\ResourceBuild\Processors" folder there is an executable named "ExcelProcessor.exe". This is the file that handles conversions from XLS to 2DA format. Below are described 3 ways in which this file may be used.

=== Drag & Drop Method ===

# Copy ExcelProcessor.exe and source .XLS files to a new directory (not explicitly neccessary, but advised)
# Select source .XLS files and drag them onto ExcelProcessor.exe
# Cut & Paste resulting .2DA files, which will be located in the same directory as the source .XLS files, to your desired location (usually to "My Documents\BioWare\Dragon Age\AddIns\yourmodulename\module\overrides\")

=== Adding 2DA export to the Windows XP file explorer ===

Here's an easy way to add a context (ie, right-click) menu item that quickly converts new or updated Dragon Age Excel files into GDA format:

Setup:

# Open Windows Explorer and click Tools | Folder Options.
# In the File Types tab, select the XLS extension from the list and click the Advanced button.
# Click the New button and put 'Binarize 2DA' in the Action field.
# Paste the following in the Application field and click OK (update the drive and folder names to match your client): <tt>"C:\Program Files\Dragon Age\tools\ResourceBuild\Processors\ExcelProcessor.exe" "%1" -outdir="C:\Documents and Settings\YOURNAME\My Documents\BioWare\Dragon Age\packages\core\override"</tt>
## For the Steam version, use the following: <tt>"C:\Program Files\Steam\steamapps\common\dragon age origins\tools\ResourceBuild\Processors\ExcelProcessor.exe" "%1" -outdir="C:\Documents and Settings\YOURNAME\My Documents\BioWare\Dragon Age\packages\core\override"</tt>

Note that paths with spaces in them can cause Windows trouble, if your paths have spaces in them remember to wrap them in quotation marks.

Usage:

# Using Windows Explorer, navigate to your 2DA folder (in my case C:\DA\tag\main\data\Source\2DA) and select the Excel file(s) to process. Right click and select 'Binarize 2DA' from the context menu.
# Confirm a corresponding GDA file is created in your override folder (in my case C:\DA\tag\main\build\packages\core\override) for each Excel file processed.

[[File:Adding binarize 2da to Windows XP explorer.png|center|thumb|300px|An example of how setting this up in Windows XP looks]]

=== Using a .BAT file ===

The following method may work better for you instead:

*Create two folders called C:\2DA\ and C:\2DA\Override\
*Copy ExcelProcessor.exe to C:\2DA\
*Copy the Excel spreadsheets containing the 2DA you want to use in the game to C:\2DA\
*Create a batch file with the following line in it (change "placeables.xls" to whatever Excel file you're working with):
C:\2DA\ExcelProcessor.exe placeables.xls -outdir=C:\2DA\override\
*Run your batch file
*Find the GDA file from the C:\2DA\Override\ directory and copy it to the game's override directory. Remember to take into account the naming conventions of M2DAs; you may need to rename your 2DA files with a new suffix unique to your module to allow it to add to the core 2DAs without conflict.
*'''If you copied your new 2DA file in your Override directory while Dragon Age Game was running, you will need to exit to windows and re-run the game to let your changes to work.'''

== 2DA XLS files used in Dragon Age ==

''Note: This list is very incomplete right now''

Bear in mind that 2DAs names are actually based on the names of the worksheets inside these Excel files, not the names of the files themselves. Some of these files contain a large number of individual 2DAs within them. They are bundled together into Excel files based on the nature of the 2DAs for convenience. They can be found under the toolsets directory
<pre>*Installdir*\Dragon Age\tools\Source\2DA\</pre>

=== Creatures ===

*[[APR_base.xls]] - appearance types for creatures
*[[ABI_base.xls]] - integrates all talents and spells into the game
*[[ANIM_base.xls]]
*[[ANIM_combat.xls]]
*[[ANIM placeables.xls]]
*[[SyncAnimations.xls]]
*[[CLA_base.xls]] - Defines the character classes used throughout the game
*[[background.xls]] - defines the various origin stories available to each race and class.

=== Objects ===
*[[placeables.xls]] - interactive object types
*[[BITM base.xls]] - item types
*[[ItemVariations.xls]] - item appearance variations (eg, all the different ways a longsword can look)
*[[PRJ_base.xls]] - how various projectiles look and behave
*[[VFX_base.xls]] - Visual effects

=== Areas and plots ===

*[[worldmaps.xls]] - world maps for open-ended travel between areas
*[[plottypes.xls]] - how plots are grouped at the highest level in the game GUI (codex entry types, story, etc.)
*[[areadata.xls]] - sets various properties for specific areas
*[[rewards.xls]] - rewards for plot completion

=== Adding to the official campaign ===
*[[PRCSCR]] - "Pre Release Content Script" - specifies scripts to run when an area or area list is loaded or entered.

== Adding Strings ==

When adding strings to a 2DA, you have two options. The simplest is to enter **** for the StringID column. In that case, the name column will be used in the game.

The other approach is to use the toolset's string editor to create a new string. When that happens, you'll get a new StringID. Next enter that number into the StringID column in the 2DA.

The second approach works better when translating your module, at the cost of portability. If someone else wanted to reuse your 2DA, they'd have to generate their own strings, then update the StringID number based on these IDs.

'''Attention:'''

* The current version of the "ExelProcessor"-App is buggy as it can't hanlde INT values above 8388607! Many thanks to elys for figuring that out.
* Also note that the original toolset (v1.0) core-talktable contains wrong ids as well - don't forget to delete it from the "packages\core\override\toolsetexport" directory if you are still using that version.

'''Workaround:'''

* Create and export your talktable, delete the core-talktable override.
* Create your M2DA File that you want to refer to your talk-table strings. Never Mind using the real IDs at this stage.
* Use the "Exelprocessor" to create the GDA file.
* Open the GDA-File with the toolset or elys's GDA-Editor App (http://social.bioware.com/project/755/)
[[File:Edit-GDA-Values.jpg]]
* Change the StringIDs to the StringIDs in your talktable.

'''Remark:'''

The previous Version stated: ''Take that StringID and add 16777216 to the number.'' this appears to be wrong and is likely a holdover from NWN.

== Users of Open Office ==
* Users of Open Office may find that no .gda file is created when they use ExcelProcessor.exe - one workaround is to copy a worksheet from an existing .xls file (such as placeable_types from placeables.xls), process the file, then remove the extraneous .gda file (e.g. placeable_types.gda). Alternately, upload your .xls file to Google Docs and then download the file as Excel format, then process the file with ExcelProcessor.exe.
* When editing existing xls files, it also works to leave the format as standard while saving the file. Open Office asks to change the file to its own spreatsheet format when saving a format other then its own, don't change the format and it should work.

[[Category:2DAs]]

Feature request: proper export directories

2010-01-24T22:58:54Z

Apolyon6k: Created page with 'Many problems with the toolset come from exported files in the packages\core\override directory. if the export process would export files to addins\"modulename"\core\override ma...'

Many problems with the toolset come from exported files in the packages\core\override directory.

if the export process would export files to addins\"modulename"\core\override many issues could be avoided.

as i understand the hierarchy the addins core directory would be loaded first
so the exporter should export to that directory first and foremost

the moving of files from addins\"modulename"\core\ to addins\"modulename"\module\override seems to be still important when the files should only be used in that module alone

the problem is also that some dependant resources namely scripts and plots in packages core cause problem ingame sometimes even unrelated problems like wynne not being able to join the party in the circle tower when some generic plot was exported (but not changed) into the packages\core directory.
after deleting those files everythings works fine again
fyi: the export was '''without''' dependant resources!
[[Category:Feature requests]]

Tutorials

2010-01-24T09:05:06Z

Apolyon6k: /* External Tutorials */

This page lists links to step-by-step tutorials, both on this wiki and on external sites.

See also the [[How-tos]] page, which contains much smaller and more focused guides on how to accomplish various common tasks.

==Introductory tutorials ==

In the course of these tutorials we'll go through all the steps needed to create a basic adventure.

{{sidebox|
*Boxes like this contain a checklist of important steps.
*They're intended as a reminder and as a navigational aid.
}}

*[[Introductory tutorial]] - An overview of the toolset as a whole
*[[Module tutorial]] - how to create a module to work in.

This set of tutorials forms a series, each building on or filling in omissions by the last:
*[[Area tutorial]]
*[[Placeable tutorial]]
*[[Item tutorial]]
*[[Creature tutorial]]
*[[Conversation tutorial]]

Once you've become familiar with the basics introduced on those tutorials you might have a better grounding for:
*[[Cutscene tutorial]]
*[[Map tutorial]] (which also introduces you to [[2DA]] editing)
*[[Level Editor Tutorial]]
*[[Scripting tutorial]]

== Demo module ==

The toolset currently ships with a simple demo module pre-loaded into its database.

*[[Demo module]] - how to export and run the demo module.

== Custom content tutorials ==
*[[Tutorial: Using DLC areas in your mods]]
*[[Tutorial: Adding custom items to custom modules]]
*[[Tutorial: Adding a Custom Model to Toolset]]
*[[Tutorial: Creating a custom placeable from a model]]
*[[Tutorial: Reskinning an Item]]
*[[Tutorial: Creating recolors of existing items]]
*[[Tutorial: Understanding Tints: Overriding Defaults & Creating New Ones]]
*[[Adding a New Spell Tutorial]]

== Character generation tutorials ==
*[[Backgrounds tutorial]]
*[[Add A New Class Tutorial]]

== Other Tutorials ==
*[[ToolSet: Area Layouts]]
*[[Adding a Location to the Single Player Campaign Tutorial]]
*[[Follower tutorial]] (Simple and advanced, requires scripting knowledge)

== External Tutorials ==
*[http://lerlek.se/Video+Tutorials Lerlek Dragon Age Origins Toolset Video Tutorials Collection] has collected many in-depth video tutorials.
*[http://dragonagemodding.wordpress.com Beyond Ferelden] has many in-depth tutorials by jwvanderbeck.
*[http://www.youtube.com/watch?v=TwQNRBFLhrE Playable Area and Conversation] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=CaHldJcUTz8 Simple Conversation Cameras] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=QOQJ2heQto4 Cutscene and Trigger] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=szWKgj2ZuXo Custom Level and Room Building] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=DKJ7F14n8o8 Downloading and Installing the Toolset] video tutorial by [http://social.bioware.com/74287/ DragonAge22].
*[http://www.youtube.com/watch?v=iMPBsulv9xI Creating a Room] video tutorial by [http://social.bioware.com/74287/ DragonAge22].
*[http://www.youtube.com/watch?v=g3kx2CaarHo How to Make an Interior Level with Lighting] video tutorial by [http://social.bioware.com/group/60/ Darkworld Development Team].
*[http://www.youtube.com/watch?v=O6TeZeE1Lc8 Making a Room] video tutorial by BigDrip681.
*[http://social.bioware.com/5339/blog/576/ Custom Player Items In Single Player] by [http://social.bioware.com/5339/ weriK].
*[http://social.bioware.com/5339/blog/651/ The Secret Behind Item Statistics] by [http://social.bioware.com/5339/ weriK].
*[http://social.bioware.com/project/923/ Guide for installing/uninstalling/updating Mods] Beginner Guide to get started with using Mods by [http://social.bioware.com/237411/ Alexspeed].
*[http://www.jezelf.co.uk/tutorials.htm Photoshop Map making tutorials] Credits to Jason Elford, brought to DAT wiki by [http://social.bioware.com/48156/ Arixsus]
*[http://social.bioware.com/project/527/ Video Tutorials by SilentCid] Multiple in-depth video tutorials of the DA Toolset
*[http://www.youtube.com/view_play_list?p=EF29DD1AACEBA92A Qkrch's Video Tutorials] Toolset tutorial complete series for the experienced builder (Spanish & English)
*[http://www.theengineeringguild.co.uk/da-new-campaign-location-tutorial World Editing and Area Creation] Tutorial by [http://social.bioware.com/profile/7848 giskard44] where he walks you through a module creation process for an single player addin.
[[Category:Tutorials| ]]

Tutorials

2010-01-24T09:04:34Z

Apolyon6k: /* External Tutorials */

This page lists links to step-by-step tutorials, both on this wiki and on external sites.

See also the [[How-tos]] page, which contains much smaller and more focused guides on how to accomplish various common tasks.

==Introductory tutorials ==

In the course of these tutorials we'll go through all the steps needed to create a basic adventure.

{{sidebox|
*Boxes like this contain a checklist of important steps.
*They're intended as a reminder and as a navigational aid.
}}

*[[Introductory tutorial]] - An overview of the toolset as a whole
*[[Module tutorial]] - how to create a module to work in.

This set of tutorials forms a series, each building on or filling in omissions by the last:
*[[Area tutorial]]
*[[Placeable tutorial]]
*[[Item tutorial]]
*[[Creature tutorial]]
*[[Conversation tutorial]]

Once you've become familiar with the basics introduced on those tutorials you might have a better grounding for:
*[[Cutscene tutorial]]
*[[Map tutorial]] (which also introduces you to [[2DA]] editing)
*[[Level Editor Tutorial]]
*[[Scripting tutorial]]

== Demo module ==

The toolset currently ships with a simple demo module pre-loaded into its database.

*[[Demo module]] - how to export and run the demo module.

== Custom content tutorials ==
*[[Tutorial: Using DLC areas in your mods]]
*[[Tutorial: Adding custom items to custom modules]]
*[[Tutorial: Adding a Custom Model to Toolset]]
*[[Tutorial: Creating a custom placeable from a model]]
*[[Tutorial: Reskinning an Item]]
*[[Tutorial: Creating recolors of existing items]]
*[[Tutorial: Understanding Tints: Overriding Defaults & Creating New Ones]]
*[[Adding a New Spell Tutorial]]

== Character generation tutorials ==
*[[Backgrounds tutorial]]
*[[Add A New Class Tutorial]]

== Other Tutorials ==
*[[ToolSet: Area Layouts]]
*[[Adding a Location to the Single Player Campaign Tutorial]]
*[[Follower tutorial]] (Simple and advanced, requires scripting knowledge)

== External Tutorials ==
*[http://lerlek.se/Video+Tutorials Lerlek Dragon Age Origins Toolset Video Tutorials Collection] has collected many in-depth video tutorials.
*[http://dragonagemodding.wordpress.com Beyond Ferelden] has many in-depth tutorials by jwvanderbeck.
*[http://www.youtube.com/watch?v=TwQNRBFLhrE Playable Area and Conversation] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=CaHldJcUTz8 Simple Conversation Cameras] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=QOQJ2heQto4 Cutscene and Trigger] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=szWKgj2ZuXo Custom Level and Room Building] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=DKJ7F14n8o8 Downloading and Installing the Toolset] video tutorial by [http://social.bioware.com/74287/ DragonAge22].
*[http://www.youtube.com/watch?v=iMPBsulv9xI Creating a Room] video tutorial by [http://social.bioware.com/74287/ DragonAge22].
*[http://www.youtube.com/watch?v=g3kx2CaarHo How to Make an Interior Level with Lighting] video tutorial by [http://social.bioware.com/group/60/ Darkworld Development Team].
*[http://www.youtube.com/watch?v=O6TeZeE1Lc8 Making a Room] video tutorial by BigDrip681.
*[http://social.bioware.com/5339/blog/576/ Custom Player Items In Single Player] by [http://social.bioware.com/5339/ weriK].
*[http://social.bioware.com/5339/blog/651/ The Secret Behind Item Statistics] by [http://social.bioware.com/5339/ weriK].
*[http://social.bioware.com/project/923/ Guide for installing/uninstalling/updating Mods] Beginner Guide to get started with using Mods by [http://social.bioware.com/237411/ Alexspeed].
*[http://www.jezelf.co.uk/tutorials.htm Photoshop Map making tutorials] Credits to Jason Elford, brought to DAT wiki by [http://social.bioware.com/48156/ Arixsus]
*[http://social.bioware.com/project/527/ Video Tutorials by SilentCid] Multiple in-depth video tutorials of the DA Toolset
*[http://www.youtube.com/view_play_list?p=EF29DD1AACEBA92A Qkrch's Video Tutorials] Toolset tutorial complete series for the experienced builder (Spanish & English)
*[http://www.theengineeringguild.co.uk/da-new-campaign-location-tutorial] Tutorial by [http://social.bioware.com/profile/7848 giskard44] where he walks you through a module creation process for an single player addin.
[[Category:Tutorials| ]]

User:Apolyon6k

2010-01-24T00:10:05Z

Apolyon6k: Created page with 'simple user with some wiki experience likes to edit tables and tries to remove horizontal scrolling from webpages...'

simple user with some wiki experience

likes to edit tables and tries to remove horizontal scrolling from webpages...

Adding custom items to custom modules tutorial

2010-01-21T19:00:21Z

Apolyon6k: /* Creating a script to summon your item */

This guide will show you the easiest way to create a custom item and add it to your inventory by using a console command '''runscript aa_give_item'''.

There are people who say that using the default 'singleplayer' module is a source for future problems so we'll be using are own module.

I hope this tutorial helps.

Author: RandyG [mailto:randy@pcwinsupport.com Email Me]

Revised by LazyMonk.

Thanks LazyMonk, I'll probably add pictures later to make it easier

== Things needed ==
*1. Dragon age origins game.
*2. Access to the console in-game ([http://dragonage.wikia.com/wiki/Console Instructions on accessing console]).
*3. Dragon age origins Toolset.
*4. Ability to follow instructions.

== Creating a new module ==
*1. Open the toolset and click on '''File -> Manage Modules'''.
*2. Click '''New'''.
*3. Enter 'my_module' in ''Name'' and ''UID'' fields, ignore the rest. Click '''OK'''.
*4. Double-click 'my_module' that was added to the list.

== Creating an item ==

*1. On the palette window select items (the sword icon).
*2. Choose an item under global.
*3. Right click on the item and select '''Duplicate'''.
*4. A window will popup, ignore all fields except resource name.
*5. Name your item in the resource name field (only letters, numbers and '_').
*6. In the main tab you will see your item, modify it to your liking. Editing the item's additional effects is in 'Item properties'.
*7. Once finished: click '''Tools -> save'''.
*8. look above at the tab's title, it should be '''custom_resource_name.uti''' (with your selected name).
*9. Right click on it again and select '''Export -> Export without dependent resources'''.

== Creating a script to summon your item ==

*1. Click on '''File -> new -> Script'''.
*2. A window will popup, ignore all fields except resource name.
*3. Enter a custom name, '''aa_give_item''' (only letters, numbers and '_'), click Ok.
*4. Copy the following to the blank script window:
<dascript>
void main() {
CreateItemOnObject(R"Item file.uti", OBJECT_SELF, 1, "", TRUE);
}
</dascript>
*5. Replace '''Item file.uti''' with your '''custom_resource_name.uti''' (the title on your item's tab).
*6. Click '''File -> save''' (saving automatically compiles the script).
'''Notice:''' If you make more than one item you can duplicate the script line for each item with it's file name. No need for a script for every item.

== Last Steps ==
*1. Goto folder: My Documents\BioWare\Dragon Age\AddIns\my_module\core\override\toolsetexport.
*2. look for the '''custom_resource_name.uti''' file.
*3. Goto folder: My Documents\BioWare\Dragon Age\AddIns\my_module\module\override\toolsetexport.
*4. look for two files named '''aa_give_item''', of types '''nss''' and '''ncs'''.
*5. Move the '''uti''' and '''ncs''' to folder: My Documents\BioWare\Dragon Age\packages\core\override.
*6. Delete the '''nss''' file.
*7. Load a saved game and enter a console command '''runscript aa_give_item''' ([http://dragonage.wikia.com/wiki/Console Instructions on accessing console]).
*8. Your custom item should be in your inventory. Enjoy.

[[Category:Tutorials]]

Reskinning an item tutorial

2010-01-19T16:11:33Z

Apolyon6k: /* Overriding the Existing Textures */

__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. Not explained here.

== 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". 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

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

Template:Dashedborder

2010-01-19T13:44:21Z

Apolyon6k:

<div class="dascript" style="font-family:monospace; background-color:#F9F9F9; border: 1px dashed #2F6FAB; line-height: 1.1em; padding: 1em; width: 95%;">{{{1|}}}</div><noinclude>

Usage:<nowiki>{{dashedborder|text to put a border around}}</nowiki>

[[Category:Formatting templates]]</noinclude>

Template:Dashedborder

2010-01-19T13:43:59Z

Apolyon6k:

<div class="dascript" style="font-family:monospace; background-color:#F9F9F9; border: 1px dashed #2F6FAB; line-height: 1.1em; padding: 1em; width: 90%;">{{{1|}}}</div><noinclude>

Usage:<nowiki>{{dashedborder|text to put a border around}}</nowiki>

[[Category:Formatting templates]]</noinclude>

Template:Dashedborder

2010-01-19T13:43:40Z

Apolyon6k:

<div class="dascript" style="font-family:monospace; background-color:#F9F9F9; border: 1px dashed #2F6FAB; line-height: 1.1em; padding: 1em; width: 100%;">{{{1|}}}</div><noinclude>

Usage:<nowiki>{{dashedborder|text to put a border around}}</nowiki>

[[Category:Formatting templates]]</noinclude>

Follower tutorial

2010-01-19T13:32:17Z

Apolyon6k: /* Include Function In Your Hire Script and Call It */

== Simple Follower Creation ==

Follow these steps to create a follower that

- Levels up with a default package

- Can be chosen from the party picker

- Can gain XP

This guide assumes you know how to create a creature and are comfortable with basic scripting.

You should only use this simple method if you are sure there will be empty space in the active party when your follower is recruited.

=== Create the creature ===

Create a creature to act as your follower. Set its name, appearance, gender, head morph, conversation, inventory etc as you want them to behave in-game.

Set an appropriate '''Tag''' (you'll be using it a lot). I suggest "party_charname".

Make sure you choose a '''Class'''. For most followers this should be Rogue, Warrior or Wizard.

[[File:class.jpg]]

Under Package/Scaling set:

'''General Package Type''' to be '''Party Members'''

'''Package''' to be an appropriate value (probably "Generic - Wizard" or similar)

'''Package AI''' (there should only be one choice)

'''Rank''' to be '''Player'''

[[File:package.jpg]]

Save and export your character as normal.

=== Override char_stage ===

In your resource palette, open char_stage under the Global folder (you will probably need to right-click it and select "Check Out" first):

[[File:area_palette.jpg]]

Create a new waypoint for your follower to appear on the party picker. This waypoint '''must''' have a tag in the form of "char_" followed by the exact tag of your follower.

[[File:char_stage.jpg]]

In this example the tag of my follower is '''bc_party_miera''' so her waypoint tag must be '''char_bc_party_miera'''

For a standalone module (such as in this example), put your waypoint wherever you please. The illustrated one is directly on top of Morrigan's. For an add-in to the main campaign, you should position your wp appropriately relative to the core party members.

Save and export the area.

Move the '''char_stage.are''' and '''char_stage.lst''' files from your core export folder to your module's export folder (probably from \Documents\Bioware\Dragon Age\packages\core\override\toolsetexport to \Documents\Bioware\Dragon Age\AddIns\yourModule\module\override\toolsetoverride). This ensures that the modification to the character stage only takes effect if your module is installed and enabled, which will help manage compatibility problems. Make sure those files are included when you package your module for distribution.

=== Create m2DAs for the Party Picker ===

You will need to create two Excel spreadsheets.

The first should be named (both worksheet and file) '''partypicker_''' with a unique suffix. In this example, my first spreadsheet is named partypicker_fofbc.xls with a worksheet name of partypicker_fofbc - the suffix being the acronym of my module.

Set up your columns as follows:

[[File:partypickerm2da.jpg]]

The '''ID''' for your follower must be '''12 or higher'''. 11 is the highest value used in the base 2DA. 12 is fine for standalone modules, add-ins will probably want to use an arbitrarily high number to avoid potential conflicts.

The '''Label''' should be the follower's name as you wish it to appear on the party picker.

The '''Tag''' must be your follower's tag.

All other values are non-functioning defaults and should be specified as in the image above unless you know explicitly what you're doing.

'''NOTE - ON SELECTION ANIMATIONS'''

Add Animation and Remove Animation are actually Id numbers of different animations, taken from anim_base.gda

Enter and Exit version of animations are generally the best ones to use, altough one can try others. NOT ALL ANIMATIONS WILL WORK, since some require special conditions.
Here are some examples you can use:

819 - talk cursing

629 - reading a book (doesn't work, since it probably requires a book object)

844 - hands behind back (848 and 849 are Enter and Exit versions respectfully)

850 - chest pounding salute

811 - fist pounding

277 - dance

247 - cast area spell

500 - vfx cast

600 - surprised

603 - praying

607 - head bow

609 - standing at attention

651,652 - crouch pray (Enter and exit)

808 - point forward

825 - nodding

840 - hand chop or frustration

905,906 - crouch (Enter, Exit)

919,920 - sit on ground (enter, exit)

965 - kneel down loop

972 - wipe nose

976,977 - squat (Enter, Exit)

986 - wipe eyes

998,999 - hands clasped (Enter, exit)

3029 - inspect nails

3031,3032 - playful (enter, exit)

3054,3056 - slouch (enter, exit)
255 - in-place fly

'''NOTE - ON SELECTION VFX'''

The VFX column is the ID of the vFX effect taken from vFx_base.gda. This one is a bit more tricky, since it also references the BlendTree value from the same file.
Find the ID of the spell effect and look for the BlendTreeName column (should the the 12th columun) and enter BOTH into the respective columns for your character in the partypicker file.

Some examples:

ID --- BLENDTREENAME --- EFFECT

6039 --- fxm_energy_up_p --- Lady of the Forest pillar of light

6040 --- fxm_power_in_p --- Branka - power in

3054 --- fxc_lotf_c --- Lady of the Forest - swirling leaves

3009 --- fxc_succubus_c --- Succubus crust

1549 --- fxa_hly_imp_c --- Holy Impact crust

1076 --- fxa_spi_aur_mht_c --- Spirit - Aura Might crust

The second spreadsheet should be named '''party_picker_''' (note middle underscore). Once again append your unique suffix (in this example party_picker_fofbc.xls with party_picker_fofbc as its worksheet).

Set up your columns and data like so:

[[File:party_pickerm2da.jpg]]

'''ID''' and '''Tag''' should match what you did in the first spreadsheet. Specify INVALID COLUMN for the third column.

If you're familiar with m2DAs, generate them from these files, copy them to your module's override directory, and skip to the next step. Otherwise, read on:

- Go to '''\Program Files\Dragon Age\tools\ResourceBuild\Processors''' (or wherever you installed Dragon Age)

- Copy '''ExcelProcessor.exe''' from that folder to whichever folder has the excel sheets you just created.

- Drag and drop your xls files onto ExcelProcessor. This will create .gda files.

- Copy these .gda files to your module's export directory (probably \Documents\Bioware\Dragon Age\AddIns\yourModule\module\override\toolsetexport). Make sure they are included in your .dazip when the time comes to build your module.

If you are an OpenOffice user and have trouble with ExcelProcessor, you can use [http://social.bioware.com/project/755/ GDApp] to directly create the 2DAs. It rocks!

=== Capture the EVENT_TYPE_PARTYMEMBER_ADDED Event ===

Amusingly enough, the Party Picker does not actually add followers to the party. However it raises an event that allows you to do so. Your module script needs to capture this event and execute some code.

The following example shows what to do with the event. The full script would work as a module script for an add-in (assuming it didn't need to do anything else), but otherwise you'll have to incorporate the event into your own module script.

If you're not sure how to set a module script, go to '''File''' then '''Manage Modules,''' select your module and click '''Properties.'''

<dascript>
#include "utility_h"

void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch(nEventType)
{
case EVENT_TYPE_PARTYMEMBER_ADDED:
{
object oFollower = GetEventObject(ev, 0);
SetLocalInt(oFollower, CREATURE_REWARD_FLAGS, 0); //Allows the follower to gain XP
AddCommand(oFollower, CommandJumpToLocation(GetLocation(GetHero()))); //Ensures follower appears at PC's location.
SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE); //Adds follower to the active party
break;
}

}
}
</dascript>

'''SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE)''' is the key statement to add the follower to the active party. You must have this.

'''SetLocalInt(oFollower, CREATURE_REWARD_FLAGS, 0)''' is a bug-fix, as followers hired with UT_HireFollower() do not receive XP by default. This statement fixes that, and I consider it best practice to keep it in this event to ensure it is always set. You will not wish to do this if you want a follower that should not gain XP to be on the party picker.

Note that you do not need to intercept the corresponding event for a party member being removed - the party picker handles spawning/despawning, and thus will successfully remove members.

Remember to save and export your module script.

If you're not sure how to set a module script, go to '''File''' then '''Manage Modules,''' select your module and click '''Properties.''' The module script is in the General category, as seen below:

[[File:module_script.jpg]]

You can set this to any script you've created. See [[Scripting tutorial]] and [[Character generation]] for more background and some simple examples of event-handling scripts. In general, you will want to make sure standalone module scripts pass events through to module_core (as in the [[Character generation]] examples) and add-in scripts do not (as in the example above).

=== Create Your Hiring Script ===

Now all that remains is to actually hire the follower :)

Create a script to handle the hiring (which will most likely be fired from a conversation). The script is quite simple:

<dascript>
#include "utility_h"

void main() {

object oFollower = GetObjectByTag("bc_party_miera"); //Use CreateObject() if the creature isn't present in the module yet

UT_HireFollower(oFollower); //Hires the follower

SetPartyPickerGUIStatus(2);

ShowPartyPickerGUI(); //Shows the Party Picker; necessary for the follower to gain XP

}
</dascript>

Make sure you use your own follower's tag and not the example one :)

This script fires the party picker after hiring the follower. That is absolutely necessary via this method, as we have put the XP fix onto an event fired by the party picker. You cannot put the XP fix into this script, it must be called from a later one (the bug is caused by an errant call to an event in player_core, which will be executed AFTER this script).

The easiest way to use this script is directly from conversation, putting it as an action on a line of dialogue where the PC invites the follower to join them. If you're not sure how to associate a script with a dialogue line, see the following image:

[[File:hire_conv.jpg]]

Create your dialogue as normal, select the line you want to fire the script, and click the '''Plots and Scripting''' tab. Use the '''Script''' file chooser in the Action section to browse to the script you created.

If everything worked, you should see something like this:

[[File:picker_success.jpg|thumb|200px|center]]

== Advanced Follower Creation ==

Follow these steps to have full control over the creation of your follower, with options such as:

- Unique level-up template

- Class and specialisation chosen via script

- Any starting state

- Level higher than the PC

- Starts with a specialisation point rather than a specific specialisation

- Set plot flags in the call to the hire script

=== Prepare Creature, char_stage and Party Picker m2DAs ===

Follow the same steps to create your create your follower creature, override char_stage and create your Party Picker m2DAs as above.

=== Create Party Plot ===

While not necessary, it's very helpful to have plot flags set when a follower is hired or joins/leaves the active party. This makes conversation interjections and the like very easy.

Create a plot with appropriate flags. There's no real need to associate journal text with them:

[[File:follower_plot.jpg]]

=== Add Plot Flags to Party Picker Event Intercept ===

We then update our module script to make use of that plot, like so:

<dascript>
#include "utility_h"
#include "wrappers_h"
#include "plt_bc_create_party" //make sure you include your own plot, not mine

void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch(nEventType)
{
case EVENT_TYPE_PARTYMEMBER_ADDED:
{
object oFollower = GetEventObject(ev, 0);
SetLocalInt(oFollower, CREATURE_REWARD_FLAGS, 0);
SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE);

AddCommand(oFollower, CommandJumpToLocation(GetLocation(GetHero()))); //Ensures follower appears at PC's location.

if (GetTag(oFollower) == "bc_party_miera") { //You must explicitly test for your follower's tag.
WR_SetPlotFlag(PLT_BC_CREATE_PARTY, PARTY_MIERA_IN_PARTY, TRUE); //Make sure you use your own flags!
}

break;
}

case EVENT_TYPE_PARTYMEMBER_DROPPED:
{
object oFollower = GetEventObject(ev, 0);

if (GetTag(oFollower) == "bc_party_miera") {
WR_SetPlotFlag(PLT_BC_CREATE_PARTY, PARTY_MIERA_IN_PARTY, FALSE); //As above, but set false.
}

}

}
}
</dascript>

=== Create a Level Up Template ===

You can skip this step if you're content to use one of the generic Rogue, Wizard or Warrior templates, but I don't recommend it. Making a template that suits your character is easy and will almost always be better for the player than a generic one that spends points poorly.

Go to \Program Files\Dragon Age\tools\Source\2DA (or wherever you installed Dragon Age).

You should see a number of excel sheets of the form '''ALCharacter.xls''' (such as ALAlistair.xls, ALLeliana.xls, ALRogue_Default.xls etc). Open the one closest to your character (ie Morrigan or Wynne for a wizard, Leliana or Zevran for a rogue). Save a copy as '''ALYourcharacter.xls''' in whatever directory you're using to create your 2DAs, remembering to rename the worksheet '''ALYourcharacter''' (in this example, ALMiera.xls with ALMiera as its worksheet).

It should look something like this:

[[File:ALtable.jpg|thumb|500px|center]]

'''Columns B''' and '''C''' are the talents/spells available to this character. Do not change them.

'''Columns F''' and '''G''' are the skills available to this character. Do not change them.

We will edit the remaining columns like so:

==== Setting Stat Weights ====

The stat weights in '''column J''' determine how the follower will spend their attribute points, in a rough ratio. So if Dexterity is set to 1.5 and Intelligence to 1, you should expect to see 3 points of Dex for every 2 points of Cunning in-game (note Intelligence is the label used in the toolset for Cunning).

Simply change the values in J to reflect how you'd like the character to spend their points. In this example we're creating a wizard, so we're not going to mess around:

[[File:miera_stat_weights.jpg]]

This character will only raise magic. I set the value to 5 rather than something like 1 to provide room underneath for the other stats while still overwhelmingly favouring magic, but in practice I only really ever want that one stat.

==== Setting Talent and Skill Priorities ====

'''Columns D''' and '''E''' are the talents/spells that the character will buy, in preference order from top to bottom.

'''Columns H''' and '''I''' are the skills that the character will buy, in preference order from top to bottom.

To change these, just copy the appropriate two cells from columns B&C or F&G over the ones you want to replace.

For example, here we're copying Morrigan's template. Morrigan has Spider Shape high in her preferences, which we do not want.

[[File:AlMori_talent_pref.jpg]]

We decide we'd prefer Flame Blast, so we find it in columns B&C and copy both cells:

[[File:ALMori_copy.jpg]]

Then we select the cells we want to replace in columns D&E and paste over them:

[[File:ALMori_paste.jpg]]

Continue this process until your priorities list for both skills and talents/spells is exactly as you want it. Make sure you have at least as many priorities as the core follower you're copying - points that cannot be spent according to these priorities have a habit of vanishing.

If you used any abilities from a specialisation, make sure you remember to set that specialisation with the function we'll introduce later. The autolevel scripts will add specialisation abilities to a character regardless of whether they have that spec or not.

==== Create a M2DA_base_ m2DA ====

Dragon Age will need to know where to find your autolevel template. We tell it by extending M2DA_base.gda

Create a spreadsheet with the name and worksheet name in the form '''M2DA_base_''' with your unique suffix (in this example, M2DA_base_fofbc.xls with M2DA_base_fofbc as a worksheet).

Set up its columns and data like so (note I used GDApp because Open Office wasn't cooperating for this one!):

[[File:m2da_base_fofbc.jpg]]

The '''ID''' should be very high to avoid conflicts. I've arbitrarily chosen 50,000+ here. Carefully note the ID you've chosen for your character, you will need it later.

Set the '''Label''' and '''Worksheet''' to be the name of your autolevel template worksheet (ALCharactername if you've been following this).

Set the '''PackageIDForAI''' to be 0, it shouldn't be needed for followers.

When you're done, use ExcelProcessor to make GDAs of both spreadsheets and copy them to your module's export folder.

FOR AUTOLEVEL TO WORK AFTER RECRUITING:

Look in packages.xls.
There is a column called LevelupTable. That links to a corresponding AL* table. For instance, row 81 is for Leliana. Her LevelupTable value is 258. If you look that up in 2DA_base, you'll see it links to ALLeliana.
(alternatively, you could try packages_base.gda)

=== Create a New Hire Function Include ===

Many vital steps of follower addition happen inside an event in player_core. Followers tend to be extremely buggy (no skill tree, for example) if this event does not fire.

However, that event is not very flexible. In order to control it to our requirements, we need to replicate its functionality inside our own script. This is probably much safer than messing with player_core directly!

Create a new script file, naming it something like '''hireCustomFollower_h'''. We will be including this wherever we want to hire a follower.

Paste in the following script:

<dascript>
#include "sys_chargen_h"
#include "wrappers_h"
#include "utility_h"
#include "sys_rewards_h"
#include "approval_h"
#include "sys_autolevelup_h"

/* Jye Nicolson 5-Jan-2010
This function set duplicates the full functionality chain of UT_HireFollower, with the following exceptions:

- Followers can gain XP
- Autolevel status can be set (default off)
- Followers can be set to any starting state (default Available) and will still be properly initalised and added to the party pool
- Autolevel tables for non-core followers can be explicitly set.
- Class and Specialisation can be chosen via script
- Followers without specialisations are granted a spec point by default.

It should only ever be called once each for characters you intend to be full followers.
Much of the protective code handling summoned creatures etc. in player_core is not present here.

Calling the function:

Simple:

hireCustomFollower(oFollower, CLASS_WARRIOR);

Change the class to CLASS_WIZARD or CLASS_ROGUE as appropriate.
This will hire your follower and make them available.
They will auto level up with a default package, and receive a free spec point.

Best Practice:

hireCustomFollower(oFollower, CLASS_WARRIOR, PLT_YOUR_PARTY_PLOT, YOUR_FOLLOWER_JOINED_FLAG, ABILITY_TALENT_HIDDEN_CHAMPION);

Where the plot and flag are those for your module (remember to create the plot and include it on the calling script), and ABILITY_TALENT_HIDDEN etc is the desired spec.

You should also have a custom ALTable set up.
See wiki for details, and remember to edit it in to GetCustomFollowerALTable below or pass it directly as an argument to hireCustomFollower.

Full argument list:

void hireCustomFollower (
object oFollower, //Pass your follower object, mandatory

int nForceClass, //Pass a Class constant here, usually CLASS_ROGUE, CLASS_WARRIOR, CLASS_WIZARD. Mandatory due to a bug.

string sPlot = "", //It's recommended you have a plot flag to be set when the follower joins. Pass the plot constant here. Remember to #include in calling script

int nPlotFlag = "", //And then pass the flag constant. Will be set to TRUE if available.

int nForceSpec = 0, //This is the ID of the Specialisation you want. Note they are NOT classes, but abilities. The full list is:
//ABILITY_SPELL_HIDDEN_ARCANE_WARRIOR, ABILITY_SPELL_HIDDEN_BLOODMAGE, ABILITY_SPELL_HIDDEN_SHAPESHIFTER, ABILITY_SPELL_HIDDEN_SPIRIT_HEALER
//ABILITY_SPELL_HIDDEN_BARD, ABILITY_TALENT_HIDDEN_ASSASSIN, ABILITY_TALENT_HIDDEN_DUELIST, ABILITY_TALENT_HIDDEN_RANGER
//ABILITY_TALENT_HIDDEN_BERSERKER, ABILITY_TALENT_HIDDEN_CHAMPION, ABILITY_TALENT_HIDDEN_REAVER, ABILITY_TALENT_HIDDEN_TEMPLAR
//I recommended forcing a spec, particularly if your ALTable includes abilities from one.

int nALTable = 0, //This is the ID of an ALTable from 2DA_base.GDA or your module's m2DA_base_*.GDA I recommended the latter, but you can edit that into GetCustomFollowerALTable below rather than passing it.

int bInvokePicker = FALSE, //Sets whether the party picker should be opened on hiring. I think it's cleaner to call the picker outside this script, particularly if you have multiple hires at once.

int nInitialState = FOLLOWER_STATE_AVAILABLE, //This sets whether the follower joins the active party or not. Options are:
//FOLLOWER_STATE_ACTIVE (put them in the active party)
//FOLLOWER_STATE_LOCKEDACTIVE (force them into the active party and keep them there, remember to change this later.
//FOLLOWER_STATE_AVAILABLE (make them available on the party picker (if you've set it up for them), but not in the active party)
//Plus some others you're unlikely to need at this time. Defaults to AVAILABLE because having 4+ active followers is screwy.

string sCurrPlot = "", //If you set FOLLOWER_STATE_ACTIVE or FOLLOWER_STATE_LOCKEDACTIVE, the script will check to see if you passed this.
//It is recommended that you have a plot flag set for a given follower being in the active party, this makes conversation interjection etc. much easier.

int nCurrPlotFlag = 0, //This flag will be set if FOLLOWER_STATE_ACTIVE or FOLLOWER_STATE_LOCKEDACTIVE are true
//AND sCurrPlot has a value AND nCurrPlotFlag is > 0.
//ie if you added someone to the active party and have a plot flag to cope with it.

int nAutolevel = 0, //Sets the Autolevel flag on the character sheet. 0 is off, 1 is on, 2 forces it on and removes it so the player can't turn it off.

bFreeSpecPoint = TRUE, //This grants a specialisation point to the follower if they do not have a specialisation.
//It's important to set this false for classes that do not have specs, such as CLASS_DOG.

int nTargetLevel = 0, //If you want a specific level, set this. Generally not worthwhile unless you set it higher than the player, since they'll just get XP from the party picker anyway.

int nMinLevel = 0 //Set this if there's a specific level you don't want the follower to go below. Probably only useful if the PC might be very low level but not necessarily so.

)
*/
/* GetCustomFollowerALTable()
This function is where you put your custom table assignments.

You should explicitly test for the tag of your follower (not mine!) and assign a value to nTable from your m2DA extension to M2DA_base

See wiki for details on how to do this, or ignore it to get the default Warrior/Rogue/Wizard AL tables.

NOTE: you MUST explicitly set a table for non-Warrior/Rogue/Wizards, eg dogs. Use TABLE_AL_DOG for a default Mabari.
*/

int GetCustomFollowerALTable(object oFollower) {
int nTable = _GetTableToUseForAL(oFollower);

if (GetTag(oFollower) == "bc_party_miera") {
nTable = 50143;
}

if (GetTag(oFollower) == "bc_party_jysavin") {
nTable = 50144;
}

if (GetTag(oFollower) == "bc_party_geldual") {
nTable = 50145;
}

if (GetTag(oFollower) == "bc_party_braghon") {
nTable = 50146;
}

return nTable;
}

// This just cleans up the main function a little

int GetCustomFollowerTargetLevel(object oFollower, object oHero, int nPackage, int nMinLevel = 0) {
int nPlayerLevel = GetLevel(oHero);
int nTargetLevel = 0;

if((nPlayerLevel >= 13) || (nPlayerLevel == 1) || (!_UT_GetIsPlotFollower(oFollower))) {
nTargetLevel = nPlayerLevel;
} else {
nTargetLevel = nPlayerLevel + 1;
}

if (nMinLevel == 0) { //If nMinLevel is not specified, checks package 2DA for a value
nMinLevel = GetM2DAInt(TABLE_PACKAGES, "MinLevel", nPackage);
}
if(nMinLevel > 0 && nMinLevel > nTargetLevel) {
nTargetLevel = nMinLevel;
}

return nTargetLevel;

}

// Moving this black box out :) I don't really understand it, but it should function if you have tactics set up in a package.

void InitCustomFollowerTactics(object oFollower, int nPackage) {
int nTableID = GetM2DAInt(TABLE_PACKAGES, "FollowerTacticsTable", nPackage);
if (nTableID != -1)
{
int nRows = GetM2DARows(nTableID);
int nMaxTactics = GetNumTactics(oFollower);

int nTacticsEntry = 1;
int i;
for (i = 1; i <= nRows && nTacticsEntry <= nMaxTactics; ++i)
{
int bAddEntry = FALSE;
int nTargetType = GetM2DAInt(nTableID, "TargetType", i);
int nCondition = GetM2DAInt(nTableID, "Condition", i);
int nCommandType = GetM2DAInt(nTableID, "Command", i);
int nCommandParam = GetM2DAInt(nTableID, "SubCommand", i);

int nUseType = GetM2DAInt(TABLE_COMMAND_TYPES, "UseType", nCommandType);
if (nUseType == 0)
{
bAddEntry = TRUE;
}
else
{
bAddEntry = HasAbility(oFollower, nCommandParam);
}

if (bAddEntry)
{
SetTacticEntry(oFollower, nTacticsEntry, TRUE, nTargetType, nCondition, nCommandType, nCommandParam);
++nTacticsEntry;
}
}
}
}

/* InitCustomFollowerSpec:

This function tries to set the forced Specialisation. If there is none, it checks the package for one.

If there isn't either of those, it grants a free spec point if bFreeSpecPoint is true.

*/

void InitCustomFollowerSpec(object oFollower, int nPackage, int nForceSpec, int bFreeSpecPoint) {
// Find specialization, and optionally add a spec point if none is found.

if (nForceSpec == 0) {

int nSpecAbility = GetM2DAInt(TABLE_PACKAGES, "switch1_class", nPackage); // followers can have only 1 advanced class
if(nSpecAbility > 0)
{
AddAbility(oFollower, nSpecAbility);
} else {
if (bFreeSpecPoint) {
SetCreatureProperty(oFollower, 38, 1.00);
}
}

} else {

AddAbility(oFollower, nForceSpec);

}
}

/* hireCustomFollower() (See doco at top of page)

I strongly suggest you reorder the parameters if you're adding many followers with advanced options.

Feel free to leave them alone if you only want to set class, plot, spec or don't mind long declarations.

Note nForceClass is currently compulsory due to flakiness with GetCreatureCoreClass()
*/

void hireCustomFollower(object oFollower, int nForceClass, string sPlot = "", int nPlotFlag = 0, int nForceSpec = 0, int nALTable = 0, int bInvokePicker = FALSE, int nInitialState = FOLLOWER_STATE_AVAILABLE, string sCurrPlot = "", int nCurrPlotFlag = 0, int nAutolevel = 0, int bFreeSpecPoint = TRUE, int nTargetLevel = 0, int nMinLevel = 0) {

object oHero = GetHero();

/* ################# BEGIN BASIC FOLLOWER JOIN BLOCK ###################

This loosely replicates WR_SetFollowerState.

*/

if (nForceClass == 0) {
nForceClass = GetCreatureCoreClass(oFollower); //This is not working. Hence nForceClass mandatory.
}

SetGroupId(oFollower, GetGroupId(oHero)); //Puts the follower in the pc's Group.
SetEventScript(oFollower, RESOURCE_SCRIPT_PLAYER_CORE); //This makes them act like a player.
SetFollowerState(oFollower, nInitialState); //This sets whether they are available, in the active party etc.

/* ################# END BASIC FOLLOWER JOIN BLOCK ##################### */

/* ################# BEGIN PLAYER_CORE EVENT_TYPE_PARTY_MEMBER_HIRED EMULATION #################
This replicates the EVENT_TYPE_PARTY_MEMBER_HIRED handler from player_core, stripped down for simplicity and allowing our custom options.

*/

Chargen_EnableTacticsPresets(oFollower); //I assume this is important.

SetLocalInt(oFollower, FOLLOWER_SCALED, 1); //This should prevent the follower being rescaled by player_core or what have you

int nPackage = GetPackage(oFollower); //Gets the package, which will be used to find a number of 2DA IDs.
int nPackageClass = GetM2DAInt(TABLE_PACKAGES, "StartingClass", nPackage); //I don't think this is used, even by player_core

// set behavior according to package
int nBehavior = GetM2DAInt(TABLE_PACKAGES, "FollowerBehavior", nPackage);

if(nBehavior >= 0) {
SetAIBehavior(oFollower, nBehavior);
}

Chargen_InitializeCharacter(oFollower); //We initialise the follower and choose race/class.

Chargen_SelectRace(oFollower,GetCreatureRacialType(oFollower));
Chargen_SelectCoreClass(oFollower,nForceClass);

if (nTargetLevel == 0) { //This block picks a target level if not specified

nTargetLevel = GetCustomFollowerTargetLevel(oFollower, oHero, nPackage, nMinLevel);
}

int nXp = RW_GetXPNeededForLevel(Max(nTargetLevel, 1)); //Here is where the XP is calculated and rewarded
RewardXP(oFollower, nXp, FALSE, FALSE);

// -------------------------------------------------------------
// add hidden approval talents - (JN: I don't know how to set these yet, but when I figure it out this should make it work)
// -------------------------------------------------------------
int nIndex = Approval_GetFollowerIndex(oFollower);
Approval_AddFollowerBonusAbility(nIndex, 0);

//Handle Specialisation
InitCustomFollowerSpec(oFollower, nPackage, nForceSpec, bFreeSpecPoint);

// -------------------------------------------------------------
// This spends all available attribute and stat points on the
// creature according to the levelup table. (JN: this replicates AL_DoAutoLevelUp but with our choice of table)
// -------------------------------------------------------------

if (nALTable == 0) {
nALTable = GetCustomFollowerALTable(oFollower);
}

AL_SpendAttributePoints(oFollower, nALTable, FALSE);
AL_SpendSkillPoints(oFollower, nALTable, TRUE);
AL_SpendSpecializationPoints(oFollower, nALTable);
AL_SpendTalentSpellPoints(oFollower, nALTable, TRUE);

// -------------------------------------------------------------------------
// Update various UIs
// -------------------------------------------------------------------------
Chargen_SetNumTactics(oFollower);
SetCanLevelUp(oFollower,Chargen_HasPointsToSpend(oFollower));

// load tactics
InitCustomFollowerTactics(oFollower, nPackage);

/* ################# END PLAYER_CORE EVENT_TYPE_PARTY_MEMBER_HIRED EMULATION ################# */

SetAutoLevelUp(oFollower, nAutolevel); //This is the autolevel flag on the character sheet.

//Set plot flags

if (!((sPlot == "") || (nPlotFlag == 0))) { //Joined Party
WR_SetPlotFlag(sPlot, nPlotFlag, TRUE);
}

if ((nInitialState == FOLLOWER_STATE_ACTIVE) || (nInitialState == FOLLOWER_STATE_LOCKEDACTIVE)) {
if (!((sCurrPlot == "") || (nCurrPlotFlag == 0))) {
WR_SetPlotFlag(sCurrPlot, nCurrPlotFlag, TRUE); //Currently in Party
}
}

// Invoke picker if requested.

if (bInvokePicker) {
SetPartyPickerGUIStatus(2);
ShowPartyPickerGUI();
}
}
</dascript>

Yeah, I know. It can't really be any smaller. Feel free to modify it if you're confident with scripting.
==== Add Your Custom Autolevel Template to GetCustomFollowerALTable() ====
While you can pass the ID you made for your autolevel template to that monster function as an argument, it's better to have them all in one place if you have multiple followers.

GetCustomFollowerALTable() is the first function in our include, and you can add an explicit if test for your follower there to assign the correct table id (the one from your M2DA_base_ m2DA). There is a function very much like it in sys_autolevel_h.nss for the core followers, so we'll copy Bioware's practice.

Let's take a look at the function by itself:

<dascript>
int GetCustomFollowerALTable(object oFollower) {
int nTable = _GetTableToUseForAL(oFollower);

if (GetTag(oFollower) == "bc_party_miera") {
nTable = 50143;
}

if (GetTag(oFollower) == "bc_party_jysavin") {
nTable = 50144;
}

if (GetTag(oFollower) == "bc_party_geldual") {
nTable = 50145;
}

if (GetTag(oFollower) == "bc_party_braghon") {
nTable = 50146;
}

return nTable;

}
</dascript>

So we have a test for each follower tag from my module, matching up to an ID which is assigned to nTable. All you need to do is change a tag from my follower to yours, and my ID to the correct one from your M2DA_base_* m2DA. Then you should delete the rest of the example if statements :)

Save and export the script. Ignore the compiler error about lack of main();

=== Include Function In Your Hire Script and Call It ===

So instead of a hire script that calls UT_HireFollower(), we want one that includes our shiny new function and calls it.

Take a look at the following example:

<dascript>
#include "plt_bc_create_party" //Make sure you include your party handling plot
#include "hireCustomFollower_h" // And include the function script - which will in turn include a bunch of stuff

void main() {

//Initialising my objects, not super-relevant to the example

object oHero = GetHero();
object oMiera = CreateObject(OBJECT_TYPE_CREATURE, R"bc_party_miera.utc", GetLocation(oHero));
object oJysavin = CreateObject(OBJECT_TYPE_CREATURE, R"bc_party_jysavin.utc", GetLocation(oHero));
object oBraghon = CreateObject(OBJECT_TYPE_CREATURE, R"bc_party_braghon.utc", GetLocation(oHero));
object oSpider = CreateObject(OBJECT_TYPE_CREATURE, R"bc_party_geldual.utc", GetLocation(oHero));

//Simplest hire call - adds to the party as a wizard. Class is currently compulsory due to a bug.
hireCustomFollower(oMiera, CLASS_WIZARD);

//Add to the party and set joining plot flags
hireCustomFollower(oJysavin, CLASS_WARRIOR, PLT_BC_CREATE_PARTY, PARTY_JYSAVIN_JOINED);

//Add to the party, set plot flags, force a specialisation
hireCustomFollower(oBraghon, CLASS_ROGUE, PLT_BC_CREATE_PARTY, PARTY_BRAGHON_JOINED, ABILITY_TALENT_HIDDEN_ASSASSIN);

//More complex example - Follower added as a unique class (Dog), not granted a specialisation or spec point.
//Note unique classes must have an ALTable passed here or specified in GetCustomFollowerALTable() or they won't work
hireCustomFollower(oSpider, CLASS_DOG, PLT_BC_CREATE_PARTY, PARTY_GELDUAL_JOINED, 0, 0, FALSE, FOLLOWER_STATE_AVAILABLE, "", 0, 0, FALSE);

//Show the party picker to let the player choose from their new companions!
SetPartyPickerGUIStatus(2);
ShowPartyPickerGUI();
}
</dascript>

The example shows several of the more simple ways of invoking the function. Check the comments at the start of the function for a full list of arguments.

I would suggest best practice for most followers would be to call as follows:

'''hireCustomFollower(oFollower, CLASS, PLOT, PLOT_FLAG, SPECIALISATION)'''

This will safely set the follower up as the desired class and specialisation (doubly important if there are spec abilities in their ALTable) while setting your plot flag for them being in the party. hireCustomFollower(oFollower, CLASS, PLOT, PLOT_FLAG, SPECIALISATION, 0, TRUE) will do the same while invoking the Party Picker automatically.

Note that the specialisations are abilities and not classes - you'll find them as ABILITY_HIDDEN_ constants.

If it's all worked, you should find you can now add followers with a lot more flexibility!

[[File:picker_advanced.jpg|thumb|500px|center]]

== Common Follower Problems & FAQ ==

====Why don't my followers gain XP?====
There is a bug in UT_HireFollower. For now the best/easiest approach to take might be to make a copy of UT_HireFollower in an include file and rename it something like UT_HireFollower_Fixed, then make the following change:
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, TRUE);
to
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, bPreventLevelup);
(Note: Be aware if you use the name UT_HireFollower_Fixed you may end up finding your include file conflicting with someone else who has named it the same in their include.)

Alternately you need to clear a flag in a separate script to the one in which they're hired.

You must use the '''SetLocalInt(oFollower, CREATURE_REWARD_FLAGS, 0);''' statement in a script you can be sure will run soon after your hiring script.

====When I choose followers from the Party Picker, they spawn into the area but do not join.====

You need to intercept the EVENT_TYPE_PARTYMEMBER_ADDED event and set the follower to FOLLOWER_STATE_ACTIVE. See Simple Follower Creation earlier in this document.

====My followers don't have skill trees!====

If a follower hasn't been through an initial chargen/autolevel event (via player_core/sys_autolevel_h) then the skill tree doesn't show. You're probably trying to be clever and get around UT_HireFollower without going all the way (see monster function above ^_^).

====My followers don't have a class====

GetCreatureCoreClass() seems flaky under some conditions. It's best to explicitly set the class yourself; this is why class is currently a mandatory argument to hireCustomFollower()

====Isn't there an easier way to do this?====

Possibly. There is a way of recruiting a follower by setting a plot flag. However I don't understand it, and I expect it still doesn't allow custom autolevel templates, full control over specialisations etc. There's still a fair bit of stuff hardcoded for the core followers, I'm not sure putting a custom follower through the same process as Al, Leli et al will have good results.

[[Category:Tutorials]]