Dragon Age Toolset Wiki - User contributions [en]

EVENT TYPE ATTACK IMPACT

2011-05-01T22:19:40Z

Noob766: A couple of the integers aren't acurate.

{{event
|sourcefile=script.ldf
|when=Exact moment of impact
|from=Engine
|to=Attacking creature or player
|tocategory1=creature
|sortkey=ATTACK_IMPACT
|creatordesc=attacker
|int0name=nHitResult
|int0desc=hit result (hit, miss, critical etc')
|int1name=nEffectId
|int1desc=Effect ID
|object0name=oAttacker
|object0desc=attacker
|object1name=oTarget
|object1desc=target
|location0name=lImpact
|location0desc=position
|location1name=lMissile
|location1desc=orientation
<dascript>
effect eImpactEffect = GetAttackImpactDamageEffect(oAttacker,nEffectId);
object oWeapon = GetEffectObject(eImpactEffect,0);
int nApp = GetAppearanceType(oAttacker);
int nAbility = GetEffectInteger(eImpactEffect,1);
float fDamage = GetEffectFloat(eImpactEffect,0);
int nVfx = GetEffectInteger(eImpactEffect,0);
int nDamageType = GetEffectInteger(eImpactEffect, 2);
</dascript>
}}

An attack has impacted the target. This can be melee (sword hit), ranged (arrow hit) or spell (fireball explodes). Used for applying damage, and handling abilities that function on hit (Berserk etc').

Follower guidelines

2010-11-27T20:34:07Z

Noob766: /* Common Core Resources */

== General Tips for Companion Mods ==
1. Permanent companions should have many dialogue options available. If you do not intend to write extensive dialogue for your companion, please consider making him/her a temporary companion instead.

2. ALWAYS include a way for the player to fire the companion.

3. ALWAYS include an approval bar. Romance is not necessary, but approval is.

4. Your mod should be lore-friendly. Do some research beforehand.

5. Companions should have a unique personality, head morph, and history.

6. Try to make the companion's race, gender, specialization, and skill set different than those of the currently available companions. (Obviously if you plan to use characters already existing in the game, this may be difficult, but for new companions, this is a must.)

7. Dialogue (including that for your companion) should have multiple lines available for the player to choose from. Generally the pathways are good/nice, evil/greedy, and neutral. The different pathways should have different effects on approval, depending on the personality and motivation of the companion.

8. Design your mod with compatibility in mind! (See below)

== Making Your Companion Mod Compatible ==

=== Basic Tips ===
1. Incorporate the changes other mods make to the common core resources into your mod.

2. Minimize the number of core resources you have to overwrite.

3. Use the same naming scheme as Bioware, except add a unique prefix or suffix.

4. Make sure your char_stage and partypicker 2das include the companion tags listed below.

5. Make sure that the common core dialogues (listed below) contain the additional lines for the other companion mods (also listed below).

6. Do not place your companion in any of the occupied locations listed below.

7. Add your information to this page!

=== Common Core Resources ===
Most companion mods must overwrite or overlay certain core files. A list of these commonly altered files is below:

- cutscene_slideshow.dlg (Ser Gilmore, Karma's Companions, ... add lines to these dialogues)

- party_events.dlg (Ser Gilmore, Karma's Companions, ... add lines to these dialogues)

- cir300_sloth_demon.dlg

- urn230_guardian.dlg

- char_stage.are (or xxx_char_stage.are)

The partypicker.gda's are not overwritten but extended.
- partypicker.gda (or partypicker_xxx.gda) [included only so that stature and animations can be altered]

- party_picker.gda (or party_picker_xxx.gda) [included only so that stature and animations can be altered]

- there are others that are less commonly overwritten!

At some point, the [http://social.bioware.com/group/935/ Custom class and Companion Core Group] will upload a Builder-to-Builder package containing the up-to-date [http://social.bioware.com/project/3137/ Common Core Resources] listed above. If you alter any of these files, please send them a Builder-to-Builder package of any core resources you alter so that they can update the package.

=== Companion Compatibility Core Package ===

'''COMPANION COMPATIBILITY CORE V1.03
BY NOOB766'''

This package is intended to use by all NPC modders in order compatibilize their mods by suppressing the edition of the file “party_events.dlg”.

DOWNLOAD [http://social.bioware.com/project/789/#files HERE]. (package and manual).

====The problem:====
Many NPC modders have the need to modify party_events.dlg in order to allow their NPCs to talk at the gates.

The objective:
* To suppress the edition of party_events.dlg.
* Modders should create a separate dlg containing their NPC’s dialogs.
* Those separate dlg’s will trigger at the gates (one after the other, after party_events.dlg.)

====Things required:====
* Toolset.
* Excel.
* ExcelProcessor (in the “tools” directory in the Dragon Age folder.)

====Contents:====
This package is distributed as a dazip for easy installation. The contents of the dazip are as follows:
* cc_climax_denerim_gates.ncs
* cc_climax_end_cust_dialog.ncs
* cc_constants_h.nss
* cc_denerim_climax.dlg
* cc_climax.GDA
* cc_denerim_climax_2.dlg
* cc_event_handler.ncs
* cc_party_events.dlg
* cc_script_end_dialog.ncs
* clipt_main.ncs
* M2DA_base_cc.GDA

====Procedure:====

Either install the .dazip or place the contents of the "source" folder in your packages/core/override folder. These are the handling scripts and all the core files.

* Create your own ''''cc_climax_YOURMOD.GDA''''

Where "ID" is your unique ID number; "TagOfSpeaker" is your NPC's tag and "DialogResource" is the climax dialog you create for your NPC.
Important!!!!! The ID number has to be between 1 and 5000!!

=====Used numbers:=====
* Ser Gilmore NPC - 1981
* Reserved by ladydesire for Lealion/Tevinter Wardens - 2001-2006

[[image:49013081.jpg]]

* Create your own '''cc_climax_YOURMOD.dlg'''

Set the line to "show only once per game":

[[image:Screendlg1.jpg]]

[[image:42673137.jpg]]

Create the script cc_climax_end_cust_dialog.nss that we need to link at the end of your custom dialog (as explained above). DO NOT EXPORT. (It's already included in the compatibility core).

#include "utility_h"
void main()
{
object oHero = GetHero();
event eDialog = Event(EVENT_TYPE_CUSTOM_EVENT_01);
DelayEvent(0.1f,oHero,eDialog,"cc_event_handler");
}

Place your GDA in your mod's core override, and export your custom dlg. Nothing else is required (because it's included in the companion compatibility core package).

====The result:====
Once the vanilla NPCs have their final dialogs at the gates, all the custom NPCs dialogs will trigger, one after the other.

====Important notes:====

* DO NOT touch or export party_events! It's not needed any more.
* DO NOT export cc_climax_end_cust_dialog.nss that you created to link at the end of your custom climax dialog. It's not needed.
* Always remember to add cc_climax_end_cust_dialog.nss at the end of your climax dialog!
* Make sure cc_climax_end_cust_dialog fires OUTSIDE of a conditional branch to ensure the next dialog gets read even if your companion isn't recruited.
* The ONLY things required from you (modder) is your GDA and your custom dlg. Simple!
* Distribute the .dazip to the players.

=== Companion Names, Races, & Tags ===

{| border="1" cellspacing="0" cellpadding="3"
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1617 Karma's Companions]:
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Cullen
| Human
| kc_cir230cr_cullen
|-
| Jowan
| Human
| kc_arl210cr_jowan
|-
| Gorim
| Dwarf
| kc_bdn120cr_gorim
|-
| Ser Gilmore
| Human
| kc_bhn100cr_gilmore
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=851 Ser Gilmore recruitable NPC]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Ser Roland Gilmore
| Human
| ser_gilmore_lbc
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1690 Lady Desire's Tevinter Wardens]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Lealion
| Human
| gen00fl_lealion
|-
| Legion
| Dog
| gen00fl_legion
|-
| Lanna
| Human
| gen00fl_lanna
|-
| Marric
| Elf
| gen00fl_marric
|-
| Martin
| Human
| gen00fl_martin
|-
| Willam
| Human
| gen00fl_willam
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1716 Cena's Qunari Companions]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Saarebas
| Qunari
| gen00fl_saarebas
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1432 Return to Korcari Wilds]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Douglas
| Human
| party_douglas
|-
| Ser Kenneth
| Human
| party_serken
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1397 The Bloodworks]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Chris
| Human
| chrischar
|-
| Lucius
| Human
| luciuschar
|-
!colspan="3"|
|-
!colspan="3"| [http://social.bioware.com/project/2157/ Dark Times: The Confederacy of Malkuth]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Lethe
| Humanoid
| dt_fol_lethe_demon
|-
| Lethe
| Human
| dt_fol_lethe_human
|-
| Thazulok
| Elf
| dt_fol_thazulok
|-
| Myrdo
| Human
| dt_fol_myrdo
|-
| Fetch
| Dwarf
| dt_fol_fetch
|-
| Marukhan
| Werewolf
| dt_fol_marukhan
|-
| Dragon
| Dragonling
| dt_fol_dragon_i
|-
!colspan="3"|
|-
!colspan="3"| [http://social.bioware.com/project/3152/ Valeria Addon]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Valeria
| Human
| valeria_npc
|-
|}

=== Occupied Locations ===
==== Party Camp ====

'''Karma's Companions:'''
:Cullen's position: 138.564f, 111.815f, -1.08586f
:Jowan's position: 174.687f, 147.589f, -1.33659f
:Gorim's position: 144.049f, 146.718f, -0.97327f
:Gilmore's position: 125.402f, 116.783f, -0.924384f

'''Karma's Bloodworks Compatibility Plugin:'''
:Lucius' and Chris' position: 167.154f, 139.113f, -1.54743f

'''Cena's Qunari Companions:'''
:Saarebas's position: 135.252625, 118.686562, -0.274021

'''Return to Korcari Wilds:'''
:Douglas' position: 134.41, 113.905, -0.552629
:Ser Kenneth's position: 137.62, 133.833, 0.629564

'''Lady Desire's Lealion the Mage:'''
:Lealion's position: 135.252625f, 113.905f, -0.274021f
:Legion's position: 135.252625f, 113.905f, -0.274021f
:(Please note that they stand next to each other, sharing a common reference point.)

==== Denerim Castle ====

'''Karma's Companions:'''
:Cullen's position: 138.564f, 111.815f, -1.08586f
:Jowan's position: 174.687f, 147.589f, -1.33659f
:Gorim's position: 144.049f, 146.718f, -0.97327f
:Gilmore's position: 125.402f, 116.783f, -0.924384f

==== Redcliffe Castle ====

'''Karma's Companions:'''
:Cullen's position: 9.62579f, -17.3753f, 0.022839f
:Jowan's position: 7.59896f, -5.17459f, 0.022839f
:Gorim's position: 26.3124f, -8.75641f, 0.022839f
:Gilmore's position: 20.797f, -14.1758f, 0.022839f

==== Post-Coronation ====

'''Karma's Companions:'''
:Cullen's position: 15.0103f, 4.66715f, 0.022839f
:Jowan's position: -1.93367f, -3.92452f, 0.022839f
:Gorim's position: 12.3308f, -5.61697f, 0.022839f
:Gilmore's position: 16.5714f, -4.42749f, 0.022839f

Follower guidelines

2010-11-27T19:39:21Z

Noob766: /* Companion Names, Races, & Tags */

== General Tips for Companion Mods ==
1. Permanent companions should have many dialogue options available. If you do not intend to write extensive dialogue for your companion, please consider making him/her a temporary companion instead.

2. ALWAYS include a way for the player to fire the companion.

3. ALWAYS include an approval bar. Romance is not necessary, but approval is.

4. Your mod should be lore-friendly. Do some research beforehand.

5. Companions should have a unique personality, head morph, and history.

6. Try to make the companion's race, gender, specialization, and skill set different than those of the currently available companions. (Obviously if you plan to use characters already existing in the game, this may be difficult, but for new companions, this is a must.)

7. Dialogue (including that for your companion) should have multiple lines available for the player to choose from. Generally the pathways are good/nice, evil/greedy, and neutral. The different pathways should have different effects on approval, depending on the personality and motivation of the companion.

8. Design your mod with compatibility in mind! (See below)

== Making Your Companion Mod Compatible ==

=== Basic Tips ===
1. Incorporate the changes other mods make to the common core resources into your mod.

2. Minimize the number of core resources you have to overwrite.

3. Use the same naming scheme as Bioware, except add a unique prefix or suffix.

4. Make sure your char_stage and partypicker 2das include the companion tags listed below.

5. Make sure that the common core dialogues (listed below) contain the additional lines for the other companion mods (also listed below).

6. Do not place your companion in any of the occupied locations listed below.

7. Add your information to this page!

=== Common Core Resources ===
Most companion mods must overwrite or overlay certain core files. A list of these commonly altered files is below:

- cutscene_slideshow.dlg (Ser Gilmore, Karma's Companions, ... add lines to these dialogues)

- party_events.dlg (Ser Gilmore, Karma's Companions, ... add lines to these dialogues)

- cir300_sloth_demon.dlg

- urn230_guardian.dlg

- char_stage.are (or xxx_char_stage.are)

- partypicker.gda (or partypicker_xxx.gda) [included only so that stature and animations can be altered]

- party_picker.gda (or party_picker_xxx.gda) [included only so that stature and animations can be altered]

- there are others that are less commonly overwritten!

At some point, the [http://social.bioware.com/group/935/ Custom class and Companion Core Group] will upload a Builder-to-Builder package containing the up-to-date [http://social.bioware.com/project/3137/ Common Core Resources] listed above. If you alter any of these files, please send them a Builder-to-Builder package of any core resources you alter so that they can update the package.

=== Companion Compatibility Core Package ===

'''COMPANION COMPATIBILITY CORE V1.03
BY NOOB766'''

This package is intended to use by all NPC modders in order compatibilize their mods by suppressing the edition of the file “party_events.dlg”.

DOWNLOAD [http://social.bioware.com/project/789/#files HERE]. (package and manual).

====The problem:====
Many NPC modders have the need to modify party_events.dlg in order to allow their NPCs to talk at the gates.

The objective:
* To suppress the edition of party_events.dlg.
* Modders should create a separate dlg containing their NPC’s dialogs.
* Those separate dlg’s will trigger at the gates (one after the other, after party_events.dlg.)

====Things required:====
* Toolset.
* Excel.
* ExcelProcessor (in the “tools” directory in the Dragon Age folder.)

====Contents:====
This package is distributed as a dazip for easy installation. The contents of the dazip are as follows:
* cc_climax_denerim_gates.ncs
* cc_climax_end_cust_dialog.ncs
* cc_constants_h.nss
* cc_denerim_climax.dlg
* cc_climax.GDA
* cc_denerim_climax_2.dlg
* cc_event_handler.ncs
* cc_party_events.dlg
* cc_script_end_dialog.ncs
* clipt_main.ncs
* M2DA_base_cc.GDA

====Procedure:====

Either install the .dazip or place the contents of the "source" folder in your packages/core/override folder. These are the handling scripts and all the core files.

* Create your own ''''cc_climax_YOURMOD.GDA''''

Where "ID" is your unique ID number; "TagOfSpeaker" is your NPC's tag and "DialogResource" is the climax dialog you create for your NPC.
Important!!!!! The ID number has to be between 1 and 5000!!

=====Used numbers:=====
* Ser Gilmore NPC - 1981
* Reserved by ladydesire for Lealion/Tevinter Wardens - 2001-2006

[[image:49013081.jpg]]

* Create your own '''cc_climax_YOURMOD.dlg'''

Set the line to "show only once per game":

[[image:Screendlg1.jpg]]

[[image:42673137.jpg]]

Create the script cc_climax_end_cust_dialog.nss that we need to link at the end of your custom dialog (as explained above). DO NOT EXPORT. (It's already included in the compatibility core).

#include "utility_h"
void main()
{
object oHero = GetHero();
event eDialog = Event(EVENT_TYPE_CUSTOM_EVENT_01);
DelayEvent(0.1f,oHero,eDialog,"cc_event_handler");
}

Place your GDA in your mod's core override, and export your custom dlg. Nothing else is required (because it's included in the companion compatibility core package).

====The result:====
Once the vanilla NPCs have their final dialogs at the gates, all the custom NPCs dialogs will trigger, one after the other.

====Important notes:====

* DO NOT touch or export party_events! It's not needed any more.
* DO NOT export cc_climax_end_cust_dialog.nss that you created to link at the end of your custom climax dialog. It's not needed.
* Always remember to add cc_climax_end_cust_dialog.nss at the end of your climax dialog!
* Make sure cc_climax_end_cust_dialog fires OUTSIDE of a conditional branch to ensure the next dialog gets read even if your companion isn't recruited.
* The ONLY things required from you (modder) is your GDA and your custom dlg. Simple!
* Distribute the .dazip to the players.

=== Companion Names, Races, & Tags ===

{| border="1" cellspacing="0" cellpadding="3"
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1617 Karma's Companions]:
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Cullen
| Human
| kc_cir230cr_cullen
|-
| Jowan
| Human
| kc_arl210cr_jowan
|-
| Gorim
| Dwarf
| kc_bdn120cr_gorim
|-
| Ser Gilmore
| Human
| kc_bhn100cr_gilmore
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=851 Ser Gilmore recruitable NPC]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Ser Roland Gilmore
| Human
| ser_gilmore_lbc
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1690 Lady Desire's Tevinter Wardens]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Lealion
| Human
| gen00fl_lealion
|-
| Legion
| Dog
| gen00fl_legion
|-
| Lanna
| Human
| gen00fl_lanna
|-
| Marric
| Elf
| gen00fl_marric
|-
| Martin
| Human
| gen00fl_martin
|-
| Willam
| Human
| gen00fl_willam
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1716 Cena's Qunari Companions]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Saarebas
| Qunari
| gen00fl_saarebas
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1432 Return to Korcari Wilds]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Douglas
| Human
| party_douglas
|-
| Ser Kenneth
| Human
| party_serken
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1397 The Bloodworks]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Chris
| Human
| chrischar
|-
| Lucius
| Human
| luciuschar
|-
!colspan="3"|
|-
!colspan="3"| [http://social.bioware.com/project/2157/ Dark Times: The Confederacy of Malkuth]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Lethe
| Humanoid
| dt_fol_lethe_demon
|-
| Lethe
| Human
| dt_fol_lethe_human
|-
| Thazulok
| Elf
| dt_fol_thazulok
|-
| Myrdo
| Human
| dt_fol_myrdo
|-
| Fetch
| Dwarf
| dt_fol_fetch
|-
| Marukhan
| Werewolf
| dt_fol_marukhan
|-
| Dragon
| Dragonling
| dt_fol_dragon_i
|-
!colspan="3"|
|-
!colspan="3"| [http://social.bioware.com/project/3152/ Valeria Addon]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Valeria
| Human
| valeria_npc
|-
|}

=== Occupied Locations ===
==== Party Camp ====

'''Karma's Companions:'''
:Cullen's position: 138.564f, 111.815f, -1.08586f
:Jowan's position: 174.687f, 147.589f, -1.33659f
:Gorim's position: 144.049f, 146.718f, -0.97327f
:Gilmore's position: 125.402f, 116.783f, -0.924384f

'''Karma's Bloodworks Compatibility Plugin:'''
:Lucius' and Chris' position: 167.154f, 139.113f, -1.54743f

'''Cena's Qunari Companions:'''
:Saarebas's position: 135.252625, 118.686562, -0.274021

'''Return to Korcari Wilds:'''
:Douglas' position: 134.41, 113.905, -0.552629
:Ser Kenneth's position: 137.62, 133.833, 0.629564

'''Lady Desire's Lealion the Mage:'''
:Lealion's position: 135.252625f, 113.905f, -0.274021f
:Legion's position: 135.252625f, 113.905f, -0.274021f
:(Please note that they stand next to each other, sharing a common reference point.)

==== Denerim Castle ====

'''Karma's Companions:'''
:Cullen's position: 138.564f, 111.815f, -1.08586f
:Jowan's position: 174.687f, 147.589f, -1.33659f
:Gorim's position: 144.049f, 146.718f, -0.97327f
:Gilmore's position: 125.402f, 116.783f, -0.924384f

==== Redcliffe Castle ====

'''Karma's Companions:'''
:Cullen's position: 9.62579f, -17.3753f, 0.022839f
:Jowan's position: 7.59896f, -5.17459f, 0.022839f
:Gorim's position: 26.3124f, -8.75641f, 0.022839f
:Gilmore's position: 20.797f, -14.1758f, 0.022839f

==== Post-Coronation ====

'''Karma's Companions:'''
:Cullen's position: 15.0103f, 4.66715f, 0.022839f
:Jowan's position: -1.93367f, -3.92452f, 0.022839f
:Gorim's position: 12.3308f, -5.61697f, 0.022839f
:Gilmore's position: 16.5714f, -4.42749f, 0.022839f

Follower guidelines

2010-11-27T18:46:20Z

Noob766: /* Important notes: */

== General Tips for Companion Mods ==
1. Permanent companions should have many dialogue options available. If you do not intend to write extensive dialogue for your companion, please consider making him/her a temporary companion instead.

2. ALWAYS include a way for the player to fire the companion.

3. ALWAYS include an approval bar. Romance is not necessary, but approval is.

4. Your mod should be lore-friendly. Do some research beforehand.

5. Companions should have a unique personality, head morph, and history.

6. Try to make the companion's race, gender, specialization, and skill set different than those of the currently available companions. (Obviously if you plan to use characters already existing in the game, this may be difficult, but for new companions, this is a must.)

7. Dialogue (including that for your companion) should have multiple lines available for the player to choose from. Generally the pathways are good/nice, evil/greedy, and neutral. The different pathways should have different effects on approval, depending on the personality and motivation of the companion.

8. Design your mod with compatibility in mind! (See below)

== Making Your Companion Mod Compatible ==

=== Basic Tips ===
1. Incorporate the changes other mods make to the common core resources into your mod.

2. Minimize the number of core resources you have to overwrite.

3. Use the same naming scheme as Bioware, except add a unique prefix or suffix.

4. Make sure your char_stage and partypicker 2das include the companion tags listed below.

5. Make sure that the common core dialogues (listed below) contain the additional lines for the other companion mods (also listed below).

6. Do not place your companion in any of the occupied locations listed below.

7. Add your information to this page!

=== Common Core Resources ===
Most companion mods must overwrite or overlay certain core files. A list of these commonly altered files is below:

- cutscene_slideshow.dlg (Ser Gilmore, Karma's Companions, ... add lines to these dialogues)

- party_events.dlg (Ser Gilmore, Karma's Companions, ... add lines to these dialogues)

- cir300_sloth_demon.dlg

- urn230_guardian.dlg

- char_stage.are (or xxx_char_stage.are)

- partypicker.gda (or partypicker_xxx.gda) [included only so that stature and animations can be altered]

- party_picker.gda (or party_picker_xxx.gda) [included only so that stature and animations can be altered]

- there are others that are less commonly overwritten!

At some point, the [http://social.bioware.com/group/935/ Custom class and Companion Core Group] will upload a Builder-to-Builder package containing the up-to-date [http://social.bioware.com/project/3137/ Common Core Resources] listed above. If you alter any of these files, please send them a Builder-to-Builder package of any core resources you alter so that they can update the package.

=== Companion Compatibility Core Package ===

'''COMPANION COMPATIBILITY CORE V1.03
BY NOOB766'''

This package is intended to use by all NPC modders in order compatibilize their mods by suppressing the edition of the file “party_events.dlg”.

DOWNLOAD [http://social.bioware.com/project/789/#files HERE]. (package and manual).

====The problem:====
Many NPC modders have the need to modify party_events.dlg in order to allow their NPCs to talk at the gates.

The objective:
* To suppress the edition of party_events.dlg.
* Modders should create a separate dlg containing their NPC’s dialogs.
* Those separate dlg’s will trigger at the gates (one after the other, after party_events.dlg.)

====Things required:====
* Toolset.
* Excel.
* ExcelProcessor (in the “tools” directory in the Dragon Age folder.)

====Contents:====
This package is distributed as a dazip for easy installation. The contents of the dazip are as follows:
* cc_climax_denerim_gates.ncs
* cc_climax_end_cust_dialog.ncs
* cc_constants_h.nss
* cc_denerim_climax.dlg
* cc_climax.GDA
* cc_denerim_climax_2.dlg
* cc_event_handler.ncs
* cc_party_events.dlg
* cc_script_end_dialog.ncs
* clipt_main.ncs
* M2DA_base_cc.GDA

====Procedure:====

Either install the .dazip or place the contents of the "source" folder in your packages/core/override folder. These are the handling scripts and all the core files.

* Create your own ''''cc_climax_YOURMOD.GDA''''

Where "ID" is your unique ID number; "TagOfSpeaker" is your NPC's tag and "DialogResource" is the climax dialog you create for your NPC.
Important!!!!! The ID number has to be between 1 and 5000!!

=====Used numbers:=====
* Ser Gilmore NPC - 1981
* Reserved by ladydesire for Lealion/Tevinter Wardens - 2001-2006

[[image:49013081.jpg]]

* Create your own '''cc_climax_YOURMOD.dlg'''

Set the line to "show only once per game":

[[image:Screendlg1.jpg]]

[[image:42673137.jpg]]

Create the script cc_climax_end_cust_dialog.nss that we need to link at the end of your custom dialog (as explained above). DO NOT EXPORT. (It's already included in the compatibility core).

#include "utility_h"
void main()
{
object oHero = GetHero();
event eDialog = Event(EVENT_TYPE_CUSTOM_EVENT_01);
DelayEvent(0.1f,oHero,eDialog,"cc_event_handler");
}

Place your GDA in your mod's core override, and export your custom dlg. Nothing else is required (because it's included in the companion compatibility core package).

====The result:====
Once the vanilla NPCs have their final dialogs at the gates, all the custom NPCs dialogs will trigger, one after the other.

====Important notes:====

* DO NOT touch or export party_events! It's not needed any more.
* DO NOT export cc_climax_end_cust_dialog.nss that you created to link at the end of your custom climax dialog. It's not needed.
* Always remember to add cc_climax_end_cust_dialog.nss at the end of your climax dialog!
* Make sure cc_climax_end_cust_dialog fires OUTSIDE of a conditional branch to ensure the next dialog gets read even if your companion isn't recruited.
* The ONLY things required from you (modder) is your GDA and your custom dlg. Simple!
* Distribute the .dazip to the players.

=== Companion Names, Races, & Tags ===

{| border="1" cellspacing="0" cellpadding="3"
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1617 Karma's Companions]:
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Cullen
| Human
| kc_cir230cr_cullen
|-
| Jowan
| Human
| kc_arl210cr_jowan
|-
| Gorim
| Dwarf
| kc_bdn120cr_gorim
|-
| Ser Gilmore
| Human
| kc_bhn100cr_gilmore
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=851 Ser Gilmore recruitable NPC]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Ser Roland Gilmore
| Human
| ser_gilmore_lbc
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1690 Lady Desire's Tevinter Wardens]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Lealion
| Human
| gen00fl_lealion
|-
| Legion
| Dog
| gen00fl_legion
|-
| Lanna
| Human
| gen00fl_lanna
|-
| Marric
| Elf
| gen00fl_marric
|-
| Martin
| Human
| gen00fl_martin
|-
| Willam
| Human
| gen00fl_willam
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1716 Cena's Qunari Companions]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Saarebas
| Qunari
| gen00fl_saarebas
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1432 Return to Korcari Wilds]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Douglas
| Human
| party_douglas
|-
| Ser Kenneth
| Human
| party_serken
|-
!colspan="3"|
|-
!colspan="3"| [http://dragonagenexus.com/downloads/file.php?id=1397 The Bloodworks]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Chris
| Human
| chrischar
|-
| Lucius
| Human
| luciuschar
|-
!colspan="3"|
|-
!colspan="3"| Dark Times: The Confederacy of Malkuth
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Lethe
| Humanoid
| dt_fol_lethe_demon
|-
| Lethe
| Human
| dt_fol_lethe_human
|-
| Thazulok
| Elf
| dt_fol_thazulok
|-
| Myrdo
| Human
| dt_fol_myrdo
|-
| Fetch
| Dwarf
| dt_fol_fetch
|-
| Marukhan
| Werewolf
| dt_fol_marukhan
|-
| Dragon
| Dragonling
| dt_fol_dragon_i
|-
!colspan="3"|
|-
!colspan="3"| [http://social.bioware.com/project/3152/ Valeria Addon]
|-
!scope="col"| Name
!scope="col"| Race
!scope="col"| Tag
|-
| Valeria
| Human
| valeria_npc
|-
|}

=== Occupied Locations ===
==== Party Camp ====

'''Karma's Companions:'''
:Cullen's position: 138.564f, 111.815f, -1.08586f
:Jowan's position: 174.687f, 147.589f, -1.33659f
:Gorim's position: 144.049f, 146.718f, -0.97327f
:Gilmore's position: 125.402f, 116.783f, -0.924384f

'''Karma's Bloodworks Compatibility Plugin:'''
:Lucius' and Chris' position: 167.154f, 139.113f, -1.54743f

'''Cena's Qunari Companions:'''
:Saarebas's position: 135.252625, 118.686562, -0.274021

'''Return to Korcari Wilds:'''
:Douglas' position: 134.41, 113.905, -0.552629
:Ser Kenneth's position: 137.62, 133.833, 0.629564

'''Lady Desire's Lealion the Mage:'''
:Lealion's position: 135.252625f, 113.905f, -0.274021f
:Legion's position: 135.252625f, 113.905f, -0.274021f
:(Please note that they stand next to each other, sharing a common reference point.)

==== Denerim Castle ====

'''Karma's Companions:'''
:Cullen's position: 138.564f, 111.815f, -1.08586f
:Jowan's position: 174.687f, 147.589f, -1.33659f
:Gorim's position: 144.049f, 146.718f, -0.97327f
:Gilmore's position: 125.402f, 116.783f, -0.924384f

==== Redcliffe Castle ====

'''Karma's Companions:'''
:Cullen's position: 9.62579f, -17.3753f, 0.022839f
:Jowan's position: 7.59896f, -5.17459f, 0.022839f
:Gorim's position: 26.3124f, -8.75641f, 0.022839f
:Gilmore's position: 20.797f, -14.1758f, 0.022839f

==== Post-Coronation ====

'''Karma's Companions:'''
:Cullen's position: 15.0103f, 4.66715f, 0.022839f
:Jowan's position: -1.93367f, -3.92452f, 0.022839f
:Gorim's position: 12.3308f, -5.61697f, 0.022839f
:Gilmore's position: 16.5714f, -4.42749f, 0.022839f

Useful Scripts

2010-07-04T13:17:19Z

Noob766: added break to the lootable placeable code

{{Infobox script}}

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that otherwise require deep scripting knowledge to figure out intuitively how to do.

Feel free to add new sections describing any tricks or techniques you think is worth documenting. If the page becomes too large it can be split up into specific topics.

See also: [[PRCSCR Script Templates]]

__TOC__
== Run a cutscene from a trigger ==

Create a script:

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

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int bEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(GetObjectActive(OBJECT_SELF)
&& IsPartyMember(oCreature))
{
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
SetObjectActive(OBJECT_SELF, FALSE);
}
}
break;
}
if (!bEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
<dascript>
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
</dascript>
to the function
<dascript>
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
</dascript>
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). 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:

<dascript>
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, TRUE);
</dascript>
to
<dascript>
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, bPreventLevelup);
</dascript>

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time. '''[To Editor: Edit in a Custom Module or the existing Single Player Campaign Module?]'''

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
// this is the name of a precreated plot file "joblos_quest" prefixed with the special "plt_"
// "plt_" + quest name allows you to reference the flag names as constants.
#include "plt_joblos_quest"
#include "wrappers_h"

void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag(PLT_JOBLOS_QUEST, JOBLO_ADDED_TO_TOWN) == FALSE)
{
object oTown = GetObjectByTag("lot100ar_lothering"); //An area's tag is the same as its resource name
vector vJobloLocation = Vector(126.745f, 120.724f, 0.460568f); // See below for how to get these coordinates

CreateObject(
OBJECT_TYPE_CREATURE,
R"joblo.utc",
Location(oTown, vJobloLocation, 180.0f); //See below for how to get the value for orientation
)

WR_SetPlotFlag("joblos_quest", JOBLO_ADDED_TO_TOWN, TRUE);
}
}
</dascript>

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
break;
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>

== Override Events (e.g. those in player_core) ==

Look here: [[Event override]]

[[category:tutorials]]
[[Category:Scripts]]