Dragon Age Toolset Wiki - User contributions [en]

Attribute

2009-10-30T17:07:41Z

Georg Zoeller:

=== Overview ===

Description of the attributes used by the game from a design perspective, with a focus on information needed by content and gameplay designers, such as how to incorporate attributes with ability, skill and campaign design.

=== Primary Attributes ===

The primary attributes in Dragon Age's rules system are

==== Strength ====

===== Effects =====

==== Dexterity ====

===== Effects =====

==== Cunning ====

===== Effects =====

==== Willpower ====

===== Effects =====

==== Constitution ====

===== Effects =====

==== Magic ====

===== Effects =====

[[Category: Scripts]]
[[Category: Rules]]

Attribute

2009-10-30T17:06:01Z

Georg Zoeller: /* Overview */

=== Overview ===

The creature property system is the heart of the rules engine and defines all the numerical values that make up a character in Dragon Age.

== Overview ==

=== Primary Attributes ===

The primary attributes in Dragon Age's rules system are

==== Strength ====

===== Effects =====

==== Dexterity ====

===== Effects =====

==== Cunning ====

===== Effects =====

==== Willpower ====

===== Effects =====

==== Constitution ====

===== Effects =====

==== Magic ====

===== Effects =====

[[Category: Scripts]]
[[Category: Rules]]

Attribute

2009-10-30T17:05:20Z

Georg Zoeller: /* Detailed Description */

=== Overview ===

The creature property system is the heart of the rules engine and defines all the numerical values that make up a character in Dragon Age.

== Overview ==

=== Primary Attributes ===

The primary attributes in Dragon Age's rules system are

==== Strength ====

===== Effects ======

==== Dexterity ====

===== Effects ======

==== Cunning ====

===== Effects ======

==== Willpower ====

===== Effects ======

==== Constitution ====

===== Effects ======

==== Magic ====

===== Effects ======

[[Category: Scripts]]
[[Category: Rules]]

Attribute

2009-10-30T16:52:59Z

Georg Zoeller: Created page with '=== Overview === The creature property system is the heart of the rules engine and defines all the numerical values that make up a character in Dragon Age. === Detailed Descrip...'

Creature Properties

2009-10-30T16:52:36Z

Georg Zoeller: /* Property Definitions */

=== Overview ===

The creature property system is the heart of the rules engine and defines all the numerical values that make up a character in Dragon Age.

=== Detailed Description ===

Properties are 32-bit floating point values associated with every combat capable creature in the game (Creature Type field in the toolset). They are used by engine, scripting and UI to make up and display the RPG ruleset of the game.

==== Property Types ====

There are 3 types of properties that abstract the most common types of statistics found in an RPG:

===== PROPERTY_TYPE_SIMPLE =====

Simple properties are 32 bit floats that can hold a single value and that generally are not modified or influenced by other properties. Examples include Experience, Level or the number of unspent talent points a character has.

===== PROPERTY_TYPE_ATTRIBUTE =====

[[Attribute]]s are a moderately complex set of values encapsulating a single character stat. They have three fields that are independently tracked in the engine and are accessible from scripting:

* Base - A character's unmodified base value, usually only modified during level up and character creation. This number is displayed as a white number the character sheet.

* Modifier - A float32 that holds the sum of all effect based modifications to the property. This number is shown as a red (if negative) or green (if positive) number on the character sheet.

* Total - The sum of the base and modifier fields along with any in engine modifications done to the property in C++ (for speed reasons) as defined by the engine link field. When reading this field, the engine will always clamp the return values between Min and Max, even through it stores the full, unmodified number internally.

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; height:100%"
|-
|'''Example:'''
A level 1 warrior with 15 strength, a buff that grants +2 strength and a shield that has a +1 strength enhancement would be stored as as:
* Base: 15
* Modifiers: 3
* Total 18
|}

===== PROPERTY_TYPE_DEPLETABLE =====
Depletables represent the most complex type of stats usually found in an RPG, used for Health and Mana. In addition to all fields present on an Attribute, they have an additional 'Current' field.

* Current - This is the character's current value in this stat, which can be between Min and Max and can exceed Total.

Additionally, just like attributes, the EngineLink field defines some hardcoded behavior in the engine such as creating the link between the 'rengeration rate' properties.

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; height:100%"
|-
|'''Example:'''
A level 1 warrior with 14 Con and 100 base health and a +5 health ring would store health who was at full health before getting hit for 20 points of damage:
* Base: 100
* Modifiers: +5
* Hidden Engine Modifiers: +20 (5 points for each point in CON after 10).
* Total: 125
* Current: 105

Hidden Engine modifiers can not be modified (obviously, they're in C++), but can be disabled by setting the EngineLink field to 0. They exist purely to speed up stats accessed with high frequency (DAScript has a 7-15x overhead per instruction compared to native code).
|}

==== Property Definitions ====

The two dimensional data array defined in [[Properties.xls]] defines numerical values that exist on every creature in the game. All properties are float32 and all rules logic of the game is based on with floating point math. This dynamic data driven approach to rules relevant stats is new to Dragon Age: Origins and makes the engine extremely flexible for Designers. It enables the game to have a rules logic that is almost completely softcoded in script and data.

The following is an excerpt from the 2da that lists all rows present in the initial ship version of Dragon Age: Origins but only shows the most important columns. Note that DLC or expansion content may be overriding individual lines in the 2da.

{| valign="top" border="1" width="100%"
|-|
| '''ID''' || '''Stat''' || '''Type''' || '''Min''' || '''Max''' || '''Comment'''
|-|
| ''int'' || ''string'' || ''string'' || ''float'' || ''float'' || ''comment''
|-|
| 0 || INVALID || INVALID || 0 || 0 ||
|-|
| 1 || Strength || ATTRIBUTE || 0 || 1000 || STR [[Attribute]]
|-|
| 2 || Dexterity || ATTRIBUTE || 0 || 1000 || DEX [[Attribute]]
|-|
| 3 || Willpower || ATTRIBUTE || 0 || 1000 || WIL [[Attribute]]
|-|
| 4 || Magic || ATTRIBUTE || 0 || 1000 || MAG [[Attribute]]
|-|
| 5 || Cunning || ATTRIBUTE || 0 || 1000 || CUN [[Attribute]]
|-|
| 6 || Constitution || ATTRIBUTE || 0 || 1000 || CON [[Attribute]]
|-|
| 7 || Health || DEPLETABLE || 1 || 9999 || Hit Points
|-|
| 8 || Mana_Stamina || DEPLETABLE || 0 || 9999 || Mana or Stamina, based on class
|-|
| 9 || Attack || ATTRIBUTE || 0 || 1000 || Attack Power
|-|
| 10 || Defense || ATTRIBUTE || 0 || 1000 || Defense
|-|
| 11 || Armor || ATTRIBUTE || 0 || 1000 || Armor Mitigation Potential
|-|
| 12 || DamageScale || ATTRIBUTE || 1 || 10 || Based Damage Scaling (for difficulty settings and ranks)
|-|
| 13 || SpellPower || ATTRIBUTE || 0 || 1000 || Spellpower (Max(MAG-10,0)+Effects)
|-|
| 14 || Regeneration_Health || ATTRIBUTE || 0 || 50 || Health Regeneration Rate (Explore Mode) per tick.
|-|
| 15 || Level || SIMPLE || 0 || 99 || Current Character Level.
|-|
| 16 || Displacement || ATTRIBUTE || 0 || 100 || Chance to outright evade any physical attach attempt (aka Dodge)
|-|
| 17 || Inventory_Size || SIMPLE || 0 || 1000 || Inventory Slot size (on party)
|-|
| 18 || AI_BEHAVIOR || SIMPLE || 0 || 1000 || Selected AI Behavior
|-|
| 19 || Experience || SIMPLE || 0 || 186001 || Experience Points
|-|
| 20 || Flanking_Angle || ATTRIBUTE || 0 || 180 || The angle at which this creature is able to flank an enemy (default is 90)
|-|
| 21 || Melee_Crit_Modifier || ATTRIBUTE || -100 || 200 || The +melee crit modifier
|-|
| 22 || Missile_Shield || ATTRIBUTE || 0 || 100 || Chance to avoid missiles (shields and some spells increase this)
|-|
| 23 || Ranged_Crit_Modifier || ATTRIBUTE || -100 || 200 || The +ranged crit modifier
|-|
| 24 || Ranged_Aim_Speed || ATTRIBUTE || -3 || 6 || The character's speed bonus or penality when aiming with ranged weapons
|-|
| 25 || BaseAttackRating || SIMPLE || 0 || 1000 || The creature's cached base attack rating
|-|
| 26 || BaseDefenseRating || SIMPLE || 0 || 1000 || The creature's cached base defense rating
|-|
| 27 || CurrentClass || SIMPLE || 0 || 31 || The creature class (index into cla_base.xls)
|-|
| 28 || Regeneration_Health_Combat || ATTRIBUTE || 0 || 20 || The creature's health regeneration rate (per tick) in combat.
|-|
| 29 || Regeneration_Stamina || ATTRIBUTE || -20 || 50 || The creature's stamina regeneration rate (per tick) in explore mode.
|-|
| 30 || Regeneration_Stamina_Combat || ATTRIBUTE || -20 || 20 || The creature's stamina regeneration rate (per tick) in combat mode.
|-|
| 31 || AttackSpeedModifier || ATTRIBUTE || 0 || 1.5 || The creature's universal melee attack speed modifiers (used by haste, momentum, etc.)
|-|
| 32 || Resistance_Mind || ATTRIBUTE || -100 || 100 || Mental Resistance.
|-|
| 33 || Resistance_Physical || ATTRIBUTE || -100 || 100 || Physical Resistance.
|-|
| 34 || Attribute_points || SIMPLE || 0 || 100 || Holds any unspent attribute points the creature has. If this is != 0, the UI shows the levelup button.
|-|
| 35 || Skill_points || SIMPLE || 0 || 100 || Holds any unspent skill points the creature has. If this is != 0, the UI shows the levelup button.
|-|
| 36 || talent_spell_points || SIMPLE || 0 || 100 ||Holds any unspent talent points the creature has. If this is != 0, the UI shows the levelup button.
|-|
| 37 || Background || SIMPLE || 0 || 10 || The character's origin (index into backgrounds.xls).
|-|
| 38 || specialization_points || SIMPLE || 0 || 2 || Holds any unspent specialization points the creature has.
|-|
| 39 || DamageBonus || ATTRIBUTE || -100 || 100 || Universal physical attack damage bonus on the creature.
|-|
| 40 || Threat_Decrease_Rate || SIMPLE || -1000 || 1000 || The rate at which the creature's threat rating decays.
|-|
| 41 || Fatique || ATTRIBUTE || -25 || 250 || The creature's current [[Fatigue]] (% increase of ability cost).
|-|
| 42 || Damage_Resistance_Fire || ATTRIBUTE || -100 || 75 || The creature's damage resistance to fire. All fire damage is reduce by %.
|-|
| 43 || Damage_Resistance_Cold || ATTRIBUTE || -100 || 75 || The creature's damage resistance to cold. All cold damage is reduce by %.
|-|
| 44 || Damage_Resistance_Electricity || ATTRIBUTE || -100 || 75 || The creature's damage resistance to lightning. All lightning damage is reduce by %.
|-|
| 45 || Damage_Resistance_Nature || ATTRIBUTE || -100 || 75|| The creature's damage resistance to nature. All nature damage is reduce by %.
|-|
| 46 || Damage_Resistance_Spirit || ATTRIBUTE || -100 || 75 || The creature's damage resistance to spirit. All spirit damage is reduce by %.
|-|
| 47 || Damage_Shield_points || ATTRIBUTE || 0 || 9999 || Magical, damage mitigating shield (all damage types) on the creature. Creature immune to damage until the shield is depleted.
|-|
| 48 || Damage_Shield_strength || ATTRIBUTE || 0 || 100 || The maximum amount of damage the creature's magical shields can absorb (not used yet.)
|-|
| 49 || Damage_OffHand || ATTRIBUTE || 0 || 9999 || Display only cache of creature's weapon damage potential. This value is only used to marshal data into the UI, it does not have any rules implications.
|-|
| 50 || Damage_MainHand || ATTRIBUTE || 0 || 9999 || Display only cache of creature's weapon damage potential. This value is only used to marshal data into the UI, it does not have any rules implications.
|-|
| 51 || Healing_Effect_Factor || ATTRIBUTE || 100 || 200 || Percentage modifier of how effective healing is on the creature. Blood magic does NOT use this field, it is coded in effect_heal_h instead.
|-|
| 52 || Spell_resistance || ATTRIBUTE || 0 || 100 || Creature 'hostile magic resistance'. % Chance to avoid any hostile magic.
|-|
| 53 || AP_BONUS || ATTRIBUTE || -100 || 100 || Armor Penetration bonuses are stored her.
|-|
| 54 || CriticalRange || ATTRIBUTE || 0 || 200 || The 'range' which critical hits use. 150 would mean up to 150% of normal damage.
|-|
| 55 || Fire_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all fire damage dealt by the user (spells, staves, etc.)
|-|
| 56 || Spirit_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all spirit damage dealt by the user (spells, staves, etc.)
|-|
| 57 || Cold_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all cold damage dealt by the user (spells, staves, etc.)
|-|
| 58 || Nature_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all nature damage dealt by the user (spells, staves, etc.)
|-|
| 59 || Electricity_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all lightning damage dealt by the user (spells, staves, etc.)
|}

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; width:100%; height:100%"
|-
| valign="top"|
<h2 style="margin:0; background:red; font-size:150%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#fff; padding:0.2em 0.4em;">Words of Caution</h2>

Properties.xls is the most integral and powerful 2da in the game. Any changes to it have profound implications on the game and the chance of breaking existing savegames and introducing unwanted behavior.

'''Removing Rows'''
It is referenced from many other rules and UI related 2das and removing existing data can have severe consequences, including the invalidation of existing characters. You can NEVER remove rows from this 2da!

'''Changing Rows'''
Changing rows is not as dangerous as removing them, but still can have severe implications. The m2da system should be utilized to modify individual rows instead of overwriting the entire 2da. Especially the Min, Max and EngineLink columns hold a lot of rules relevant data that might not be obvious on the first glance (e.g. the Max value on 'Experience' defines the maximum XP the game will allow on a character. Any attempt to award more XP from script will silently fail.)

'''Adding rows''':
Every row added to this file will reserve several Float32 data fields on every combat capable creature in the game. While a few floats might not sound like a lot, the impact on runtime area memory, savegame size and associated load times can not be overstated. While these issues are more pressing for the console versions of the game, they still do affect the PC version and I strongly advise not to add to this file unless absolutely necessary.

|}

== Q&A ==

=== Q: Why use Floats instead of integers? ===

We had initially investigated a structure that would allow creation of typed properties but found the associated overhead and complexity in such a frequently accessed system to be too high to be worth it.

Since much of our system requires floating point values and floats can be easily rounded for display purposes, we decided to use floating point across the board.

=== Q: Won't floating point math lead to imprecision? ===

Yes, it can. Certain mathematical operations promote imprecision in floating point values. DA script, like NWScript is only precise for a limited number of digits and any existing imprecision can be magnified by consecutive divisions and other operations.

However, there are mitigating circumstances that make this much less of a problem than it might appear on paper (or fresh from university :)

* Most frequent calculations retrieve an existing floating point value cached in a property, run a bunch of calculations and then execute the result (e.g. calculating damage). The resulting values are rarely stored so imprecision has little opportunity to build up over time.

* When writing to values that are displayed as integers on the UI or used as integers in the combat math, we are casting back to integer before storing or computation (e.g. to avoid health from going into the gray realm between 0 and 1).

* Some engine commands have added security to prevent rounding errors from propagating from script into engine stored values.

* If you happen to do .004 points damage more during an attack, the gameplay impact is virtually zero, so even if imprecision manages to propagate up to the 3rd decimal, it is still not visible in the game.

=== Q: Is there anything absolutely hardcoded? ===

Yes. While nearly all C++ implemented aspects of the rules system can be turned off by removing the associated EngineLink from properties.xls, a few behaviors are not easy to modify or replace by script:

* Regeneration. While it is technically possible to turn off regeneration by setting all rates to 0, the system can not be modified. One would have to replace it with a scripted, heartbeat like construct to make changes. The reason for this is simple: Regeneration ticks at a high frequency on all combat capable creatures and the cpu time consumed by running this entirely in script is completely unacceptable.

* Some UI rules are currently hardcoded and although it is possible to control some of the UI through various 2das, replacing the entire UI with a new framework is impossible at this point.

Creature Properties

2009-10-30T16:52:15Z

Georg Zoeller: /* PROPERTY_TYPE_ATTRIBUTE */

=== Overview ===

The creature property system is the heart of the rules engine and defines all the numerical values that make up a character in Dragon Age.

=== Detailed Description ===

Properties are 32-bit floating point values associated with every combat capable creature in the game (Creature Type field in the toolset). They are used by engine, scripting and UI to make up and display the RPG ruleset of the game.

==== Property Types ====

There are 3 types of properties that abstract the most common types of statistics found in an RPG:

===== PROPERTY_TYPE_SIMPLE =====

Simple properties are 32 bit floats that can hold a single value and that generally are not modified or influenced by other properties. Examples include Experience, Level or the number of unspent talent points a character has.

===== PROPERTY_TYPE_ATTRIBUTE =====

[[Attribute]]s are a moderately complex set of values encapsulating a single character stat. They have three fields that are independently tracked in the engine and are accessible from scripting:

* Base - A character's unmodified base value, usually only modified during level up and character creation. This number is displayed as a white number the character sheet.

* Modifier - A float32 that holds the sum of all effect based modifications to the property. This number is shown as a red (if negative) or green (if positive) number on the character sheet.

* Total - The sum of the base and modifier fields along with any in engine modifications done to the property in C++ (for speed reasons) as defined by the engine link field. When reading this field, the engine will always clamp the return values between Min and Max, even through it stores the full, unmodified number internally.

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; height:100%"
|-
|'''Example:'''
A level 1 warrior with 15 strength, a buff that grants +2 strength and a shield that has a +1 strength enhancement would be stored as as:
* Base: 15
* Modifiers: 3
* Total 18
|}

===== PROPERTY_TYPE_DEPLETABLE =====
Depletables represent the most complex type of stats usually found in an RPG, used for Health and Mana. In addition to all fields present on an Attribute, they have an additional 'Current' field.

* Current - This is the character's current value in this stat, which can be between Min and Max and can exceed Total.

Additionally, just like attributes, the EngineLink field defines some hardcoded behavior in the engine such as creating the link between the 'rengeration rate' properties.

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; height:100%"
|-
|'''Example:'''
A level 1 warrior with 14 Con and 100 base health and a +5 health ring would store health who was at full health before getting hit for 20 points of damage:
* Base: 100
* Modifiers: +5
* Hidden Engine Modifiers: +20 (5 points for each point in CON after 10).
* Total: 125
* Current: 105

Hidden Engine modifiers can not be modified (obviously, they're in C++), but can be disabled by setting the EngineLink field to 0. They exist purely to speed up stats accessed with high frequency (DAScript has a 7-15x overhead per instruction compared to native code).
|}

==== Property Definitions ====

The two dimensional data array defined in [[Properties.xls]] defines numerical values that exist on every creature in the game. All properties are float32 and all rules logic of the game is based on with floating point math. This dynamic data driven approach to rules relevant stats is new to Dragon Age: Origins and makes the engine extremely flexible for Designers. It enables the game to have a rules logic that is almost completely softcoded in script and data.

The following is an excerpt from the 2da that lists all rows present in the initial ship version of Dragon Age: Origins but only shows the most important columns. Note that DLC or expansion content may be overriding individual lines in the 2da.

{| valign="top" border="1" width="100%"
|-|
| '''ID''' || '''Stat''' || '''Type''' || '''Min''' || '''Max''' || '''Comment'''
|-|
| ''int'' || ''string'' || ''string'' || ''float'' || ''float'' || ''comment''
|-|
| 0 || INVALID || INVALID || 0 || 0 ||
|-|
| 1 || Strength || ATTRIBUTE || 0 || 1000 || STR
|-|
| 2 || Dexterity || ATTRIBUTE || 0 || 1000 || DEX
|-|
| 3 || Willpower || ATTRIBUTE || 0 || 1000 || WIL
|-|
| 4 || Magic || ATTRIBUTE || 0 || 1000 || MAG
|-|
| 5 || Cunning || ATTRIBUTE || 0 || 1000 || CUN
|-|
| 6 || Constitution || ATTRIBUTE || 0 || 1000 || CON
|-|
| 7 || Health || DEPLETABLE || 1 || 9999 || Hit Points
|-|
| 8 || Mana_Stamina || DEPLETABLE || 0 || 9999 || Mana or Stamina, based on class
|-|
| 9 || Attack || ATTRIBUTE || 0 || 1000 || Attack Power
|-|
| 10 || Defense || ATTRIBUTE || 0 || 1000 || Defense
|-|
| 11 || Armor || ATTRIBUTE || 0 || 1000 || Armor Mitigation Potential
|-|
| 12 || DamageScale || ATTRIBUTE || 1 || 10 || Based Damage Scaling (for difficulty settings and ranks)
|-|
| 13 || SpellPower || ATTRIBUTE || 0 || 1000 || Spellpower (Max(MAG-10,0)+Effects)
|-|
| 14 || Regeneration_Health || ATTRIBUTE || 0 || 50 || Health Regeneration Rate (Explore Mode) per tick.
|-|
| 15 || Level || SIMPLE || 0 || 99 || Current Character Level.
|-|
| 16 || Displacement || ATTRIBUTE || 0 || 100 || Chance to outright evade any physical attach attempt (aka Dodge)
|-|
| 17 || Inventory_Size || SIMPLE || 0 || 1000 || Inventory Slot size (on party)
|-|
| 18 || AI_BEHAVIOR || SIMPLE || 0 || 1000 || Selected AI Behavior
|-|
| 19 || Experience || SIMPLE || 0 || 186001 || Experience Points
|-|
| 20 || Flanking_Angle || ATTRIBUTE || 0 || 180 || The angle at which this creature is able to flank an enemy (default is 90)
|-|
| 21 || Melee_Crit_Modifier || ATTRIBUTE || -100 || 200 || The +melee crit modifier
|-|
| 22 || Missile_Shield || ATTRIBUTE || 0 || 100 || Chance to avoid missiles (shields and some spells increase this)
|-|
| 23 || Ranged_Crit_Modifier || ATTRIBUTE || -100 || 200 || The +ranged crit modifier
|-|
| 24 || Ranged_Aim_Speed || ATTRIBUTE || -3 || 6 || The character's speed bonus or penality when aiming with ranged weapons
|-|
| 25 || BaseAttackRating || SIMPLE || 0 || 1000 || The creature's cached base attack rating
|-|
| 26 || BaseDefenseRating || SIMPLE || 0 || 1000 || The creature's cached base defense rating
|-|
| 27 || CurrentClass || SIMPLE || 0 || 31 || The creature class (index into cla_base.xls)
|-|
| 28 || Regeneration_Health_Combat || ATTRIBUTE || 0 || 20 || The creature's health regeneration rate (per tick) in combat.
|-|
| 29 || Regeneration_Stamina || ATTRIBUTE || -20 || 50 || The creature's stamina regeneration rate (per tick) in explore mode.
|-|
| 30 || Regeneration_Stamina_Combat || ATTRIBUTE || -20 || 20 || The creature's stamina regeneration rate (per tick) in combat mode.
|-|
| 31 || AttackSpeedModifier || ATTRIBUTE || 0 || 1.5 || The creature's universal melee attack speed modifiers (used by haste, momentum, etc.)
|-|
| 32 || Resistance_Mind || ATTRIBUTE || -100 || 100 || Mental Resistance.
|-|
| 33 || Resistance_Physical || ATTRIBUTE || -100 || 100 || Physical Resistance.
|-|
| 34 || Attribute_points || SIMPLE || 0 || 100 || Holds any unspent attribute points the creature has. If this is != 0, the UI shows the levelup button.
|-|
| 35 || Skill_points || SIMPLE || 0 || 100 || Holds any unspent skill points the creature has. If this is != 0, the UI shows the levelup button.
|-|
| 36 || talent_spell_points || SIMPLE || 0 || 100 ||Holds any unspent talent points the creature has. If this is != 0, the UI shows the levelup button.
|-|
| 37 || Background || SIMPLE || 0 || 10 || The character's origin (index into backgrounds.xls).
|-|
| 38 || specialization_points || SIMPLE || 0 || 2 || Holds any unspent specialization points the creature has.
|-|
| 39 || DamageBonus || ATTRIBUTE || -100 || 100 || Universal physical attack damage bonus on the creature.
|-|
| 40 || Threat_Decrease_Rate || SIMPLE || -1000 || 1000 || The rate at which the creature's threat rating decays.
|-|
| 41 || Fatique || ATTRIBUTE || -25 || 250 || The creature's current [[Fatigue]] (% increase of ability cost).
|-|
| 42 || Damage_Resistance_Fire || ATTRIBUTE || -100 || 75 || The creature's damage resistance to fire. All fire damage is reduce by %.
|-|
| 43 || Damage_Resistance_Cold || ATTRIBUTE || -100 || 75 || The creature's damage resistance to cold. All cold damage is reduce by %.
|-|
| 44 || Damage_Resistance_Electricity || ATTRIBUTE || -100 || 75 || The creature's damage resistance to lightning. All lightning damage is reduce by %.
|-|
| 45 || Damage_Resistance_Nature || ATTRIBUTE || -100 || 75|| The creature's damage resistance to nature. All nature damage is reduce by %.
|-|
| 46 || Damage_Resistance_Spirit || ATTRIBUTE || -100 || 75 || The creature's damage resistance to spirit. All spirit damage is reduce by %.
|-|
| 47 || Damage_Shield_points || ATTRIBUTE || 0 || 9999 || Magical, damage mitigating shield (all damage types) on the creature. Creature immune to damage until the shield is depleted.
|-|
| 48 || Damage_Shield_strength || ATTRIBUTE || 0 || 100 || The maximum amount of damage the creature's magical shields can absorb (not used yet.)
|-|
| 49 || Damage_OffHand || ATTRIBUTE || 0 || 9999 || Display only cache of creature's weapon damage potential. This value is only used to marshal data into the UI, it does not have any rules implications.
|-|
| 50 || Damage_MainHand || ATTRIBUTE || 0 || 9999 || Display only cache of creature's weapon damage potential. This value is only used to marshal data into the UI, it does not have any rules implications.
|-|
| 51 || Healing_Effect_Factor || ATTRIBUTE || 100 || 200 || Percentage modifier of how effective healing is on the creature. Blood magic does NOT use this field, it is coded in effect_heal_h instead.
|-|
| 52 || Spell_resistance || ATTRIBUTE || 0 || 100 || Creature 'hostile magic resistance'. % Chance to avoid any hostile magic.
|-|
| 53 || AP_BONUS || ATTRIBUTE || -100 || 100 || Armor Penetration bonuses are stored her.
|-|
| 54 || CriticalRange || ATTRIBUTE || 0 || 200 || The 'range' which critical hits use. 150 would mean up to 150% of normal damage.
|-|
| 55 || Fire_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all fire damage dealt by the user (spells, staves, etc.)
|-|
| 56 || Spirit_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all spirit damage dealt by the user (spells, staves, etc.)
|-|
| 57 || Cold_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all cold damage dealt by the user (spells, staves, etc.)
|-|
| 58 || Nature_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all nature damage dealt by the user (spells, staves, etc.)
|-|
| 59 || Electricity_Damage_Bonus || ATTRIBUTE || 0 || 30 || Percentage bonus to all lightning damage dealt by the user (spells, staves, etc.)
|}

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; width:100%; height:100%"
|-
| valign="top"|
<h2 style="margin:0; background:red; font-size:150%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#fff; padding:0.2em 0.4em;">Words of Caution</h2>

Properties.xls is the most integral and powerful 2da in the game. Any changes to it have profound implications on the game and the chance of breaking existing savegames and introducing unwanted behavior.

'''Removing Rows'''
It is referenced from many other rules and UI related 2das and removing existing data can have severe consequences, including the invalidation of existing characters. You can NEVER remove rows from this 2da!

'''Changing Rows'''
Changing rows is not as dangerous as removing them, but still can have severe implications. The m2da system should be utilized to modify individual rows instead of overwriting the entire 2da. Especially the Min, Max and EngineLink columns hold a lot of rules relevant data that might not be obvious on the first glance (e.g. the Max value on 'Experience' defines the maximum XP the game will allow on a character. Any attempt to award more XP from script will silently fail.)

'''Adding rows''':
Every row added to this file will reserve several Float32 data fields on every combat capable creature in the game. While a few floats might not sound like a lot, the impact on runtime area memory, savegame size and associated load times can not be overstated. While these issues are more pressing for the console versions of the game, they still do affect the PC version and I strongly advise not to add to this file unless absolutely necessary.

|}

== Q&A ==

=== Q: Why use Floats instead of integers? ===

We had initially investigated a structure that would allow creation of typed properties but found the associated overhead and complexity in such a frequently accessed system to be too high to be worth it.

Since much of our system requires floating point values and floats can be easily rounded for display purposes, we decided to use floating point across the board.

=== Q: Won't floating point math lead to imprecision? ===

Yes, it can. Certain mathematical operations promote imprecision in floating point values. DA script, like NWScript is only precise for a limited number of digits and any existing imprecision can be magnified by consecutive divisions and other operations.

However, there are mitigating circumstances that make this much less of a problem than it might appear on paper (or fresh from university :)

* Most frequent calculations retrieve an existing floating point value cached in a property, run a bunch of calculations and then execute the result (e.g. calculating damage). The resulting values are rarely stored so imprecision has little opportunity to build up over time.

* When writing to values that are displayed as integers on the UI or used as integers in the combat math, we are casting back to integer before storing or computation (e.g. to avoid health from going into the gray realm between 0 and 1).

* Some engine commands have added security to prevent rounding errors from propagating from script into engine stored values.

* If you happen to do .004 points damage more during an attack, the gameplay impact is virtually zero, so even if imprecision manages to propagate up to the 3rd decimal, it is still not visible in the game.

=== Q: Is there anything absolutely hardcoded? ===

Yes. While nearly all C++ implemented aspects of the rules system can be turned off by removing the associated EngineLink from properties.xls, a few behaviors are not easy to modify or replace by script:

* Regeneration. While it is technically possible to turn off regeneration by setting all rates to 0, the system can not be modified. One would have to replace it with a scripted, heartbeat like construct to make changes. The reason for this is simple: Regeneration ticks at a high frequency on all combat capable creatures and the cpu time consumed by running this entirely in script is completely unacceptable.

* Some UI rules are currently hardcoded and although it is possible to control some of the UI through various 2das, replacing the entire UI with a new framework is impossible at this point.

Rules

2009-10-30T16:51:56Z

Georg Zoeller: /* Overview */

=== Overview ===

The Core Game rules of Dragon Age are implemented mostly in the Scripting Language and Data. This page details the organization of the rules system, design principles, technical implementation details and limitations.

{| width="100%"
|-
| valign="top" height="100%" |

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; width:100%; height:100%"
|-
| valign="top"|
<h2 style="margin:0; background:#cef2e0; font-size:150%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"> Categories </h2>
|-
|
* [[Creature Properties]] - Attributes, Stats and other numbers that make up a character.
** [[Attribute]]s - Details about attributes.
* [[Classes]] - Technical information on the implementation of character classes.
* [[Combat Rules]] - The rules of conflict resolution. Who hits. When. For how much.
* [[Ability|Abilities]] - Spells, Skills, Talents and Item Abilities.
|}
|}

=== Detailed Description ===

[[Category:Scripts]]

Rules

2009-10-30T16:51:28Z

Georg Zoeller: /* Overview */

=== Overview ===

The Core Game rules of Dragon Age are implemented mostly in the Scripting Language and Data. This page details the organization of the rules system, design principles, technical implementation details and limitations.

{| width="100%"
|-
| valign="top" height="100%" |

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; width:100%; height:100%"
|-
| valign="top"|
<h2 style="margin:0; background:#cef2e0; font-size:150%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"> Categories </h2>
|-
|
* [[Creature Properties]] - Attributes, Stats and other numbers that make up a character.
** [[Attributes]] - Details about attributes.
* [[Classes]] - Technical information on the implementation of character classes.
* [[Combat Rules]] - The rules of conflict resolution. Who hits. When. For how much.
* [[Ability|Abilities]] - Spells, Skills, Talents and Item Abilities.
|}
|}

=== Detailed Description ===

[[Category:Scripts]]

Talk:Combat Rules

2009-10-30T16:43:12Z

Georg Zoeller:

Dom> Sunjammer, are you sure we want to wikifi in script function declaration? That'd generate like half a million pages. We should probably stick to file level and make your tool write out an anchor for each function
: That was our original plan (Byran being a co-conspirator) but I'm happy to look at alternatives if they would be better for the end user.
:--[[User:Sunjammer|Sunjammer]] 01:16, 28 October 2009 (UTC)
::Dom> I did some test implementation on the page, we can automate this later.
:::Looking at the examples I don't see this approach as being particularly beneficial to the end user. They can get whole definition (i.e. function body) in the script editor so all we really want is an abstraction, explanation and/or notes on usage: reproducing the function body here seems somewhat redundant. Also this approach prevents us from including the functions in the '''GeSHi''' config file (which automatically links defined functions in snippets wrapped with the '''dascript''' tags).
:::--[[User:Sunjammer|Sunjammer]] 18:33, 28 October 2009 (UTC)
::::Dom> I kind of like the ability of people being able to discuss certain parts of the code (which you can't do in the toolset). There's a lot of obscure stuff in there that profoundly affects how combat resolution works out. The other option might be to spin off a seperate wiki like the good old NWN Lexicon...

Georg> Regarding questions of why backstabs get demoted by misdirection hexes while critical hits do not: This is intentional to ensure misdirection hex is effective against high level rogues. Misdirection hex is a very powerful curse and one of the few options an AI mage has of ridding himself of a rogue who got close. The code could be structured to make this clearer, but yes, this is intentional.

Talk:Combat Rules

2009-10-30T16:41:58Z

Georg Zoeller:

Dom> Sunjammer, are you sure we want to wikifi in script function declaration? That'd generate like half a million pages. We should probably stick to file level and make your tool write out an anchor for each function
: That was our original plan (Byran being a co-conspirator) but I'm happy to look at alternatives if they would be better for the end user.
:--[[User:Sunjammer|Sunjammer]] 01:16, 28 October 2009 (UTC)
::Dom> I did some test implementation on the page, we can automate this later.
:::Looking at the examples I don't see this approach as being particularly beneficial to the end user. They can get whole definition (i.e. function body) in the script editor so all we really want is an abstraction, explanation and/or notes on usage: reproducing the function body here seems somewhat redundant. Also this approach prevents us from including the functions in the '''GeSHi''' config file (which automatically links defined functions in snippets wrapped with the '''dascript''' tags).
:::--[[User:Sunjammer|Sunjammer]] 18:33, 28 October 2009 (UTC)

Georg> Regarding questions of why backstabs get demoted by misdirection hexes while critical hits do not: This is intentional to ensure misdirection hex is effective against high level rogues. Misdirection hex is a very powerful curse and one of the few options an AI mage has of ridding himself of a rogue who got close. The code could be structured to make this clearer, but yes, this is intentional.

Combat Rules

2009-10-28T18:41:32Z

Georg Zoeller: /* Critical Hit Damage Modification */

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value and (missile deflection if attack was ranged). This includes items, effects and magical bonus.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].
* The damage logic is implemented in [[combat_damage_h.nss#Combat_Damage_GetBackstabDamage|Combat_Damage_GetBackstabDamage]].

===== Critical Hit Determination =====

* Critical Hit Chance uses the attackers Melee or Ranged critical hit modifier based on attack type.
* + the attacking weapon's critical hit modifier stat.
* + 1.20x (1.1x for non rogues) the attacker's [[#Flanking Bonus Determination|Flanking Bonus]] in the current situation.
* + 3.5 for each enemy past the 2nd that is fighting a warriors with the bravery talent.
* A critical hit occurs when the resulting CriticalHitChance is smaller than RandomFloat()*100.0f.
* Certain effects and spells (e.g. Death Hex) can always override the result, as will attacking from stealth (always hits critical).
* The logic is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]]

==== Damage Resolution ====

Damage resolution logic is implemented in the script [[combat_damage_h.nss]].

===== Critical Hit Damage Modification =====

* Critical hits increase the amount of damage done by an attack by a fixed multiplier.
* The magnitude of the multiplier can be affected by items and effects, but is not affected by of the character's attributes.
* Historical Note: Critical damage used to be variable 'up to...', but was changed to constant to provide a more predictable flow of damage.
* The logic for critical damage is implemented in [[combat_damage_h.nss#GetCriticalDamageModifier]].

===== Backstab Damage Modification =====

* Backstab damage is essentially identical to critical damage, but modified by certain rogue talents.
* The full logic is implemented [[combat_damage_h.nss#Combat_Damage_GetBackstabDamage|Combat_Damage_GetBackstabDamage]] in [[combat_damage_h.nss]].

[[Category: Scripts]]

Combat damage h.nss

2009-10-28T18:38:32Z

Georg Zoeller: /* GetCriticalDamageModifier */

=== Overview ===

combat_damage_h.nss handles the core rule resolution logic for non-spell damage.

=== Notable Functions ===

==== GetCriticalDamageModifier ====

Returns the multiplier for critical hit damage.

<dascript>
const float COMBAT_CRITICAL_DAMAGE_MODIFIER = 1.5f; // critical hits increase damage increase.

float GetCriticalDamageModifier(object oAttacker)
{
return COMBAT_CRITICAL_DAMAGE_MODIFIER + (GetCreatureProperty(oAttacker, 54 /*PROPERTY_ATTRIBUTE_CRITICAL_RANGE*/) / 100.0);
}
</dascript>

==== Combat_Damage_GetBackstabDamage ====

Determines the backstab damage given attacker and attack damage. (weapon is passed in for future use)
Note: This function was slightly modified from the toolset version to remove some non-essential elements for clarity.

<dascript>
float Combat_Damage_GetBackstabDamage(object oAttacker, object oWeapon, float fDamage)
{
// ------------------------------------------------------------------------
// Each backstab is an auto crit.
// ------------------------------------------------------------------------
fDamage *= GetCriticalDamageModifier(oAttacker);

// -------------------------------------------------------------------------
// Exploit Weakness: Backstab Damage + max(CUN-10,0) / 3.0
// -------------------------------------------------------------------------
if (HasAbility(oAttacker,ABILITY_TALENT_EXPLOIT_WEAKNESS))
{
float fBase = MaxF(0.0,(GetAttributeModifier(oAttacker,PROPERTY_ATTRIBUTE_CUNNING)/3.0)) ;
float fMod = MaxF(0.2,RandomFloat());
fDamage += (fBase * fMod);
}

return fDamage;
}
</dascript>

Combat damage h.nss

2009-10-28T18:37:53Z

Georg Zoeller: /* Notable Functions */

=== Overview ===

combat_damage_h.nss handles the core rule resolution logic for non-spell damage.

=== Notable Functions ===

==== GetCriticalDamageModifier ====

Returns the multiplier for critical hit damage.

<dascript>
const float COMBAT_CRITICAL_DAMAGE_MODIFIER = 1.5f; // critical hits increase damage by up to this factor.

float GetCriticalDamageModifier(object oAttacker)
{
return COMBAT_CRITICAL_DAMAGE_MODIFIER + (GetCreatureProperty(oAttacker, 54 /*PROPERTY_ATTRIBUTE_CRITICAL_RANGE*/) / 100.0);
}
</dascript>

==== Combat_Damage_GetBackstabDamage ====

Determines the backstab damage given attacker and attack damage. (weapon is passed in for future use)
Note: This function was slightly modified from the toolset version to remove some non-essential elements for clarity.

<dascript>
float Combat_Damage_GetBackstabDamage(object oAttacker, object oWeapon, float fDamage)
{
// ------------------------------------------------------------------------
// Each backstab is an auto crit.
// ------------------------------------------------------------------------
fDamage *= GetCriticalDamageModifier(oAttacker);

// -------------------------------------------------------------------------
// Exploit Weakness: Backstab Damage + max(CUN-10,0) / 3.0
// -------------------------------------------------------------------------
if (HasAbility(oAttacker,ABILITY_TALENT_EXPLOIT_WEAKNESS))
{
float fBase = MaxF(0.0,(GetAttributeModifier(oAttacker,PROPERTY_ATTRIBUTE_CUNNING)/3.0)) ;
float fMod = MaxF(0.2,RandomFloat());
fDamage += (fBase * fMod);
}

return fDamage;
}
</dascript>

Combat Rules

2009-10-28T18:30:57Z

Georg Zoeller: /* Damage Resolution */

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value and (missile deflection if attack was ranged). This includes items, effects and magical bonus.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].
* The damage logic is implemented in [[combat_damage_h.nss#Combat_Damage_GetBackstabDamage|Combat_Damage_GetBackstabDamage]].

===== Critical Hit Determination =====

* Critical Hit Chance uses the attackers Melee or Ranged critical hit modifier based on attack type.
* + the attacking weapon's critical hit modifier stat.
* + 1.20x (1.1x for non rogues) the attacker's [[#Flanking Bonus Determination|Flanking Bonus]] in the current situation.
* + 3.5 for each enemy past the 2nd that is fighting a warriors with the bravery talent.
* A critical hit occurs when the resulting CriticalHitChance is smaller than RandomFloat()*100.0f.
* Certain effects and spells (e.g. Death Hex) can always override the result, as will attacking from stealth (always hits critical).
* The logic is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]]

==== Damage Resolution ====

Damage resolution logic is implemented in the script [[combat_damage_h.nss]].

===== Critical Hit Damage Modification =====

* Critical hits increase the amount of damage done by an attack by a fixed multiplier.
* The magnitude of the multiplier can be affected by items and effects, but is not affected by stats.

===== Backstab Damage Modification =====

* Backstab damage is essentially identical to critical damage, but modified by certain rogue talents.
* The full logic is implemented [[combat_damage_h.nss#Combat_Damage_GetBackstabDamage|Combat_Damage_GetBackstabDamage]] in [[combat_damage_h.nss]].

[[Category: Scripts]]

Combat Rules

2009-10-28T18:22:44Z

Georg Zoeller: /* Damage Resolution */

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value and (missile deflection if attack was ranged). This includes items, effects and magical bonus.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].
* The damage logic is implemented in [[combat_damage_h.nss#Combat_Damage_GetBackstabDamage|Combat_Damage_GetBackstabDamage]].

===== Critical Hit Determination =====

* Critical Hit Chance uses the attackers Melee or Ranged critical hit modifier based on attack type.
* + the attacking weapon's critical hit modifier stat.
* + 1.20x (1.1x for non rogues) the attacker's [[#Flanking Bonus Determination|Flanking Bonus]] in the current situation.
* + 3.5 for each enemy past the 2nd that is fighting a warriors with the bravery talent.
* A critical hit occurs when the resulting CriticalHitChance is smaller than RandomFloat()*100.0f.
* Certain effects and spells (e.g. Death Hex) can always override the result, as will attacking from stealth (always hits critical).
* The logic is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]]

==== Damage Resolution ====

Damage resolution logic is implemented in the script [[combat_damage_h.nss]].

===== Backstab Damage Modifications =====

* Backstab damage is essentially identical to critical damage, but modified by certain rogue talents.
* The full logic is implemented [[combat_damage_h.nss#Combat_Damage_GetBackstabDamage|Combat_Damage_GetBackstabDamage]] in [[combat_damage_h.nss]].

[[Category: Scripts]]

Combat Rules

2009-10-28T18:19:54Z

Georg Zoeller: /* Backstab Determination */

Combat damage h.nss

2009-10-28T18:19:14Z

Georg Zoeller: /* Combat_Damage_GetBackstabDamage */

=== Overview ===

combat_damage_h.nss handles the core rule resolution logic for non-spell damage.

=== Notable Functions ===

==== Combat_Damage_GetBackstabDamage ====

Determines the backstab damage given attacker, weapon and attack damage.
Note: This function was slightly modified from the toolset version to remove some non-essential elements for clarity.

<dascript>
float Combat_Damage_GetBackstabDamage(object oAttacker, object oWeapon, float fDamage)
{
// ------------------------------------------------------------------------
// Each backstab is an auto crit.
// ------------------------------------------------------------------------
fDamage *= GetCriticalDamageModifier(oAttacker);

// -------------------------------------------------------------------------
// Exploit Weakness: Backstab Damage + max(CUN-10,0) / 3.0
// -------------------------------------------------------------------------
if (HasAbility(oAttacker,ABILITY_TALENT_EXPLOIT_WEAKNESS))
{
float fBase = MaxF(0.0,(GetAttributeModifier(oAttacker,PROPERTY_ATTRIBUTE_CUNNING)/3.0)) ;
float fMod = MaxF(0.2,RandomFloat());
fDamage += (fBase * fMod);
}

return fDamage;
}
</dascript>

Combat damage h.nss

2009-10-28T18:18:40Z

Georg Zoeller: Created page with '=== Overview === combat_damage_h.nss handles the core rule resolution logic for non-spell damage. === Notable Functions === ==== Combat_Damage_GetBackstabDamage ==== Determ...'

=== Overview ===

combat_damage_h.nss handles the core rule resolution logic for non-spell damage.

=== Notable Functions ===

==== Combat_Damage_GetBackstabDamage ====

Determines the backstab damage given attacker, weapon and attack damage.
Note: This function was slightly modified from the toolset version to remove some non-essential elements for clarity.

<dascript>
float Combat_Damage_GetBackstabDamage(object oAttacker, object oWeapon, float fDamage)
{
// ------------------------------------------------------------------------
// Each backstab is an auto crit.
// ------------------------------------------------------------------------
fDamage *= GetCriticalDamageModifier(oAttacker);

// -------------------------------------------------------------------------
// Exploit Weakness: Backstab Damage = max(CUN-10,0) / 3.0
// -------------------------------------------------------------------------
if (HasAbility(oAttacker,ABILITY_TALENT_EXPLOIT_WEAKNESS))
{
float fBase = MaxF(0.0,(GetAttributeModifier(oAttacker,PROPERTY_ATTRIBUTE_CUNNING)/3.0)) ;
float fMod = MaxF(0.2,RandomFloat());
fDamage += (fBase * fMod);
}

return fDamage;
}
</dascript>

Combat Rules

2009-10-28T18:14:11Z

Georg Zoeller: /* Damage Resolution */

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value and (missile deflection if attack was ranged). This includes items, effects and magical bonus.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].

===== Critical Hit Determination =====

* Critical Hit Chance uses the attackers Melee or Ranged critical hit modifier based on attack type.
* + the attacking weapon's critical hit modifier stat.
* + 1.20x (1.1x for non rogues) the attacker's [[#Flanking Bonus Determination|Flanking Bonus]] in the current situation.
* + 3.5 for each enemy past the 2nd that is fighting a warriors with the bravery talent.
* A critical hit occurs when the resulting CriticalHitChance is smaller than RandomFloat()*100.0f.
* Certain effects and spells (e.g. Death Hex) can always override the result, as will attacking from stealth (always hits critical).
* The logic is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]]

==== Damage Resolution ====

Damage resolution logic is implemented in the script [[combat_damage_h.nss]].

[[Category: Scripts]]

Combat Rules

2009-10-28T16:52:24Z

Georg Zoeller: /* Defense Rating */ clarified.

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value and (missile deflection if attack was ranged). This includes items, effects and magical bonus.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].

===== Critical Hit Determination =====

* Critical Hit Chance uses the attackers Melee or Ranged critical hit modifier based on attack type.
* + the attacking weapon's critical hit modifier stat.
* + 1.20x (1.1x for non rogues) the attacker's [[#Flanking Bonus Determination|Flanking Bonus]] in the current situation.
* + 3.5 for each enemy past the 2nd that is fighting a warriors with the bravery talent.
* A critical hit occurs when the resulting CriticalHitChance is smaller than RandomFloat()*100.0f.
* Certain effects and spells (e.g. Death Hex) can always override the result, as will attacking from stealth (always hits critical).
* The logic is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]]

==== Damage Resolution ====

[[Category: Scripts]]

Combat Rules

2009-10-28T03:41:11Z

Georg Zoeller:

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value or missile deflection if attack was ranged. This includes items, effects and magical bonus.
* Yes, this means that avoiding archers is hard for characters without a shield.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].

===== Critical Hit Determination =====

* Critical Hit Chance uses the attackers Melee or Ranged critical hit modifier based on attack type.
* + the attacking weapon's critical hit modifier stat.
* + 1.20x (1.1x for non rogues) the attacker's [[#Flanking Bonus Determination|Flanking Bonus]] in the current situation.
* + 3.5 for each enemy past the 2nd that is fighting a warriors with the bravery talent.
* A critical hit occurs when the resulting CriticalHitChance is smaller than RandomFloat()*100.0f.
* Certain effects and spells (e.g. Death Hex) can always override the result, as will attacking from stealth (always hits critical).
* The logic is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]]

==== Damage Resolution ====

[[Category: Scripts]]

Combat Rules

2009-10-28T03:40:52Z

Georg Zoeller: Critical hit details and link to the full GetCombatResult code.

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value or missile deflection if attack was ranged. This includes items, effects and magical bonus.
* Yes, this means that avoiding archers is hard for characters without a shield.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].

===== Critical Hit Determination =====

* Critical Hit Chance uses the attackers Melee or Ranged critical hit modifier based on attack type.
* + the attacking weapon's critical hit modifier stat.
* + 1.20x (1.1x for non rogues) the attacker's [[#Flanking Bonus Determination|Flanking Bonus]] in the current situation.
* + 3.5 for each enemy past the 2nd that is fighting a warriors with the bravery talent.
* A critical hit occurs when the resulting CriticalHitChance is smaller than RandomFloat()*100.0f.
* Certain effects and spells (e.g. Death Hex) can always override the result, as will attacking from stealth (always hits critical).
* The logic is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]]

==== Damage Resolution ====

[[Category: Scripts]]

Combat h.nss

2009-10-28T03:30:04Z

Georg Zoeller: /* Combat_GetAttackResult */

=== Overview ===

Combat_h.nss handles the core rule resolution logic for non-talent combat interaction.

=== Notable Functions ===

==== Combat_GetAttackResult ====

This function is determines whether or not a weapon/unarmed attack hits and determines substates such as critical hit or backstab.

<dascript>
/**
* @brief Determine whether or not an attack hits a target.
*
* Note that this function only calculates to hit and crits, death blows are
* determined in Combat_PerformAttack
*
* @param oAttacker The attacker
* @param oTarget The target that is being attacked
* @param nAbility If != 0, it won't trigger backstabs and deathblows.
*
* @returns COMBAT_RESULT_HIT, COMBAT_RESULT_CRITICALHIT or COMBAT_RESULT_MISS
*
* @author Georg Zoeller
*
**/
int Combat_GetAttackResult(object oAttacker, object oTarget, object oWeapon, float fBonus = 0.0f, int nAbility = 0);
int Combat_GetAttackResult(object oAttacker, object oTarget, object oWeapon, float fBonus = 0.0f, int nAbility = 0)
{

// -------------------------------------------------------------------------
// Debug
// -------------------------------------------------------------------------
int nForcedCombatResult = GetForcedCombatResult(oAttacker);
if (nForcedCombatResult != -1)
{
#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," Skipped rules, FORCED RESULT IS:" + ToString(nForcedCombatResult), oTarget);
#endif
return nForcedCombatResult;
}

// -------------------------------------------------------------------------
// Placeables are always hit
// -------------------------------------------------------------------------
if (GetObjectType(oTarget) == OBJECT_TYPE_PLACEABLE)
{
#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," Placeable, automatic result : COMBAT_RESULT_HIT", oTarget);
#endif
return COMBAT_RESULT_HIT;
}

// -------------------------------------------------------------------------
// Displacement / Dodge
// -------------------------------------------------------------------------
float fDisplace = GetCreatureProperty(oTarget, PROPERTY_ATTRIBUTE_DISPLACEMENT);
float fRand = RandomFloat()*100.0;
if ( fRand < fDisplace)
{
#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," Displacement effect kciked in, automatic result : COMBAT_RESULT_MISS", oTarget);
#endif

// ---------------------------------------------------------------------
// if the target has the evasion talent, attribute this miss to the talent
// (random 50% because the anim is interrupting)
// ---------------------------------------------------------------------
if (HasAbility(oTarget, ABILITY_TALENT_EVASION) && fRand < (20.0f - (RandomFloat()*10.0f) ))
{
command currentCmd = GetCurrentCommand(oTarget);
int nCmdType = GetCommandType(currentCmd);

// Evasion only plays during attack and wait commands.
if ( nCmdType == COMMAND_TYPE_WAIT || nCmdType == COMMAND_TYPE_ATTACK || nCmdType == COMMAND_TYPE_INVALID )
{
ApplyEffectOnObject(EFFECT_DURATION_TYPE_INSTANT, Effect(1055), oTarget, 0.0f, oTarget, ABILITY_TALENT_EVASION);
}
}

return COMBAT_RESULT_MISS;
}

int nAttackType = Combat_GetAttackType(oAttacker, oWeapon);
int nRet;

// -------------------------------------------------------------------------
// Get the attackers attack rating (includes effects and equipment stats)
// -------------------------------------------------------------------------
float fAttackRating;

if (GetBaseItemType(oWeapon) == BASE_ITEM_TYPE_STAFF)
{
// ---------------------------------------------------------------------
// Staves always hit
// ---------------------------------------------------------------------
return COMBAT_RESULT_HIT;
}

fAttackRating = GetCreatureAttackRating (oAttacker);

// -------------------------------------------------------------------------
// Add item stat (usually 0) along with scripted boni and attack bias.
// -------------------------------------------------------------------------

fAttackRating += GetItemStat(oWeapon, ITEM_STAT_ATTACK) + fBonus + ATTACK_HIT_BIAS;

// -------------------------------------------------------------------------
// Easier difficulties grant the player a bonus.
// -------------------------------------------------------------------------
fAttackRating += Diff_GetRulesAttackBonus(oAttacker);

// -------------------------------------------------------------------------
// This section deals with figuring out which critical hit modifier (melee, ranged, etc)
// to use for this attack.
// -------------------------------------------------------------------------
float fCriticalHitModifier;
int nCriticalHitModifier = (nAttackType == ATTACK_TYPE_RANGED) ? CRITICAL_MODIFIER_RANGED : CRITICAL_MODIFIER_MELEE;

fCriticalHitModifier = GetCreatureCriticalHitModifier(oAttacker, nCriticalHitModifier);
fCriticalHitModifier += GetItemStat(oWeapon, ITEM_STAT_CRIT_CHANCE_MODIFIER);

// -------------------------------------------------------------------------
// Bravery grants +3.5 critical hit per enemy past the first 2
// -------------------------------------------------------------------------
if (HasAbility(oAttacker, ABILITY_TALENT_BRAVERY))
{

int nEnemies = Max(0,GetArraySize(GetCreaturesInMeleeRing(oAttacker,0.0, 359.99f,TRUE,0))-2);
fCriticalHitModifier += nEnemies * 3.5f;
}

// -------------------------------------------------------------------------
// Calculate Flanking Bonus
// -------------------------------------------------------------------------
float fFlanking = Combat_GetFlankingBonus(oAttacker, oTarget);
if (fFlanking > 0.0 )
{
// ---------------------------------------------------------------------
// Also increase chance for critical hits by 1/5th of the flanking bonus
// ---------------------------------------------------------------------
fCriticalHitModifier *= (1.0 + (fFlanking/5.0));
}

// -------------------------------------------------------------------------
// Range plays a role too.
// -------------------------------------------------------------------------
float fDistance = GetDistanceBetween(oAttacker, oTarget);
float fNoPenaltyDistance = MaxF(POINT_BLANK_RANGE,GetItemStat(oWeapon, ITEM_STAT_OPTIMUM_RANGE));
fDistance = MaxF(fDistance-fNoPenaltyDistance,0.0f);

float fAttackRoll = 50.0;
float fPenalties = fDistance; // every meter distance past the free range is -1!
float fAttack = fAttackRating + fAttackRoll + fFlanking - fPenalties;

// >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
// BEGIN SECTION CRITICAL HITS
// >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

int bThreatenCritical = (RandomFloat()*100.0f < fCriticalHitModifier );

if (!bThreatenCritical)
{
// ---------------------------------------------------------------------
// Attacking out of stealth always threatens crit.
// ---------------------------------------------------------------------
if (IsModalAbilityActive(oAttacker, ABILITY_SKILL_STEALTH_1))
{
bThreatenCritical = TRUE;
}

// -----------------------------------------------------------------
// Death hex effect ... all hits are auto crit
// -----------------------------------------------------------------
if (GetHasEffects(oTarget, EFFECT_TYPE_DEATH_HEX))
{
bThreatenCritical = TRUE;
}

// -----------------------------------------------------------------
// Autocrit effect
// -----------------------------------------------------------------
if (GetHasEffects(oAttacker, EFFECT_TYPE_AUTOCRIT))
{
bThreatenCritical = TRUE;
}
}
else
{
// ---------------------------------------------------------------------
// Double strike does not allow crits
// ---------------------------------------------------------------------
if (IsModalAbilityActive(oAttacker, ABILITY_TALENT_DUAL_WEAPON_DOUBLE_STRIKE))
{
bThreatenCritical = FALSE;
}

// rapid shot doesn't allow critical strikes
if (IsModalAbilityActive(oAttacker, ABILITY_TALENT_RAPIDSHOT))
{
bThreatenCritical = FALSE;
}
}

// ---------------------------------------------------------------------
// Targets that have critical hit immunity can not be crit...
// ---------------------------------------------------------------------
if (bThreatenCritical)
{
bThreatenCritical = !HasAbility(oTarget, ABILITY_TRAIT_CRITICAL_HIT_IMMUNITY);

if (!bThreatenCritical)
Log_Trace_Combat("combat_h.GetAttackResult"," Critical hit averted, target has critical hit immunity", oTarget);
}

// <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
// END SECTION CRITICAL HITS
// <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

// -------------------------------------------------------------------------
// This section deals with calculating the defense values of the attack target
// -------------------------------------------------------------------------
float fDefenseRating = GetCreatureDefense(oTarget) + ((nAttackType == ATTACK_TYPE_RANGED) ? GetCreatureProperty(oTarget,PROPERTY_ATTRIBUTE_MISSILE_SHIELD):0.0f);

// -------------------------------------------------------------------------
// Easier difficulties grant the player a bonus.
// -------------------------------------------------------------------------
fDefenseRating += Diff_GetRulesDefenseBonus(oTarget);

// -------------------------------------------------------------------------
// A hit is successful if the attack rating exceeds the defense rating
// -------------------------------------------------------------------------
if (RandomFloat()*100.0f < fAttack - fDefenseRating)
{

// ---------------------------------------------------------------------
// If we threatened a critical, we crit here, otherwise just report normal hit
// ---------------------------------------------------------------------
nRet = ( (bThreatenCritical) ? COMBAT_RESULT_CRITICALHIT : COMBAT_RESULT_HIT );

if ( nAttackType == ATTACK_TYPE_MELEE)
{
// -----------------------------------------------------------------
// If we are backstabbing, we change the result here if it
// was a crit. Abilities never bs (anim priority)
// -----------------------------------------------------------------
if ( nAbility == 0 && Combat_CheckBackstab(oAttacker, oTarget, oWeapon,fFlanking))
{
nRet = COMBAT_RESULT_BACKSTAB;
}
}

}
// -------------------------------------------------------------------------
// Miss...
// -------------------------------------------------------------------------
else
{
nRet = COMBAT_RESULT_MISS;

}

// -------------------------------------------------------------------------
// Misdirection Hex
// -------------------------------------------------------------------------
if (GetHasEffects(oAttacker, EFFECT_TYPE_MISDIRECTION_HEX))
{
#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," Attacker under misdirection hex: Hits are misses, crits are hits.", oTarget);
#endif

if (nRet == COMBAT_RESULT_HIT || nRet == COMBAT_RESULT_BACKSTAB)
{
nRet = COMBAT_RESULT_MISS;
}
else if (nRet == COMBAT_RESULT_CRITICALHIT)
{
nRet = COMBAT_RESULT_HIT;
}
}

#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," ToHit Calculation: " +
" fAttack:" + ToString(fAttack) +
" = (fAttackRating: " + ToString(fAttackRating) +
" fAttackRoll:" + ToString(fAttackRoll) +
" (range penalty:" + ToString(fPenalties) + ")"+
" fFlanking: " + ToString(fFlanking) +
" fBonus(script): " + ToString(fBonus) +
")" , oAttacker, oTarget, LOG_CHANNEL_COMBAT_TOHIT );

Log_Trace_Combat("combat_h.GetAttackResult"," ToHit Calculation (2): " +
" fDefenseRating: " + ToString(fDefenseRating) +
" fCriticalHitModifier: " + ToString(fCriticalHitModifier) +
" bThreatenCritical: " + ToString(bThreatenCritical), oAttacker, oTarget, LOG_CHANNEL_COMBAT_TOHIT );

#endif

return nRet;
}
</dascript>

==== Combat_CheckBackstab ====

<dascript>
// -----------------------------------------------------------------------------
// Check if backstab conditions are true
// -----------------------------------------------------------------------------
int Combat_CheckBackstab(object oAttacker, object oTarget, object oWeapon, float fFlankingBonus)
{
// -------------------------------------------------------------------------
// If we we are a rogue
// -------------------------------------------------------------------------
if (!HasAbility(oAttacker, ABILITY_TALENT_HIDDEN_ROGUE))
{
return FALSE;
}

// -------------------------------------------------------------------------
// Only humanoid rigs have the backstab anim
// -------------------------------------------------------------------------
if (!IsHumanoid(oAttacker))
{
return FALSE;
}

// -------------------------------------------------------------------------
// And target is not immune
// -------------------------------------------------------------------------
if (HasAbility(oTarget, ABILITY_TRAIT_CRITICAL_HIT_IMMUNITY))
{
return FALSE;
}

// -------------------------------------------------------------------------
// And attacker does not use double strike mode
// -------------------------------------------------------------------------
if (IsModalAbilityActive(oAttacker, ABILITY_TALENT_DUAL_WEAPON_DOUBLE_STRIKE))
{
return FALSE;
}

// -------------------------------------------------------------------------
// We can only backstab if we are flanking.
// -------------------------------------------------------------------------
if (fFlankingBonus>0.0)
{
return TRUE;
}
else
{
/* Coup de grace*/
if (HasAbility(oAttacker, ABILITY_TALENT_BACKSTAB))
{
if (GetHasEffects(oTarget, EFFECT_TYPE_STUN))
{
return TRUE;
}
else if (GetHasEffects(oTarget, EFFECT_TYPE_PARALYZE))
{
return TRUE;
}
}

}

return FALSE;
}
</dascript>

==== Combat_GetFlankingBonus ====

This function is invoked during to hit determination and returns the magnitude
of the benefit the attacker may receive due to his facing and location relative to
the target.

<dascript>
// -----------------------------------------------------------------------------
// Determine the magnitude of positional bonuses for the attacker
// -----------------------------------------------------------------------------
float Combat_GetFlankingBonus(object oAttacker, object oTarget)
{

if (HasAbility(oTarget, ABILITY_TALENT_SHIELD_TACTICS))
{
if (IsUsingShield(oTarget))
return 0.0;
}

if (GetHasEffects(oTarget, EFFECT_TYPE_FLANK_IMMUNITY))
{
return 0.0;
}

float fAngle = GetAngleBetweenObjects(oTarget, oAttacker);
float fFactor = 0.0;

// -------------------------------------------------------------------------
// The maximum bonus from position is +15
// -------------------------------------------------------------------------
float fMaxModifier = 15.0;

// The attackers ability to flank is stored in a creature property
float fFlankingAngle = GetCreatureProperty(oAttacker, PROPERTY_ATTRIBUTE_FLANKING_ANGLE);

if (fFlankingAngle <= 10.0 ) /*old savegames have this at 10*/
{
fFlankingAngle = 60.0; // old savegames need this to avoid divby0 later
}
else if (fFlankingAngle>180.0)
{
fFlankingAngle = 180.0;
}

// -------------------------------------------------------------------------
// Combat movement expands the maximum bonus to +20
// -------------------------------------------------------------------------
if (HasAbility(oAttacker, ABILITY_TALENT_COMBAT_MOVEMENT))
{
fMaxModifier = 20.0;
}

if ( fMaxModifier <= 0.0 )
{
return 0.0;
}

if ( (fAngle>= (180.0 - fFlankingAngle) && fAngle<=(180.0 + fFlankingAngle )))
{
// Shield block negates flanking on the left.

int bShieldBlock = HasAbility(oTarget,ABILITY_TALENT_SHIELD_BLOCK);
int bUsingShield = IsUsingShield(oTarget);

if (!bShieldBlock || fAngle < 180.0 || (bShieldBlock && !bUsingShield) )
{
fFactor = (fFlankingAngle - fabs( 180.0 - fAngle))/fFlankingAngle;
}

}

// Only rogues get the full positional benefits on the battlefield,
// everyone else gets half
float fClassModifier = GetCreatureCoreClass(oAttacker) == CLASS_ROGUE?1.0f:0.5f;

return fFactor * fMaxModifier * fClassModifier;
}
</dascript>

[[Category: Scripts]]

Combat Rules

2009-10-28T03:28:03Z

Georg Zoeller: /* Hit Resolution */

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value or missile deflection if attack was ranged. This includes items, effects and magical bonus.
* Yes, this means that avoiding archers is hard for characters without a shield.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].

==== Damage Resolution ====

[[Category: Scripts]]

Combat h.nss

2009-10-28T03:27:19Z

Georg Zoeller: Added code for combat_getattackresult

=== Overview ===

Combat_h.nss handles the core rule resolution logic for non-talent combat interaction.

=== Notable Functions ===

==== Combat_GetAttackResult ====

This function is determines whether or not a weapon/unarmed attack hits and determines substates such as critical hit or backstab.

<dascript>
/**
* @brief Determine whether or not an attack hits a target.
*
* Note that this function only calculates to hit and crits, death blows are
* determined in Combat_PerformAttack
*
* @param oAttacker The attacker
* @param oTarget The target that is being attacked
* @param nAbility If != 0, it won't trigger backstabs and deathblows.
*
* @returns COMBAT_RESULT_HIT, COMBAT_RESULT_CRITICALHIT or COMBAT_RESULT_MISS
*
* @author Georg Zoeller
*
**/
int Combat_GetAttackResult(object oAttacker, object oTarget, object oWeapon, float fBonus = 0.0f, int nAbility = 0);
int Combat_GetAttackResult(object oAttacker, object oTarget, object oWeapon, float fBonus = 0.0f, int nAbility = 0)
{

// -------------------------------------------------------------------------
// Debug
// -------------------------------------------------------------------------
int nForcedCombatResult = GetForcedCombatResult(oAttacker);
if (nForcedCombatResult != -1)
{
#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," Skipped rules, FORCED RESULT IS:" + ToString(nForcedCombatResult), oTarget);
#endif
return nForcedCombatResult;
}

// -------------------------------------------------------------------------
// Placeables are always hit
// -------------------------------------------------------------------------
if (GetObjectType(oTarget) == OBJECT_TYPE_PLACEABLE)
{
#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," Placeable, automatic result : COMBAT_RESULT_HIT", oTarget);
#endif
return COMBAT_RESULT_HIT;
}

// -------------------------------------------------------------------------
// Displacement / Dodge
// -------------------------------------------------------------------------
float fDisplace = GetCreatureProperty(oTarget, PROPERTY_ATTRIBUTE_DISPLACEMENT);
float fRand = RandomFloat()*100.0;
if ( fRand < fDisplace)
{
#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," Displacement effect kciked in, automatic result : COMBAT_RESULT_MISS", oTarget);
#endif

// ---------------------------------------------------------------------
// if the target has the evasion talent, attribute this miss to the talent
// (random 50% because the anim is interrupting)
// ---------------------------------------------------------------------
if (HasAbility(oTarget, ABILITY_TALENT_EVASION) && fRand < (20.0f - (RandomFloat()*10.0f) ))
{
command currentCmd = GetCurrentCommand(oTarget);
int nCmdType = GetCommandType(currentCmd);

// Evasion only plays during attack and wait commands.
if ( nCmdType == COMMAND_TYPE_WAIT || nCmdType == COMMAND_TYPE_ATTACK || nCmdType == COMMAND_TYPE_INVALID )
{
ApplyEffectOnObject(EFFECT_DURATION_TYPE_INSTANT, Effect(1055), oTarget, 0.0f, oTarget, ABILITY_TALENT_EVASION);
}
}

return COMBAT_RESULT_MISS;
}

int nAttackType = Combat_GetAttackType(oAttacker, oWeapon);
int nRet;

// -------------------------------------------------------------------------
// Get the attackers attack rating (includes effects and equipment stats)
// -------------------------------------------------------------------------
float fAttackRating;

if (GetBaseItemType(oWeapon) == BASE_ITEM_TYPE_STAFF)
{
// ---------------------------------------------------------------------
// Staves always hit
// ---------------------------------------------------------------------
return COMBAT_RESULT_HIT;
}

fAttackRating = GetCreatureAttackRating (oAttacker);

// -------------------------------------------------------------------------
// Add item stat (usually 0) along with scripted boni and attack bias.
// -------------------------------------------------------------------------

fAttackRating += GetItemStat(oWeapon, ITEM_STAT_ATTACK) + fBonus + ATTACK_HIT_BIAS;

// -------------------------------------------------------------------------
// Easier difficulties grant the player a bonus.
// -------------------------------------------------------------------------
fAttackRating += Diff_GetRulesAttackBonus(oAttacker);

// -------------------------------------------------------------------------
// This section deals with figuring out which critical hit modifier (melee, ranged, etc)
// to use for this attack.
// -------------------------------------------------------------------------
float fCriticalHitModifier;
int nCriticalHitModifier = (nAttackType == ATTACK_TYPE_RANGED) ? CRITICAL_MODIFIER_RANGED : CRITICAL_MODIFIER_MELEE;

fCriticalHitModifier = GetCreatureCriticalHitModifier(oAttacker, nCriticalHitModifier);
fCriticalHitModifier += GetItemStat(oWeapon, ITEM_STAT_CRIT_CHANCE_MODIFIER);

// -------------------------------------------------------------------------
// Bravery grants +3.5 critical hit per enemy past the first 2
// -------------------------------------------------------------------------
if (HasAbility(oAttacker, ABILITY_TALENT_BRAVERY))
{

int nEnemies = Max(0,GetArraySize(GetCreaturesInMeleeRing(oAttacker,0.0, 359.99f,TRUE,0))-2);
fCriticalHitModifier += nEnemies * 3.5f;
}

// -------------------------------------------------------------------------
// Calculate Flanking Bonus
// -------------------------------------------------------------------------
float fFlanking = Combat_GetFlankingBonus(oAttacker, oTarget);
if (fFlanking > 0.0 )
{
// ---------------------------------------------------------------------
// Also increase chance for critical hits by 1/5th of the flanking bonus
// ---------------------------------------------------------------------
fCriticalHitModifier *= (1.0 + (fFlanking/5.0));
}

// -------------------------------------------------------------------------
// Range plays a role too.
// -------------------------------------------------------------------------
float fDistance = GetDistanceBetween(oAttacker, oTarget);
float fNoPenaltyDistance = MaxF(POINT_BLANK_RANGE,GetItemStat(oWeapon, ITEM_STAT_OPTIMUM_RANGE));
fDistance = MaxF(fDistance-fNoPenaltyDistance,0.0f);

float fAttackRoll = 50.0;
float fPenalties = fDistance; // every meter distance past the free range is -1!
float fAttack = fAttackRating + fAttackRoll + fFlanking - fPenalties;

// >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
// BEGIN SECTION CRITICAL HITS
// >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

int bThreatenCritical = (RandomFloat()*100.0f < fCriticalHitModifier );

if (!bThreatenCritical)
{
// ---------------------------------------------------------------------
// Attacking out of stealth always threatens crit.
// ---------------------------------------------------------------------
if (IsModalAbilityActive(oAttacker, ABILITY_SKILL_STEALTH_1))
{
bThreatenCritical = TRUE;
}

// -----------------------------------------------------------------
// Death hex effect ... all hits are auto crit
// -----------------------------------------------------------------
if (GetHasEffects(oTarget, EFFECT_TYPE_DEATH_HEX))
{
bThreatenCritical = TRUE;
}

// -----------------------------------------------------------------
// Autocrit effect
// -----------------------------------------------------------------
if (GetHasEffects(oAttacker, EFFECT_TYPE_AUTOCRIT))
{
bThreatenCritical = TRUE;
}
}
else
{
// ---------------------------------------------------------------------
// Double strike does not allow crits
// ---------------------------------------------------------------------
if (IsModalAbilityActive(oAttacker, ABILITY_TALENT_DUAL_WEAPON_DOUBLE_STRIKE))
{
bThreatenCritical = FALSE;
}

// rapid shot doesn't allow critical strikes
if (IsModalAbilityActive(oAttacker, ABILITY_TALENT_RAPIDSHOT))
{
bThreatenCritical = FALSE;
}
}

// ---------------------------------------------------------------------
// Targets that have critical hit immunity can not be crit...
// ---------------------------------------------------------------------
if (bThreatenCritical)
{
Log_Trace_Combat("combat_h.GetAttackResult"," Critical hit averted, target has critical hit immunity", oTarget);
bThreatenCritical = !HasAbility(oTarget, ABILITY_TRAIT_CRITICAL_HIT_IMMUNITY);
}

// <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
// END SECTION CRITICAL HITS
// <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

// -------------------------------------------------------------------------
// This section deals with calculating the defense values of the attack target
// -------------------------------------------------------------------------
float fDefenseRating = GetCreatureDefense(oTarget) + ((nAttackType == ATTACK_TYPE_RANGED) ? GetCreatureProperty(oTarget,PROPERTY_ATTRIBUTE_MISSILE_SHIELD):0.0f);

// -------------------------------------------------------------------------
// Easier difficulties grant the player a bonus.
// -------------------------------------------------------------------------
fDefenseRating += Diff_GetRulesDefenseBonus(oTarget);

// -------------------------------------------------------------------------
// A hit is successful if the attack rating exceeds the defense rating
// -------------------------------------------------------------------------
if (RandomFloat()*100.0f < fAttack - fDefenseRating)
{

// ---------------------------------------------------------------------
// If we threatened a critical, we crit here, otherwise just report normal hit
// ---------------------------------------------------------------------
nRet = ( (bThreatenCritical) ? COMBAT_RESULT_CRITICALHIT : COMBAT_RESULT_HIT );

if ( nAttackType == ATTACK_TYPE_MELEE)
{
// -----------------------------------------------------------------
// If we are backstabbing, we change the result here if it
// was a crit. Abilities never bs (anim priority)
// -----------------------------------------------------------------
if ( nAbility == 0 && Combat_CheckBackstab(oAttacker, oTarget, oWeapon,fFlanking))
{
nRet = COMBAT_RESULT_BACKSTAB;
}
}

}
// -------------------------------------------------------------------------
// Miss...
// -------------------------------------------------------------------------
else
{
nRet = COMBAT_RESULT_MISS;

}

// -------------------------------------------------------------------------
// Misdirection Hex
// -------------------------------------------------------------------------
if (GetHasEffects(oAttacker, EFFECT_TYPE_MISDIRECTION_HEX))
{
#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," Attacker under misdirection hex: Hits are misses, crits are hits.", oTarget);
#endif

if (nRet == COMBAT_RESULT_HIT || nRet == COMBAT_RESULT_BACKSTAB)
{
nRet = COMBAT_RESULT_MISS;
}
else if (nRet == COMBAT_RESULT_CRITICALHIT)
{
nRet = COMBAT_RESULT_HIT;
}
}

#ifdef DEBUG
Log_Trace_Combat("combat_h.GetAttackResult"," ToHit Calculation: " +
" fAttack:" + ToString(fAttack) +
" = (fAttackRating: " + ToString(fAttackRating) +
" fAttackRoll:" + ToString(fAttackRoll) +
" (range penalty:" + ToString(fPenalties) + ")"+
" fFlanking: " + ToString(fFlanking) +
" fBonus(script): " + ToString(fBonus) +
")" , oAttacker, oTarget, LOG_CHANNEL_COMBAT_TOHIT );

Log_Trace_Combat("combat_h.GetAttackResult"," ToHit Calculation (2): " +
" fDefenseRating: " + ToString(fDefenseRating) +
" fCriticalHitModifier: " + ToString(fCriticalHitModifier) +
" bThreatenCritical: " + ToString(bThreatenCritical), oAttacker, oTarget, LOG_CHANNEL_COMBAT_TOHIT );

#endif

return nRet;
}
</dascript>

==== Combat_CheckBackstab ====

<dascript>
// -----------------------------------------------------------------------------
// Check if backstab conditions are true
// -----------------------------------------------------------------------------
int Combat_CheckBackstab(object oAttacker, object oTarget, object oWeapon, float fFlankingBonus)
{
// -------------------------------------------------------------------------
// If we we are a rogue
// -------------------------------------------------------------------------
if (!HasAbility(oAttacker, ABILITY_TALENT_HIDDEN_ROGUE))
{
return FALSE;
}

// -------------------------------------------------------------------------
// Only humanoid rigs have the backstab anim
// -------------------------------------------------------------------------
if (!IsHumanoid(oAttacker))
{
return FALSE;
}

// -------------------------------------------------------------------------
// And target is not immune
// -------------------------------------------------------------------------
if (HasAbility(oTarget, ABILITY_TRAIT_CRITICAL_HIT_IMMUNITY))
{
return FALSE;
}

// -------------------------------------------------------------------------
// And attacker does not use double strike mode
// -------------------------------------------------------------------------
if (IsModalAbilityActive(oAttacker, ABILITY_TALENT_DUAL_WEAPON_DOUBLE_STRIKE))
{
return FALSE;
}

// -------------------------------------------------------------------------
// We can only backstab if we are flanking.
// -------------------------------------------------------------------------
if (fFlankingBonus>0.0)
{
return TRUE;
}
else
{
/* Coup de grace*/
if (HasAbility(oAttacker, ABILITY_TALENT_BACKSTAB))
{
if (GetHasEffects(oTarget, EFFECT_TYPE_STUN))
{
return TRUE;
}
else if (GetHasEffects(oTarget, EFFECT_TYPE_PARALYZE))
{
return TRUE;
}
}

}

return FALSE;
}
</dascript>

==== Combat_GetFlankingBonus ====

This function is invoked during to hit determination and returns the magnitude
of the benefit the attacker may receive due to his facing and location relative to
the target.

<dascript>
// -----------------------------------------------------------------------------
// Determine the magnitude of positional bonuses for the attacker
// -----------------------------------------------------------------------------
float Combat_GetFlankingBonus(object oAttacker, object oTarget)
{

if (HasAbility(oTarget, ABILITY_TALENT_SHIELD_TACTICS))
{
if (IsUsingShield(oTarget))
return 0.0;
}

if (GetHasEffects(oTarget, EFFECT_TYPE_FLANK_IMMUNITY))
{
return 0.0;
}

float fAngle = GetAngleBetweenObjects(oTarget, oAttacker);
float fFactor = 0.0;

// -------------------------------------------------------------------------
// The maximum bonus from position is +15
// -------------------------------------------------------------------------
float fMaxModifier = 15.0;

// The attackers ability to flank is stored in a creature property
float fFlankingAngle = GetCreatureProperty(oAttacker, PROPERTY_ATTRIBUTE_FLANKING_ANGLE);

if (fFlankingAngle <= 10.0 ) /*old savegames have this at 10*/
{
fFlankingAngle = 60.0; // old savegames need this to avoid divby0 later
}
else if (fFlankingAngle>180.0)
{
fFlankingAngle = 180.0;
}

// -------------------------------------------------------------------------
// Combat movement expands the maximum bonus to +20
// -------------------------------------------------------------------------
if (HasAbility(oAttacker, ABILITY_TALENT_COMBAT_MOVEMENT))
{
fMaxModifier = 20.0;
}

if ( fMaxModifier <= 0.0 )
{
return 0.0;
}

if ( (fAngle>= (180.0 - fFlankingAngle) && fAngle<=(180.0 + fFlankingAngle )))
{
// Shield block negates flanking on the left.

int bShieldBlock = HasAbility(oTarget,ABILITY_TALENT_SHIELD_BLOCK);
int bUsingShield = IsUsingShield(oTarget);

if (!bShieldBlock || fAngle < 180.0 || (bShieldBlock && !bUsingShield) )
{
fFactor = (fFlankingAngle - fabs( 180.0 - fAngle))/fFlankingAngle;
}

}

// Only rogues get the full positional benefits on the battlefield,
// everyone else gets half
float fClassModifier = GetCreatureCoreClass(oAttacker) == CLASS_ROGUE?1.0f:0.5f;

return fFactor * fMaxModifier * fClassModifier;
}
</dascript>

[[Category: Scripts]]

Combat Rules

2009-10-28T02:36:28Z

Georg Zoeller: /* Backstab Determination */

'''This page is work in progress'''

=== Overview ===

This page describes the technical implementation and flow of combat logic in the game scripts.
It deals mostly with weapon based combat, for spells and abilities, please see [[Ability|Abilities]].

Note: The term 'property' used on this page refers to [[Creature Properties]].

=== Detailed Description ===

Combat in Dragon Age: Origin is handled mainly through scripts - the game engine itself has little knowledge of rule concepts such as 'Strength', 'Damage Modifier' or 'Armor Penetration'.

==== Hit Resolution ====

Hit resolution is implemented in the function [[combat_h.nss#Combat_GetAttackResult|Combat_GetAttackResult]] in the script library [[combat_h.nss]], which is invoked from the [[creature_core.nss]] script whenever an attack event is received. The function returns one of several [[COMBAT_RESULT|COMBAT_RESULT_*]] constants and handles messaging to the game engine which animation to play.

Overall, Dragon Age: Origin's combat system is 'hit heavy' as a targets armor does not modify it's chance of getting hit.

The simplified decision tree for to hit resolution is as follows:

<dascript>

if Target Is Placeable Object
return COMBAT_RESULT_HIT

if Target Displacement/Dodge < RandomF(100.0)
return COMBAT_RESULT_MISS

if Attacker Is Using BASE_ITEM_TYPE_STAFF
return COMBAT_RESULT_HIT

bHit = RandomF(100.0) < AttackRating - DefenseRating
bCrit = CheckCricital()
bBackstab = CheckBackstab()

if bHit
if HasEffect(attacker, EFFECT_TYPE_MISDIRECTION_HEX)
if bCrit OR bBackstab
return COMBAT_RESULT_HIT
else
return COMBAT_RESULT_MISS

if bBackstab
return COMBAT_RESULT_BACKSTAB
else
if bCrit
return COMBAT_RESULT_CRITICAL_HIT
else
return COMBAT_RESULT_HIT

else
return COMBAT_RESULT_MISS

</dascript>

===== Attack Rating =====

Attack rating includes:

* Base attack value (54.0f)
* + [[#Flanking Bonus Determination|Flanking Bonus]] (position based, modified by attacker and enemy talents and effects as well as shields. Rogues have a bonus here).
* + Distance based penalties (for ranged attacks)
* + Attacker's attack property value (this includes modifiers from buffs, etc.)
* + Any +attack item bonuses on the weapon that performs the attack.
* + Any external bonuses or penalties passed into the function (from talent scripts, etc.)
* + Difficulty setting based modifications

===== Defense Rating =====

Defense rating includes:

* Defender defense value or missile deflection if attack was ranged. This includes items, effects and magical bonus.
* Yes, this means that avoiding archers is hard for characters without a shield.
* Difficulty setting based modifications

===== Flanking Bonus Determination =====

* Flanking bonus is a floating point value that applies to both AttackRating and to the chance to score a critical hit.
* It is essentially a representation of close the character is to the best position when attacking the enemy (directly in the back)
* Various shield abilities on the target reduce or prevent the attacker from getting the bonus.
* The further away the character is from that position, the more the bonus is diluted.
* The magnitude of the bonus ranges from +0 to +15 (+20 with combat_movement) and is applied to AttackRating and partially (1+(FlankingBonus/5)) to critical hit chance.
* Most characters only flank 60 degrees in each direction, combat movement allows an increase to 90 degrees (the full back 180).
* Only rogues get the full flanking bonus, everyone else still gets half.
* The full logic is implemented in the function [[combat_h.nss#Combat_GetFlankingBonus|Combat_GetFlankingBonus]] in [[combat_h.nss]].

===== Backstab Determination =====

* Backstab is determined for each melee attack only.
* Backstab requires the attacker to have a flanking bonus > 0 (some talents waive this restriction)
* Only creatures with the Rogue [[Classes|Character Class]] may backstab. This is a class benefit.
* Only humanoid attackers can backstab (this includes darkspawn)
* The full logic is implemented in the function [[combat_h.nss#Combat_CheckBackstab|Combat_CheckBackstab]] in [[combat_h.nss]].

==== Damage Resolution ====

[[Category: Scripts]]

Console

2009-10-28T02:16:59Z

Georg Zoeller: /* Using the console in-game */

Up in the View Menu other windows you will see one called "Console".

This is where you would enter console commands that allow the toolset to interact with the game engine. It is mostly (if not always) used when you have an area open in the Area Editor.

The console commands were built to work with the game not the toolset but some of them do work with the toolset alone.

Your toolset will crash when using some of them so make sure you save your work before trying them.

== Using the console in-game ==

The in-game console is normally not accessible. To enable it run the game with a command line parameter "enabledeveloperconsole". Then, when the game is running, press the tilde key (~) to bring up the console. This is a prompt in the upper left corner of the screen. The console was used extensively in development for debugging and testing purposes, but in the finished version of the game there's only one console command available; "runscript".

The runscript command does exactly as it says - it runs a script, given as a name typed after a space. So for example:

<pre>
>runscript killallhostiles
</pre>

will cause the script named "killallhostiles" to be run.

You can pass the script additional parameters if you like. These parameters will be stored in the [[module]] variable RUNSCRIPT_VAR. RUNSCRIPT_VAR is a simple string, your script will need to parse it itself.

'''Caution:''' Using scripts like killallhostiles may break scripted plot situations, so you should avoid using it outside of custom content testing.

For example,

<pre>
>runscript usespecificobject demo100pl_lever
</pre>

calls the script "usespecificobject" and puts "demo100pl_lever" into the module RUNSCRIPT_VAR. The script can then call

<dascript>
string sParam = GetLocalString(GetModule(),"RUNSCRIPT_VAR");
</dascript>

to retrieve it.

If you need more than one parameter, pick a separator (a space is usually most appropriate) and split up the string in RUNSCRIPT_VAR appropriately. For example:

<dascript>
//parse out first parameter - the object to use.
nSpaceLoc = FindSubString(sParam," ");
sTemp = SubString(sParam,0,nSpaceLoc);
oDestination = GetObjectByTag(sTemp);
</dascript>

Combat Rules

2009-10-28T02:07:17Z

Georg Zoeller:

Combat Rules

2009-10-28T00:24:26Z

Georg Zoeller:

Combat Rules

2009-10-28T00:22:19Z

Georg Zoeller: /* Damage Resolution */

Combat Rules

2009-10-28T00:22:12Z

Georg Zoeller: /* Hit Resolution */

Combat Rules

2009-10-28T00:21:50Z

Georg Zoeller: Combat resolution formulas

Script.ldf

2009-10-27T23:21:48Z

Georg Zoeller:

Script.ldf is a header file that contains the engine-defined functions of the Dragon Age scripting language. These functions represent the lowest "level" that scripting has access to and many of them are only routinely accessed via wrapper functions defined in core include files.

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; width:100%; height:100%"
|-
| valign="top"|
<h2 style="margin:0; background:red; font-size:150%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#fff; padding:0.2em 0.4em;">Caution</h2>
This file should never be modified by content creators.
|}

[[Category:Scripts]]

Classes

2009-10-27T23:16:17Z

Georg Zoeller: /* Description */

''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'''||'''IntAdjust'''||'''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 through the Character Creation UIs, use the data in [[CLA_base.xls]] to construct the character based on the player's choices and 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: Scripting]]

CLA base.xls

2009-10-27T23:11:13Z

Georg Zoeller:

This 2da file is used to define the [[Classes|Character Classes]] available in Dragon Age: Origins.

== CLA_data worksheet ==

{{2da start|CLA_data}}
{{2da column| Label | string | }}
{{2da column| NameStrref |int| the reference ID number of a string in the string table that has this class' name in it. Use the [[String Editor]] to view strings by ID.}}
{{2da column| PluralStrref | int | a string in the string table with the class' name, pluralized}}
{{2da column| LowerStrref | int | }}
{{2da column| DescStrref| int | A short description of the class.}}
{{2da column| TooltipStrref |int| Tooltip text for the class.}}
{{2da column| Icon | resource | Icon used to represent this class in character generation.}}
{{2da column| Constant | string| The name of the constant used in scripts to refer to this class. eg, "CLASS_Warrior".}}
{{2da column| Package | int | }}
{{2da column| BaseHealth | float | Start health }}
{{2da column| bUsesMana |int| 0 sets this class to use stamina for its abilities, 1 sets it to use mana.}}
{{2da column| BaseManaStamina | float | Start mana / stamina }}
{{2da column| DepletableProgression | float | How much stamina/mana the class gets every level after 1. }}
{{2da column| StrAdjust |float| a bonus this class gets to starting strength attribute }}
{{2da column| ConAdjust |float| a bonus this class gets to starting constitution attribute }}
{{2da column| WillAdjust |float| a bonus this class gets to starting willpower attribute }}
{{2da column| MagAdjust |float| a bonus this class gets to starting magic attribute }}
{{2da column| IntAdjust |float| a bonus this class gets to starting cunning attribute }}
{{2da column| DexAdjust |float| a bonus this class gets to starting dexterity attribute }}
{{2da column| MinLevel |int| The prerequesite level a character must be to take this class. If it's greater than zero, it's an advanced class. '''Note: this column is a remnant of when specialization classes were included in the base class 2DA; this approach is no longer used.'''}}
{{2da column| BaseClass |int| For advanced classes, this sets which base class it is an advanced class of. The number here refers to the ID of the row that it's a advanced class for. '''Note: this column is a remnant of when specialization classes were included in the base class 2DA; this approach is no longer used.'''}}
{{2da column| BaseAttack | float | }}
{{2da column| BaseDefense | float | }}
{{2da column| DefensePerLevel | float | }}
{{2da column| HealthPerLevel | float | }}
{{2da column| LevelsPerAbility | int | How many levels before gaining an ability. Example. If a 3 is here, it means you get an ability on every level divisible by 3}}
{{2da column| LevelsPerSkill | int | How many levels before gaining a skill. Example. If a 3 is here, it means you get an ability on every level divisible by 3}}
{{2da column| DamagePerLevel | float | This was a fudge added to the rule system to diminish the power that Strength's bonus damage had. Basically, this is just added to the base damage bonus of the character.}}
{{2da column| StartingAbility1 | int | This is an index into the ABI 2da. If its valid it will add that ability to the character when you first take a level with the class. This is used for the hidden talent that all classes get. This talent is used in subsequent prereq checks}}
{{2da column| StartingAbility2 | int | This is an index into the ABI 2da. If its valid it will add that ability to the character when you first take a level with the class.}}
{{2da column| PlayerClass |int| Determines whether this class can be taken by a player.}}
{{2da column| CharGenLabel| string| }}
{{2da column| Achievement | string| Required Achievement to unlock this class permanently}}
{{2da end}}
[[Category:2DAs]]

Event keyword

2009-10-27T22:52:11Z

Georg Zoeller: /* Persistence */ Removed section, these scripting functions are not used.

__NOTOC__
The '''event''' type represents a package of information that can be passed around in the game to trigger some behaviour.

== Constructor ==

A constructor is a function that creates an instance of a [[DAScript_types|dascript type]].

The constructor for an event is [[Event]].

== Literals ==

A literal is a textual representation of a particular value of a type.

There is no literal for an event.

== Conversion ==

There is no explicit or implicit conversion to or from an event.

== Examples ==

<dascript>
void main()
{
// uninitialised
event evDefault;

// initialised using the constructor
event evConstructed = Event(EVENT_TYPE_USE);

// initialised using a function
event evCurrent = GetCurrentEvent();
}
</dascript>

== Remarks ==

Events are usually passed off to an [[object (dascript type)|object's]] [[event script]] for handling, but there are a few engine-only event types that are not exposed to the end-users.

Scripting Events have an integer type, target object, a time delay and a package of parameters (arbitrary number of [[int (dascript type)|ints]], [[object (dascript type)|objects]], [[float (dascript type)|floats]] and [[string (dascript type)|strings]]). Certain event types will be defined by the engine and referenced as #defines in the scripts.

Events are handled in the scripting language with the following types of commands:
* Event() Constructor — Scripters can create events of any type and signal them to other objects
* Signal Event commands — Events can be signalled to a single object, by proximity or to all objects with a certain group id
* Parameter access — All of the parameters on an event can be get and set through scripting.
* Event handling — Events can be passed to other script files through the HandleEvent command. This command will be run inline so that hierarchies of event-handling behaviour can be built.

A typical event-handling script would have the form

<dascript>
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev); //extract event type from current event
int nEventHandled = FALSE; //keep track of whether the event has been handled
switch(nEventType)
{
case EVENT_TYPE_AREALOAD_SPECIAL:
{
...
nEventHandled = TRUE; //set this if no further action is required for this event
break;
}
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_AREA_CORE);
}
}
</dascript>

In the event that you want to intercept some events but leave others to be handled by a default script (for example if you're overriding one aspect of a creature's event response but the rest of the default creature_core responses responses are fine) you can pass execution to the default script with the following:

<dascript>
HandleEvent(ev, RESOURCE_SCRIPT_CREATURE_CORE);
</dascript>

(constants for referencing core script resources are available in the "global_objects_h" include file)

Below is a list of the event types that are defined within the core resources:

* '''Perception'''
** [[EVENT_TYPE_PERCEPTION_APPEAR]] - A creature enters the perception area of creature receiving the event
** [[EVENT_TYPE_PERCEPTION_DISAPPEAR]] - A creature exits the perception area of creature receiving the event
* '''Effects'''
**[[EVENT_TYPE_APPLY_EFFECT]] - an effect is applied to the receiving object
**[[EVENT_TYPE_REMOVE_EFFECT]] - an effect is removed from the receiving object
* '''Combat'''
**[[ EVENT_TYPE_COMBAT_INITIATED ]] - Fires whenever the attack command is added into the command queue. Used to set combat mode and combat camera/music. Also fires by scripting to trigger combat after being attacked or an ally is attack.
**[[ EVENT_TYPE_COMBAT_END ]] - a creature doesn't perceive any more hostiles.
**[[ EVENT_TYPE_MELEE_ATTACK_START ]] - {{undocumented}}
**[[ EVENT_TYPE_COMMAND_PENDING ]] - Fires at the beginning of the attack part of the attack command OR at the beginning of an ability execution.
**[[ EVENT_TYPE_COMMAND_COMPLETE ]] - creature finishes doing a command(attack, special ability, spell, conversation, etc)
**[[ EVENT_TYPE_ATTACK_IMPACT ]] -- 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').
**[[ EVENT_TYPE_ATTACKED ]] - another object tried attacking this creature using melee/ranged weapons (hit or miss), talents or spells.
**[[ EVENT_TYPE_ALLY_ATTACKED ]] - an ally has received the ATTACKED event. An ally is an object with the same group ID.
* '''Damage and death'''
**[[ EVENT_TYPE_DAMAGED ]] - an object loses 1 hit point or more
**[[ EVENT_TYPE_DOT_TICK ]] - Damage over time tick event.
**[[ EVENT_TYPE_DYING ]] - a creature received the killing blow.
**[[ EVENT_TYPE_DEATH ]] - creature or placeable have the death effect applied (regardless of hitpoints)
**[[ EVENT_TYPE_RESURRECTION ]] - Creature resurrected.
**[[ EVENT_TYPE_TEAM_DESTROYED ]] - Fires when an entire team of creatures is destroyed.
* '''Inventory '''
**[[ EVENT_TYPE_INVENTORY_ADDED ]] - An item is added to the personal inventory of the object receiving the event or the party inventory.
**[[ EVENT_TYPE_INVENTORY_REMOVED ]] - An item is removed from the personal inventory of the object receiving the event or the party inventory.
**[[ EVENT_TYPE_EQUIP ]] - The current creature has equipped an item
**[[ EVENT_TYPE_UNEQUIP ]] - The current creature has unequipped an item
**[[ EVENT_TYPE_CAMPAIGN_ITEM_ACQUIRED ]] - items with the ITEM_ACQUIRED_EVENT_ID variable set are picked up.
**[[ EVENT_TYPE_INVENTORY_FULL ]] - {{undocumented}}
**[[ EVENT_TYPE_OUT_OF_AMMO ]] - {{undocumented}}
* '''Movement'''
**[[ EVENT_TYPE_BLOCKED ]] - The current creature's path has been blocked while moving by a creature or door. This event will NOT fire when blocked by placeables who can not change the walk mesh or terrain.
**[[ EVENT_TYPE_ENTER ]] - A creature enters the object receiving the event
**[[ EVENT_TYPE_EXIT ]] - A creature exits the object receiving the event
**[[ EVENT_TYPE_REACHED_WAYPOINT ]] - {{undocumented}}
* '''Traps'''
**[[ EVENT_TYPE_APPROACH_TRAP ]] - Trap triggered and the creature receiving this event should approach the trap
**[[ EVENT_TYPE_TRAP_ARM ]] Sent by script to request that a trap arm itself.
**[[ EVENT_TYPE_TRAP_TRIGGER_ENTER ]] - {{undocumented}}
**[[ EVENT_TYPE_TRAP_DISARMED ]] - {{undocumented}}
**[[ EVENT_TYPE_TRAP_TRIGGER_ARMED ]] - {{undocumented}}
**[[ EVENT_TYPE_TRAP_TRIGGER_EXIT ]] - {{undocumented}}
**[[ EVENT_TYPE_TRAP_TRIGGERED ]] - {{undocumented}}
* '''Game state events'''
**[[ EVENT_TYPE_SPAWN ]] - an object spawns into the game. This event can fire only once per game for each object, regardless of save games.
**[[ EVENT_TYPE_MODULE_START ]] - The module starts. This can happen only once for a single game instance.
**[[ EVENT_TYPE_MODULE_LOAD ]] - The module loads from a save game. This event can fire more than once for a single module or game instance.
**[[ EVENT_TYPE_AREALOAD_SPECIAL ]]- for playing things like cutscenes and movies when you enter an area, things that do not involve AI or actual game play
**[[ EVENT_TYPE_AREALOAD_PRELOADEXIT ]] - for things you want to happen while the load screen is still up, things like moving creatures around
**[[ EVENT_TYPE_AREALOAD_POSTLOADEXIT ]] - fires at the same time that the load screen is going away, and can be used for things that you want to make sure the player sees.
**[[ EVENT_TYPE_AREALOADSAVE_POSTLOADEXIT ]] - fires at the same time that the load screen is going away, but only when loading a savegame.
**[[ EVENT_TYPE_GAMEMODE_CHANGE ]]
**[[ EVENT_TYPE_DELAYED_GM_CHANGE ]]
**[[ EVENT_TYPE_SET_GAME_MODE ]]
*'''Plots'''
**[[ EVENT_TYPE_SET_PLOT ]] - A plot is setting a plot flag
**[[ EVENT_TYPE_GET_PLOT ]] - A plot is setting a plot flag
*''' Dialogue'''
**[[ EVENT_TYPE_DIALOGUE ]] - An object tries to initiate dialog with the object receiving the event, either by clicking or by scripting
**[[ EVENT_TYPE_DELAYED_SHOUT ]] - Used to fire a dialog shout every few seconds.
**[[ EVENT_TYPE_AMBIENT_CONTINUE ]] - conversation ends or player is nearby to resume ambient behaviour
*'''Party management'''
**[[ EVENT_TYPE_PARTYMEMBER_ADDED ]] - Party member added to active party using the party GUI
**[[ EVENT_TYPE_PARTYMEMBER_DROPPED ]] - Party member removed from active party using the party GUI
**[[ EVENT_TYPE_PARTYPICKER_CLOSED ]] - {{undocumented}}
**[[ EVENT_TYPE_PARTY_MEMBER_HIRED ]] - Fires first time a party member is added to the party. For plot followers: follower recruited (added to pool). For other followers: UT_Hire called
**[[ EVENT_TYPE_PARTY_MEMBER_FIRED ]] - Fires when an active or locked-active party member is removed from the active party
**[[ EVENT_TYPE_PARTY_MEMBER_RES_TIMER ]] - Resurrection timer used if a creature dies in explore mode.
**[[ EVENT_TYPE_GIFT_ITEM ]]- {{undocumented}}
**[[ EVENT_TYPE_MODULE_HANDLE_FOLLOWER_DEATH ]] - {{undocumented}}
**[[ EVENT_TYPE_MODULE_HANDLE_GIFT ]] - {{undocumented}}
**[[ EVENT_TYPE_SUMMON_DIED ]] - {{undocumented}}
* '''Character generation and level advancement '''
**[[EVENT_TYPE_CHARGEN_START]] and [[EVENT_TYPE_CHARGEN_END ]] - A range of event constants (nEvent >= EVENT_TYPE_CHARGEN_START && nEvent <= EVENT_TYPE_CHARGEN_END) that occur during character generation.
**[[ EVENT_TYPE_PLAYER_LEVELUP ]] Fired by sys_rewards_h.RewardXP (the levelup system)
**[[ EVENT_TYPE_PLAYERLEVELUP ]]
**[[ EVENT_TYPE_CHARGEN_AUTOLEVEL ]]
**[[ EVENT_TYPE_MODULE_CHARGEN_DONE ]]
**[[ EVENT_TYPE_GUI_OPENED ]] - GUI tutorial calls
* '''World map'''
**[[ EVENT_TYPE_TRANSITION_TO_WORLD_MAP ]] - Player uses the generic transition system to open the world map
**[[ EVENT_TYPE_WORLD_MAP_CLOSED ]]
**[[ EVENT_TYPE_WORLD_MAP_USED ]] - the player clicks on a destination in the world map
** [[ EVENT_TYPE_BEGIN_TRAVEL ]]
** [[ EVENT_TYPE_WORLDMAP_PRETRANSITION ]]
**[[ EVENT_TYPE_WORLDMAP_POSTTRANSITION ]]
**[[ EVENT_TYPE_FINISH_TRAVEL ]]
*''' Found in placeable_core '''
**[[ EVENT_TYPE_PLACEABLE_ONCLICK ]] player clicks on object.
**[[ EVENT_TYPE_USE ]]
**[[ EVENT_TYPE_UNLOCKED ]] Sent by script when placeable is unlocked.
**[[ EVENT_TYPE_SET_OBJECT_ACTIVE ]] Sent by script to change active state. Needed since CommandDoFunction was removed and we're using CommandDoEvent
**[[ EVENT_TYPE_PLACEABLE_COLLISION ]] player collides with object (if EnableCollisionEvent column in placeables.xls is non-zero).
**[[ EVENT_TYPE_POPUP_RESULT ]]
* '''Found in rules_core'''
**[[ EVENT_TYPE_ITEM_ONHIT ]]
**[[ EVENT_TYPE_CONFUSION_CALLBACK ]]
**[[ EVENT_TYPE_DESTROY_OBJECT ]]
* '''Found in player_core'''
**[[ EVENT_TYPE_HEARTBEAT ]]
**[[ EVENT_TYPE_LOAD_TACTICS_PRESET ]]
*'''Spellcasting'''
**[[ EVENT_TYPE_ABILITY_CAST_START ]]
**[[ EVENT_TYPE_ABILITY_CAST_IMPACT ]]
**[[ EVENT_TYPE_CAST_AT ]]
**[[ EVENT_TYPE_COMBO_IGNITE ]]
**[[ EVENT_TYPE_SPELLCASTAT ]]
**[[ EVENT_TYPE_SPELLSCRIPT_CAST ]]
**[[ EVENT_TYPE_SPELLSCRIPT_DEACTIVATE ]]
**[[ EVENT_TYPE_SPELLSCRIPT_IMPACT ]]
**[[ EVENT_TYPE_SPELLSCRIPT_PENDING ]]
* '''Proving events'''
**[[ EVENT_TYPE_PROVING_ENTER ]]
**[[ EVENT_TYPE_PROVING_EXIT ]]
**[[ EVENT_TYPE_PROVING_LOSE ]]
**[[ EVENT_TYPE_PROVING_START ]]
**[[ EVENT_TYPE_PROVING_WIN ]]
* '''Debugging'''
** [[ EVENT_TYPE_DEBUG_KICKSTART_AI ]]
**[[ EVENT_TYPE_DEATH_RES_PARTY ]]
**[[ EVENT_TYPE_DEBUG_RESURRECTION ]]
* '''Stats'''
**[[ EVENT_TYPE_STAT_REGEN ]]
**[[ EVENT_TYPE_MANA_STAM_DEPLETED ]]
* '''Miscellaney'''
**[[ EVENT_TYPE_CLICK ]]
**[[ EVENT_TYPE_CUSTOM_COMMAND_COMPLETE ]]
**[[ EVENT_TYPE_FAILTOOPEN ]]
**[[ EVENT_TYPE_HANDLE_CUSTOM_AI ]]
**[[ EVENT_TYPE_INVALID ]]
**[[ EVENT_TYPE_LISTENER ]]
**[[ EVENT_TYPE_LOCKED ]]
**[[ EVENT_TYPE_QA_EVENT ]]
**[[ EVENT_TYPE_QA_EVENT_BLA ]]
**[[ EVENT_TYPE_STEALING_FAILURE ]]
**[[ EVENT_TYPE_STEALING_SUCCESS ]]
**[[ EVENT_TYPE_UNIQUE_POWER ]]

== Shouts ==

Shouts (events) are used to make creatures communicate with one another. This is a list of all the shouts referenced in the AI documentation.

[[ Creature Shouts ]]

*SHOUT_TYPE_WASATTACKED When I am attacked, signal this event for all allies. What do the allies do? They will go into combat round, not specifically targeting this attacker but becoming combat ready.
*SHOUT_TYPE_SAWENEMY Attack enemy.
*SHOUT_TYPE_KILLEDME Attack enemy.
*SHOUT_TYPE_SWITCH_MELEE Will switch to melee weapons, useful for certain plot situations
*SHOUT_TYPE_WAKE_UP Any creature that hears this shout will wake up, if sleeping. This shout needs to be manually called.
*SHOUT_TYPE_FOUND_SOMEONE (YaronToDo) a scout sees someone they broadcasts this event. Allies go here. (NOT DONE)

[[ Commander-Specific Orders ]]

*SHOUT_TYPE_FINISHHIM Attacks a specified enemy till they are dead. A Commander issues order generally.
*SHOUT_TYPE_ATTACK_WIZARD (YaronToDo) Starting targeting wizard class enemies instead of others.
*SHOUT_TYPE_FLANK Rogues will get into a flanking position to an appropriate enemy
*SHOUT_TYPE_SWITCH_RANGED Will randomly choose one ally and ask them to switch to a ranged weapon. This is mostly done to even out the number of participants in melee battle for animation purposes (closer to even the sides are, the better things look)

== See Also ==

[[IsEventValid]], [[HandleEvent]], [[SignalEvent]]

[[Category: DAScript types]]

Ability

2009-10-27T22:48:03Z

Georg Zoeller: /* Q: What does 'asymmetric rules system' mean ? */

=== Overview ===
The Ability System is used to handle Spells, Talents, Skills, and Item Abilities in Dragon Age.

=== Detailed Description ===

Spells, Talents, Skills and item abilities all use the same backend in the game, a mostly script implemented system relying heavily on two dimensional data arrays.

The most important 2da file for abilities is '''[[ABI_base.xls]]''', as it defines each ability and all aspects of execution and handling in both scripting and engine code.

{| style="margin:0; background:#f5faff; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em; width:100%; height:100%"
|-
|'''Ability Design Notes'''

When creating an ability in Dragon Age: Origins, we generally stick to the following guidelines

* Keep it useful.
Some constant benefits (such as an increase in Attack or Defense) stay useful for the duration of the game as the progression of the related properties are slow.
For other effects, such as damage, a constant value would mean that the ability will become progressively worse through the game as damage needed to drop enemies increases from level to level. In such cases, the ability should be tied in some fashion to a Spellpower (for spells) or another relevant (such as cunning for rogues) to ensure they stay useful throughout the game.

* No repetition.
Each ability in Dragon Age: Origins is unique. No incremental abilities such as 'fireball I, fireball II, etc.'. Skills are exempt from this rule. Remember that the Damage Types dramatically alter the actual effect of an ability (such as lightning always draining stamina alongside doing damage), so having similar damaging abilities in different trees is usually fine.

* Thematic matching.
Abilities within the same chain should follow a common theme.

* Avoid binary abilities. Design hit heavy.
Avoid abilities that are hit-or-miss. Generally, abilities should hit whenever possible and use target side mitigation of effects (resistance checks, damage mitigation) instead of 'hit or miss' mechanics. Melee abilities may use the normal attack resolution routines but should always perform their attacks at a bonus. Use rank based mitigation and resistances to allow for very powerful effects that do not trivialize boss battles.

* Use meaningful effects
Abilities should always be worth it. Don't do minor effects (+1 attack). The player should always be able to see the effect of the ability in game (not necessarily visually, but at least through increased damage, etc.). The first ability in a chain should, whenever possible, be active. The fourth ability in a chain should always have the biggest 'bang-for-the-buck' factor. Abilities lower in the chain should have shorter cooldowns. Do not allow instant death on bosses and elite bosses.

* Avoid 'zero-sum' abilities
When possible, avoid 'zero-sum' abilities that trade a penalty for a benefit (e.g. increase defense but decrease attack). There are a number of these abilities that are valid (such as aim), but balancing them and keeping them useful is hard and requires a lot of work. This obviously does not apply to drastic abilities such as blood magic.

* No emulation of defining class capabilities
Never ever grant a basic class capability from one class to another class via abilities. This means no invisibilityor magical unlock spells for mages, as these are defining capabilities of the rogue class. No weapon talents for mages. No magic spells or large, targeted area of effects for warriors or rogues. Items might blur this line if the cost is balanced properly (e.g. grenades).

|}

==== Basic Ability Types ====

Abilities are divided into 4 subtypes, as defined in the 'abilitytype' column in abi_base.xls:

* Talents - Abilities used by warriors and rogues, usually non magical in nature. (abilitytype=1)
* Spells - Abilities used by mages, either spell or passive abilities. (abilitytype=2)
* Skills - Abilities usable by all classes, such as Survival and Combat training (abilitytype=3).
* Items - Abilities present on an item that are triggered when the item is used on the quickbar. (ability_type=4)

Note: Talents do not show up on mages and spells do not show up on rogue or warrior characters, so to create abilities that can be used by all classes, abilitytype 3 (Skill) must be used. To define under which heading an ability shows up on the character's talent/spell page, the field 'guitype' is used. It resolves against guitype.xls which lists all known headings.

There are 3 basic ability types in the game, defined by the field 'use_type' in [[ABI_base.xls]].

'''Passive Abilities'''

Passive abilities (use_type = 3) grant persistent or conditionally persistent bonuses or penalties to the creature that has the ability.

A passive ability may grant up to 3 modifications to creature properties (properties.xls). Those modifications are defined in the passive_abilities worksheet of abi_base.xls and linked to the ability through the passive_id column in abi_base.xls.

Additionally, the bonuses of an ability can be made conditional on the character's current 'wield mode' (2-handed, dual, weapon & shield, or universal) through the conditional integer field on the passive_abilities worksheet.

Finally, a number of passive abilities do not define any property modifications in passive_abilites but instead have checks coded against their Ids (e.g. HasAbility(oCreature, ABILITY_TALENT_LETHALITY)) directly in the combat resolution scripts. The mere presence of the ability on a creature causes a different code path to be taken in the scripts in those cases.

Note that passive_ability benefits are not limited to abilities with use_type 3. Some active abilities also grant additional property modifying benefits to the owner.

'''Sustained Abilities'''

Sustained abilities (use_type = 2) are turned on and off per character and, while turned on, grant effects or property modifications to the user.
Most 'buffs' are implemented this way.

Only members of the player's party are using sustained ability as the code overhead required to track them is too expensive to be used on monsters that only exist to die in an encounter with the player's party. (These creatures use duration based effects to emulate similar abilities instead).

Most sustained abilities follow the same pattern:
* They do not have any activation cost, encouraging tactical use of buffs.
* They increase the users [[Fatigue]] property, therefore increasing the activation cost of all other abilities.
* They reduce the users maximum available mana or stamina by a constant value.
* They use cooldown to prevent the user from being too opportunistic with their use.
* Some abilities shut down when the user reaches 0 mana/stamina. Very powerful abilities (such as Momentum) have an associated stamina/mana drain effect to limit their use to a short or medium period of time. Creative item / buff use can be used to increase the length such an ability can be sustained.

The benefits from sustained abilities are calculated when the ability is activated, so if a character levels up or otherwise changes stats that influence the magnitude of a sustained ability will not update until the ability is reactivated the next time.

Some sustained abilities (such as Flaming Weapons) are active 'party-wide' - the caster not only sustains the ability on himself but on all his party members as well. This is controlled by the 'bPartyWide' flag in abi_base.xls. Due to implementation limitations, party members who die or otherwise enter/exit the current party will not be affected by these abilities until they are recast. (we put low cooldown times on these abilities for that very reason).

{| style="margin:0; background:#f5faff; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em; width:100%; height:100%"
|-
|'''Gameplay Design Note'''
* Unlike in games like Baldur's Gate, the system in DA: Origins is designed to encourage tactical use of buffs over strategical. We wanted to put an emphasis on the player making smart choices during an encounter vs. the player guessing which buffs might be useful ahead of time or having to employ save-die-reload to find out.

* It is generally wise to run only one or two buffs all around and activate additional buffs only when needed.
|}

'''Activated Abilities'''

Activated abilities (use_type = 4) are abilities that instantly execute their effect (see Targeting Behavior below). Most melee talents or targeted spells fall in this category. There are several sub-types of activated abilies, such as

* Targeted, single target spells and talents (such as Winter's Grasp or Flurry)
* Ground targeted abilities (such as Blizzard or various Glyphs)
* Self targeted activated abilities.

==== Targeting Behavior ====

An abilities targeting behavior is controlled by several settings in abi_base.xls

'''AutoTarget''' is a boolean field that defines how the UI resolves targeting.

{| border="1"
|-
| 0 || The UI will always bring up a targeting cursor.
|-
| 1 || The UI will only produce a targeting cursor if no suitable target is currently selected. e.g if the player currently has a hostile creature targeted and if the spells TargetType includes 0x4 (hostile), the ability will trigger immediately, not producing a targeting cursor. Most single target spells and talents use this setting.
|}

Regardless of AutoTarget setting, the UI will never produce a targeting cursor if an ability is type 0x1 (self) -

'''TargetType''' is a bit mask derived from the following table and controls the behavior of the UI's targeting cursor.

{| border="1"
|-
|'''Bitmask''' || '''Effect'''
|-
| 0x1 || Self
|-
| 0x2 || Friendly Creature
|-
| 0x4 || Hostile Creature
|-
| 0x8 || Placeable Object
|-
| 0x10 || Area of Effect Object (deprecated)
|-
| 0x20 || Ground (see details)
|-
| 0x40 || Dead Body (deprecated)
|-
| 0x80 || Party Member
|}

'''AutoDraw''' is an integer boolean field that defines how a character's weapons are handled when the ability is triggered.

{| border="1"
|-
| 0 || The ability will not affect the player's weapon sheath status.
|-
| 1 || The engine will force the player to draw/unsheathe his weapon before executing the ability. This is used for most bow and melee weapon abilities.
|-
| 2 || The engine will force the player to stow away any non staff melee weapons before executing the ability. This is used to ensure that no inappropriate animations play with weapons drawn (e.g. the player conjuring with a sword clipping through his body) and to discourage switching between melee and spellcasting on the fly.
|}

==== Balancing (Cost, Cooldown, etc) ====

Abilities in Dragon Age are balanced along several vectors, most of which boil down to simple 'use frequency'. As a general rule of thumb, the more specialized and limited the effect of an ability is, the more outrageously powerful an ability can be.

Use frequency of abilities can be adjusted by modifying the following field in abi_base.xls

* Cost: This is the simple mana (spells) or stamina (talents) activation cost of an ability. It is subtracted when the conjure phase of the spell has succesfully completed (e.g. no cost for spell interruptions). Without sufficient resources to cover activation cost, the UI will not allow the player to execute the ability. The value is a constant integer and is multiplied with 1+(Current Fatigue) of the caster.

* Cooldown: Cooldown is a constant float in seconds that defines how long the player has to wait after the successful activation of an ability until he can use it again. For abilities that apply duration based debuffs or effects to a target, cooldown is usually set slightly higher than the duration of the effect to avoid stacking by the same caster.

* Upkeep: Defines how much mana or stamina is removed from the casters overall pool while a sustained ability is active. This naturally limits the number of sustained abilities present on a creature and ensures that the more beneficial buffs are active on the caster, the less mana is available for immediate use.

* [[Fatigue]]: Fatigue affects use frequency only indirectly, but it prevents characters from stacking too many buffs on each other, as each sustained ability active usually adds around 5-10% fatigue to the caster.

* Mana/Stamina drain: By reducing the mana/stamina regeneration rate on a creature, the duration for which a sustained ability can be used can be restricted. This mechanic is used only for the most powerful sustained abilities in the game, which are flagged to turn off when the caster sustaining them reaches 0 mana/stamina.

Other balancing vectors:

* AoESize and AoeShape: Area of effect spells that deal friendly fire are location and situation restricted on normal+ difficulty (hard+ on the consoles). Since dropping an Inferno on your own party members is hardly a good idea in most cases, the usefulness of the spell becomes restricted to careful positioning and the earlier stages of combat.

* Threat Generation: Abilities apply threat not just by damage but often by activation. Higher activation threat of an ability can balance out outrageously powerful effects by making it harder for the player to use the spell. The prime example is the Walking Bomb kind of spells which deal excellent damage, but, on higher difficulties, also make the targets very very angry at the caster. Using these spells effectively often requires a tactical approach by the player, thus limiting their universal usefulness and offsetting their very powerful effects.

* Threat Removal: Some abilities are designed to only provide a short term benefit (Such as 3s stun on Mindblast) but offset their weakness by removing threat from the caster, often by reinitializing the threat tables on the target, causing enemies to randomly seek new targets.

* Conjure time: Spells with a conjure time of 1+ (Speed in abi_base.xls) can be interrupted by damage, limiting their usefulness in melee situations or when only one party member remains on the battlefield. Many of the very powerful Area of Effect type spells use this feature. Most activated spells have a conjure time of 0, making them instant cast.

* Range: Lower ranges force the ability user into potentially more dangerous situations, adding additional risk to the use of an ability.

=== Q&A ===

==== Q: Where do we find the exact formula for abilities ? ====

A: Due to most abilities being unique, the only place to find the exact details on each spell is in the scripts. While a lot of data can be glanced from abi_base.xls, a lot of the detailed mechanics are very different between abilities and can only be found in the appropriate spellscript. The *_constant.nss files hold some basic values, but often get further modified in the scripts.

This is also one of the reasons why some elements of a talent are not displayed in the UI description in game. While we can calculate cost and cooldown based on the casting character and his fatigue and other properties (and consequently display it), we can usually not calculate damage or duration as they are mitigated on the target creature:

Displaying those values results in very misleading information (e.g. while damage seems to be higher on one ability, the mitigation mechanisms and unique side effects of another ability will make it just as good or better - in certain situations) and it turned out to be better to provide the player with general guidance than the misleading information.

==== Q: What is Spellpower and how does it interact with abilities ====

Spellpower is probably the most important stat for a mage character (and only exists on mage characters). It is calculated as max(Magic - 10,0) and therefore increases by one point for every point a mage spends on his Magic attribute.

Most mage spells benefit directly from higher spellpower by increased damage, effect magnitude and duration. It also plays a role in a mages ability to overcome mental or physical resistance on a target (where applicable). The actual impact of spellpower on an ability varies from spell to spell but the most common construct equates to something like 1% increase in spell potency per point of Spellpower. Thus, items and spells that increase spellpower are very powerful as they increase the potency of every spell the mage can cast.

Spellpower is the only factor that causes an increase of a spells potency over time, so a level 20 mage with neglected the Magic attribute would be much less powerful than a mage that didn't neglect Magic.

Some examples:

* The damage potential for Winter's Grasp is calculated as (100.0f + GetCreatureSpellPower(stEvent.oCaster)) * 0.36f;
* The healing potential for the heal spell is calculated as (100.0f + GetCreatureSpellPower(stEvent.oCaster)) * 0.40f;
* The damage over time component of blizzard is executed as ApplyEffectDamageOverTime(a[i], oCreator, ABILITY_SPELL_BLIZZARD, (100.0f + GetCreatureSpellPower(oCreator)) * 0.1, (BLIZZARD_INTERVAL_DURATION - 0.5f), DAMAGE_TYPE_COLD);

Note that these formulas only list the raw damage potential and do not take into account the effects of damage types, difficulty, rank, resistances, magical shields and any other mitigating factors on the target or enhancing factors on the caster. This means that just comparing the numbers will not give you an idea which spell is better or worse.

For non-mage spells and abilities, spellpower is often substituted by an appropriate other construct (such as max(Cunning-10,0) for rogue abilities).

==== Q: Can we have the damage formula for abilities ? ====

A: There is no damage formula for abilities, as mentioned before, each ability follows their own rules.

In general, talent damage is based on the weapon being used (e.g. Assault does 3 melee attacks that deal weapon damage with some additional bonuses) and are modified by external cirumstances such as location, critical chance and ability to deliver a backstab and are mitigated by armor on the target.

Spells deal damage of different damage types following a rough rule of (Constant * (Spellpower / Variable)) / [Variables] ) + Modifiers but this only tells part of the story as actual damage is dependent on the target, it's resistances, rank and a number of other factors.

Some additional factors affecting spell damage are:

* damage resistance.
* magical shields.
* difficulty level.
* elemental damage bonuses from spells or items
* Environmental conditions (frozen targets take less damage from fire, etc.)

==== Q: What are the differences between damage types? ====

A: Creatures have variable damage resistances based on their type and rank. Dragons might get 60% less damage from fire (60% fire resistance), other creatures will have different immunities. Additional effects are:

* Electricity: In addition to normal damage, these also reduce the targets stamina (but not mana) by the same amount, making them very effective boss killers.

* Fire: Cancels Cold based damage over time effects and applies damage over time.

* Cold: Cancel Fire based damage over time effects and often is accompanied by slow or slipping effects.

* Spirit: There are very few ways of increasing spirit resistance in the game, so spells dealing spirit damage are universally useful...

* Nature: Rarely found on spells. Many creatures are resistant to this.

(This should probably go on its own wiki page)

==== Q: Are sustained abilities mutually exclusive ? ====

A: There is a very limited number of sustained abilities that are mutually exclusive, usually because it makes sense. Mutually exclusive abilities cancel each other upon activation.

* Shield stances (Shield Wall, Shield Cover, Shield Defense) are mutually exclusive.
* Archery stances (Aim, Rapid Fire, Defensive Fire) are mutually exclusive.
* Shapeshifting forms are (Sorry, no Bear-Wolfspider) are mutually exclusive.
* Weapon Enhancement spells are too, but only for the same caster (so two mages can run two different weapon enhancements if they want to).
* Bard Songs are mutually exclusive.
* The Death Syphon and Death Magic spells are mutually exclusive.

Technically, all abilities in abi_base.xls that share the same 'condition_group' value are mutually exclusive.

==== Q: What are the rules for stacking effects and damage ? ====

A: The general rules of stacking for abilities are:

* Identical effect from different abilities stack (e.g. getting +10 attack from one ability and +10 attack from another nets +20 attack).
* The effects of identical abilities stack as long as they are from different caster. (Same caster usually does not apply as cooldown often exceeds duration).
* Weapon enhancement spells of the same type (e.g. 2 mages with flame weapons) do not stack. The sword does not get more flaming, sorry :)
* Animation based effects (knockdown, stun, etc.) stack, but only the one with the highest priority is played. This is defined in the priority column in effects.xls.
* Glyphs do stack but there is a limit of 5 active glyphs per caster.
* Fire and Cold DoT effects do not stack, the spell cast last will cancel any existing spell of the opposite type.
* Fire and Cold AoEs cancel each other, other AoEs might interact rather violently, handle with care :)

For equipment and item based effects, the game usually stacks within the minumum and maximum clamp values of a property (properties.xls). This means that you can accumulate a lot of +damage or +critical critical chance effects, but for some type of stats there is a point where you are no longer gaining any benefits (e.g. speed modification - animations can only be sped up to a certain point before breaking, so stacking momentum, haste and a weapon with a speed based effect will not result in a -3.0s attack time, sorry :p)

For almost all effects, the total result of all property modifications on a creature are visible on the main character UI by hovering over the individual stats.

==== Q: How does game difficulty affect abilities ? ====

A: Our approach to game difficulty dictates that the effect of your chosen setting are

a) non punishing - You do not get less XP for chosing a lower difficulty mode, etc.
b) challenge scaling - Higher difficulty will reward you with greater obstacles to overcome.
c) fair - Lower difficulties grant benefits that gradually get removed. (This does not mean the rules are symmetric and is not true on nightmare at all. Nightmare is evil. And unfair.)
d) non persistent - Difficulty changes are possible on the fly, at any time and take immediate effect.

The game is balanced so that Hard mode is challenging for a Baldur's gate veteran.

Based on these guidelines, you can expect the following ability behaviors in game:

* The lower the difficulty, the longer your hostile effects such as stuns will last on enemies and the shorter they will last on you.
* The lower the difficulty, the more damage your abilities will do.
* The lower the difficulty, the less likely the enemy AI will use devastating special abilities (Note: less likely does not mean 'does not use').
* Casual and Normal have reduced friendly or nullified fire damage damage from area effect spells. Hard and Nightmare require careful positioning and tactical use of spells.
* The higher the difficulty, the more careful you need to manage threat when using spells and abilities (The AI becomes smarter about picking targets).

==== Q: What is spell affinity ? ====

A: Spell Affinity was a design we toyed with for a while during development but decided not to implement.

==== Q: How does Rank Based Mitigation Work ? ====

A: In line with Dragon Age: Origin's asymmetric approach to rules, the game uses creature ranks (instead of levels) in addition to stats and resistances to define how creatures get affected by abilities. In short: Boss monsters get affected differently by abilities and effects than Lieutenants or Critters.

The rank system is the primary balancing vector for the games difficulty levels and profoundly affects all aspects of combat. The gory details of this system are defined in creature_ranks.xls and difficulty.xls.

Rank mitigation affects not just damage in- and output of a creature, but also the duration that hostile effects persist on it and is different for each difficulty level of the game. Note that party members have their own rank in this system and are handled differently from other creatures in some cases.

Below is the formula used for rank based effect duration mitigation:

<dascript>
// sys_resistances_h
// @brief Returns an effect duration scaled by rank of oCreature and game difficulty
// @author Georg
float GetRankAdjustedEffectDuration(object oCreature, float fDur)
{

// -------------------------------------------------------------------------
// Georg: This deserves some explanation:
//
// One of the core issues when designing the combat system was always
// the fact that the story called for sequences during the game in which
// your main character acts solo.
//
// Characters reliant on special abilities, such as rogues, would require
// them to be very effective in order to beat enemies that a standard tank
// can plow through. However, if these abilities would maintain the same
// effectiveness in a full party, most encounters would turn into a stunfest.
//
// The solution is to add 1 second flat to each detrimental effect duration
// lasting at least 1 second for each unoccupied slot in the party - before applying
// rank and difficulty modifiers. This also makes solo play a bit more viable.
//
// This is in addition to the diminishing returns on quickly successive stuns.
//
// -------------------------------------------------------------------------
if (!IsPartyMember(oCreature))
{
float fPartySizeModifier = IntToFloat(Max(0,4 - GetArraySize(GetPartyList())));

if (fDur >= 1.0f)
{
fDur += fPartySizeModifier;
}
}

float fRankDurMod = Diff_GetDurationModifier(oCreature);
if (fRankDurMod >0.0f)
{
return (fDur * fRankDurMod);
}
else
{
return fDur;
}
}
</dascript>

[[Category:Scripts]]

==== Q: What does 'asymmetric rules system' mean ? ====

The goal behind Dragon Age: Origin's rule system was to create a fun and challenging video game experience first and foremost.

We describe the rules as 'asymmetric' because a subset of the game rules treats player controlled characters and monsters differently, which is a deviation from pen and paper rule design that often require player and opponents to be treated exactly the same.

Notable Examples:
* Party members never die permanently (get shattered, etc.)
* Differently ranked creatures (including party members) get affected for different durations by effects
* In limited situations in the game, we apply benefits to the player to overcome greater odds than they would usually be able to.
* Some abilities will work diferently when deployed against the party (although the visual results might be identical).
* Elimination of instant death situations (not fun!) against players but not against monsters (fun!).
* Sustained abilities only work for players (the overhead is not justified for monsters that won't ever reappear after they die).

Ability

2009-10-27T22:47:02Z

Georg Zoeller: /* Q: How does Rank Based Mitigation Work ? */

Classes

2009-10-27T22:21:46Z

Georg Zoeller: /* Character Creation Scripting */ Added list of relevant scripts

''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'''||'''IntAdjust'''||'''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 and 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 through the Character Creation UIs, use the data in [[CLA_base.xls]] to construct the character based on the player's choices and 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: Scripting]]

CLA base.xls

2009-10-27T22:11:56Z

Georg Zoeller:

This 2da file is used to define the [[Classes|Character Classes]] available in Dragon Age: Origins.

== CLA_data worksheet ==

{{2da start|CLA_data}}
{{2da column| Label | string | }}
{{2da column| NameStrref |int| the reference ID number of a string in the string table that has this class' name in it. Use the [[String Editor]] to view strings by ID.}}
{{2da column| PluralStrref | int | a string in the string table with the class' name, pluralized}}
{{2da column| LowerStrref | int | }}
{{2da column| DescStrref| int | A short description of the class.}}
{{2da column| TooltipStrref |int| Tooltip text for the class.}}
{{2da column| Icon | resource | Icon used to represent this class in character generation.}}
{{2da column| Constant | string| The name of the constant used in scripts to refer to this class. eg, "CLASS_Warrior".}}
{{2da column| Package | int | }}
{{2da column| BaseHealth | float | }}
{{2da column| bUsesMana |int| 0 sets this class to use stamina for its abilities, 1 sets it to use mana.}}
{{2da column| BaseManaStamina | float | }}
{{2da column| DepletableProgression | float | }}
{{2da column| StrAdjust |float| a bonus this class gets to starting strength attribute }}
{{2da column| ConAdjust |float| a bonus this class gets to starting constitution attribute }}
{{2da column| WillAdjust |float| a bonus this class gets to starting willpower attribute }}
{{2da column| MagAdjust |float| a bonus this class gets to starting magic attribute }}
{{2da column| IntAdjust |float| a bonus this class gets to starting cunning attribute }}
{{2da column| DexAdjust |float| a bonus this class gets to starting dexterity attribute }}
{{2da column| MinLevel |int| The prerequesite level a character must be to take this class. If it's greater than zero, it's an advanced class. '''Note: this column is a remnant of when specialization classes were included in the base class 2DA; this approach is no longer used.'''}}
{{2da column| BaseClass |int| For advanced classes, this sets which base class it is an advanced class of. The number here refers to the ID of the row that it's a advanced class for. '''Note: this column is a remnant of when specialization classes were included in the base class 2DA; this approach is no longer used.'''}}
{{2da column| BaseAttack | float | }}
{{2da column| BaseDefense | float | }}
{{2da column| DefensePerLevel | float | }}
{{2da column| HealthPerLevel | float | }}
{{2da column| LevelsPerAbility | int | How many levels before gaining an ability. Example. If a 3 is here, it means you get an ability on every level divisible by 3}}
{{2da column| LevelsPerSkill | int | How many levels before gaining a skill. Example. If a 3 is here, it means you get an ability on every level divisible by 3}}
{{2da column| DamagePerLevel | float | This was a fudge added to the rule system to diminish the power that Strength's bonus damage had. Basically, this is just added to the base damage bonus of the character.}}
{{2da column| StartingAbility1 | int | This is an index into the ABI 2da. If its valid it will add that ability to the character when you first take a level with the class. This is used for the hidden talent that all classes get. This talent is used in subsequent prereq checks}}
{{2da column| StartingAbility2 | int | This is an index into the ABI 2da. If its valid it will add that ability to the character when you first take a level with the class.}}
{{2da column| PlayerClass |int| Determines whether this class can be taken by a player.}}
{{2da column| CharGenLabel| string| }}
{{2da column| Achievement | string| Required Achievement to unlock this class permanently}}
{{2da end}}
[[Category:2DAs]]

CLA base.xls

2009-10-27T22:10:01Z

Georg Zoeller:

== CLA_data worksheet ==

{{2da start|CLA_data}}
{{2da column| Label | string | }}
{{2da column| NameStrref |int| the reference ID number of a string in the string table that has this class' name in it. Use the [[String Editor]] to view strings by ID.}}
{{2da column| PluralStrref | int | a string in the string table with the class' name, pluralized}}
{{2da column| LowerStrref | int | }}
{{2da column| DescStrref| int | A short description of the class.}}
{{2da column| TooltipStrref |int| Tooltip text for the class.}}
{{2da column| Icon | resource | Icon used to represent this class in character generation.}}
{{2da column| Constant | string| The name of the constant used in scripts to refer to this class. eg, "CLASS_Warrior".}}
{{2da column| Package | int | }}
{{2da column| BaseHealth | float | }}
{{2da column| bUsesMana |int| 0 sets this class to use stamina for its abilities, 1 sets it to use mana.}}
{{2da column| BaseManaStamina | float | }}
{{2da column| DepletableProgression | float | }}
{{2da column| StrAdjust |float| a bonus this class gets to starting strength attribute }}
{{2da column| ConAdjust |float| a bonus this class gets to starting constitution attribute }}
{{2da column| WillAdjust |float| a bonus this class gets to starting willpower attribute }}
{{2da column| MagAdjust |float| a bonus this class gets to starting magic attribute }}
{{2da column| IntAdjust |float| a bonus this class gets to starting cunning attribute }}
{{2da column| DexAdjust |float| a bonus this class gets to starting dexterity attribute }}
{{2da column| MinLevel |int| The prerequesite level a character must be to take this class. If it's greater than zero, it's an advanced class. '''Note: this column is a remnant of when specialization classes were included in the base class 2DA; this approach is no longer used.'''}}
{{2da column| BaseClass |int| For advanced classes, this sets which base class it is an advanced class of. The number here refers to the ID of the row that it's a advanced class for. '''Note: this column is a remnant of when specialization classes were included in the base class 2DA; this approach is no longer used.'''}}
{{2da column| BaseAttack | float | }}
{{2da column| BaseDefense | float | }}
{{2da column| DefensePerLevel | float | }}
{{2da column| HealthPerLevel | float | }}
{{2da column| LevelsPerAbility | int | How many levels before gaining an ability. Example. If a 3 is here, it means you get an ability on every level divisible by 3}}
{{2da column| LevelsPerSkill | int | How many levels before gaining a skill. Example. If a 3 is here, it means you get an ability on every level divisible by 3}}
{{2da column| DamagePerLevel | float | This was a fudge added to the rule system to diminish the power that Strength's bonus damage had. Basically, this is just added to the base damage bonus of the character.}}
{{2da column| StartingAbility1 | int | This is an index into the ABI 2da. If its valid it will add that ability to the character when you first take a level with the class. This is used for the hidden talent that all classes get. This talent is used in subsequent prereq checks}}
{{2da column| StartingAbility2 | int | This is an index into the ABI 2da. If its valid it will add that ability to the character when you first take a level with the class.}}
{{2da column| PlayerClass |int| Determines whether this class can be taken by a player.}}
{{2da column| CharGenLabel| string| }}
{{2da column| Achievement | string| Required Achievement to unlock this class permanently}}
{{2da end}}
[[Category:2DAs]]

Classes

2009-10-27T22:02:43Z

Georg Zoeller: /* Character Creation Scripting */

Classes

2009-10-27T22:02:33Z

Georg Zoeller: /* Description */ Shrunk fonts to fit table on page

Classes

2009-10-27T22:01:16Z

Georg Zoeller: /* Detailed Description */ Added 2da sample, links to CLA_Base and started writing documentation on how character creation scripting works.

Classes

2009-10-27T21:44:02Z

Georg Zoeller:

''Work in progress''

=== Overview ===

Dragon Age: Origins is a strongly class based RPG featuring 3 distinct character classes with exclusive abilities and progressions.

=== Detailed Description ===

The detailed rules implications of a class are defined in [[CLA_base.xls]].

In addition to the three base classes

* Mage
* Warrior
* Rogue

the 2da defines several additional classes used by creatures in the game as well as special NPCs such as

* Dog
* Shale

Classes

2009-10-27T20:16:32Z

Georg Zoeller: Created page with '''Work in progress'' === Overview === Dragon Age: Origins is a strongly class based RPG featuring 3 distinct character classes with exclusive abilities and progressions. === ...'

''Work in progress''

=== Overview ===

Dragon Age: Origins is a strongly class based RPG featuring 3 distinct character classes with exclusive abilities and progressions.

=== Detailed Description ===

The detailed rules implications of a class are defined in [[CLA_BASE.xls]].

In addition to the three base classes

* Mage
* Warrior
* Rogue

the 2da defines several additional classes used by creatures in the game as well as special NPCs such as

* Dog
* Shale

Properties.xls

2009-10-27T19:40:24Z

Georg Zoeller:

Depletable properties will be updated by their "combat" every 2 seconds and their "non-combat" values every 5 seconds.

EngineLink:
* 00 - DerivedDefault : No modification of stats
<dascript>
return 0; // Nothing
</dascript>

* 01 - DerivedAttack: Each point of STR and DEX above 10 adds + 0.5 attack
<dascript>
return (FLOAT32) ( max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_STRENGTH) -10.0f)/2.0f , 0.0) +
max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_DEXTERITY) -10.0f)/2.0f , 0.0));
</dascript>

* 02 - DerivedDefense: Each point of DEX above 10 adds +1.0 defense
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_DEXTERITY) -10) , 0.0) ;
</dascript>

* 03 - DerivedArmor: No special interaction
<dascript>
return 0; // Nothing
</dascript>

* 04 - DerivedAP: Each point of CUN above 10 adds +(1/7) points of AP
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_CUNNING)-10),0.0)/7;
</dascript>

* 05 - DerivedSpellPower: Each point of MAG above 10 adds +1.0 Spellpower
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_MAGIC) -10) , 0.0);
</dascript>

* 06 - DerivedHealth: Each point of CON above 10 adds 5 points of health.
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_CONSTITUTION) -10) , 0.0)*5;
</dascript>

* 07 - DerivedManaStamina: Each point of WIL above 10 adds 5 points of Mana/Stamina
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_WILLPOWER) -10) , 0.0)*5;
</dascript>

* 08 - DerivedResistanceMental: Each mental attribute point above 10 adds 0.5 Mental Resistance.
<dascript>
return (FLOAT32) ( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_MAGIC) -10) +
(cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_WILLPOWER) -10) +
(cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_INTELLIGENCE)) -10) / 2.0f;
</dascript>

* 09 - DerivedResistancePhysical: Each physical attribute above 10 adds 0.5 Physical Resistance.
<dascript>
return (FLOAT32) ( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_STRENGTH) -10) +
(cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_CONSTITUTION) -10) +
(cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_DEXTERITY) -10)) / 2.0f;
</dascript>

{{2da start|Properties}}
{{2da column|Stat|string|Human Readable statname. Spaces are not allowed in these strings}}
{{2da column|Type|string|SIMPLE, ATTRIBUTE, DEPLETABLE}}
{{2da column|Min|float|Minimum value possible}}
{{2da column|Max|float|Maximum value possible}}
{{2da column|UIMapping|int|
*1: Base resistances
*2: Deprecated
*3: Elemental (%) resistances}}
{{2da column|NameStrId|int|}}
{{2da column|NameLowerStrId|int|}}
{{2da column|DescStrId|int|}}
{{2da column|Desc2StrId|int|Necessary for rows 4 - 9 ONLY. When hovering over the numerical values of the attributes in the character sheet, there should be detailed and technical text written that explains the effects of these stats. Need writing for: Strength, Dexterity, Willpower, Magic, Cunning, Constitution}}
{{2da column|NonCombatEffect|int|}}
{{2da column|CombatEffect|int|}}
{{2da column|EngineLink|int|See above}}
{{2da column|ToolsetName|string|}}
{{2da column|bShowInToolset|int|}}
{{2da column|Constant|comment|}}
{{2da column|bShowInPartyPicker|int|}}
{{2da column|Precision|int|Number of digits to display after the decimal place.}}
{{2da end}}

{{2da start|HeroicStats}}
{{2da column|Stat|string|Human Readable statname. Spaces are not allowed in these strings}}
{{2da column|Type|string|SIMPLE, ATTRIBUTE, DEPLETABLE}}
{{2da column|Min|float|Minimum value possible}}
{{2da column|Max|float|Maximum value possible}}
{{2da column|UIMapping|int|}}
{{2da column|NameStrId|int|}}
{{2da column|DescStrId|int|}}
{{2da column|NonCombatEffect|int|}}
{{2da column|CombatEffect|int|}}
{{2da column|EngineLink|int|See above}}
{{2da column|ToolsetName|string|}}
{{2da column|bShowInToolset|int|}}
{{2da column|Constant|comment|}}
{{2da column|bShowInPartyPicker|int|}}
{{2da column|SortOrder|int|Sorts ascending, negative values allowed}}
{{2da end}}

{{2da start|HeroicPartyStats}}
{{2da column|Stat|string|Human Readable statname}}
{{2da column|Type|string|SIMPLE, ATTRIBUTE, DEPLETABLE}}
{{2da column|Min|float|Minimum value possible}}
{{2da column|Max|float|Maximum value possible}}
{{2da column|UIMapping|int|}}
{{2da column|NameStrId|int|}}
{{2da column|DescStrId|int|}}
{{2da column|NonCombatEffect|int|}}
{{2da column|CombatEffect|int|}}
{{2da column|EngineLink|int|See above}}
{{2da column|ToolsetName|string|}}
{{2da column|bShowInToolset|int|}}
{{2da column|Constant|comment|}}
{{2da column|bShowInPartyPicker|int|}}
{{2da column|SortOrder|int|Sorts ascending, negative values allowed}}
{{2da end}}

[[Category:2DAs]]

Properties.xls

2009-10-27T19:39:44Z

Georg Zoeller: Added some information on the hardcoded engine link functionality.

Depletable properties will be updated by their "combat" every 2 seconds and their "non-combat" values every 5 seconds.

EngineLink:
* 00 - DerivedDefault : No modification of stats
<dascript>
return 0; // Nothing
</dascript>

* 01 - DerivedAttack: Each point of STR and DEX above 10 adds + 0.5 attack
<dascript>
return (FLOAT32) ( max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_STRENGTH) -10.0f)/2.0f , 0.0) +
max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_DEXTERITY) -10.0f)/2.0f , 0.0));
</dascript>

* 02 - DerivedDefense: Each point of DEX above 10 adds +1.0 defense
<dascript>
FLOAT32 fDexBonus = (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_DEXTERITY) -10) , 0.0) ;
</dascript>

* 03 - DerivedArmor: No special interaction
<dascript>
return 0; // Nothing
</dascript>

* 04 - DerivedAP: Each point of CUN above 10 adds +(1/7) points of AP
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_CUNNING)-10),0.0)/7;
</dascript>

* 05 - DerivedSpellPower: Each point of MAG above 10 adds +1.0 Spellpower
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_MAGIC) -10) , 0.0);
</dascript>

* 06 - DerivedHealth: Each point of CON above 10 adds 5 points of health.
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_CONSTITUTION) -10) , 0.0)*5;
</dascript>

* 07 - DerivedManaStamina: Each point of WIL above 10 adds 5 points of Mana/Stamina
<dascript>
return (FLOAT32) max( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_WILLPOWER) -10) , 0.0)*5;
</dascript>

* 08 - DerivedResistanceMental: Each mental attribute point above 10 adds 0.5 Mental Resistance.
<dascript>
return (FLOAT32) ( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_MAGIC) -10) +
(cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_WILLPOWER) -10) +
(cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_INTELLIGENCE)) -10) / 2.0f;
</dascript>

* 09 - DerivedResistancePhysical: Each physical attribute above 10 adds 0.5 Physical Resistance.
<dascript>
return (FLOAT32) ( (cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_STRENGTH) -10) +
(cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_CONSTITUTION) -10) +
(cPropertiesList.GetValue(PROPERTY_ATTRIBUTE_DEXTERITY) -10)) / 2.0f;
</dascript>

{{2da start|Properties}}
{{2da column|Stat|string|Human Readable statname. Spaces are not allowed in these strings}}
{{2da column|Type|string|SIMPLE, ATTRIBUTE, DEPLETABLE}}
{{2da column|Min|float|Minimum value possible}}
{{2da column|Max|float|Maximum value possible}}
{{2da column|UIMapping|int|
*1: Base resistances
*2: Deprecated
*3: Elemental (%) resistances}}
{{2da column|NameStrId|int|}}
{{2da column|NameLowerStrId|int|}}
{{2da column|DescStrId|int|}}
{{2da column|Desc2StrId|int|Necessary for rows 4 - 9 ONLY. When hovering over the numerical values of the attributes in the character sheet, there should be detailed and technical text written that explains the effects of these stats. Need writing for: Strength, Dexterity, Willpower, Magic, Cunning, Constitution}}
{{2da column|NonCombatEffect|int|}}
{{2da column|CombatEffect|int|}}
{{2da column|EngineLink|int|See above}}
{{2da column|ToolsetName|string|}}
{{2da column|bShowInToolset|int|}}
{{2da column|Constant|comment|}}
{{2da column|bShowInPartyPicker|int|}}
{{2da column|Precision|int|Number of digits to display after the decimal place.}}
{{2da end}}

{{2da start|HeroicStats}}
{{2da column|Stat|string|Human Readable statname. Spaces are not allowed in these strings}}
{{2da column|Type|string|SIMPLE, ATTRIBUTE, DEPLETABLE}}
{{2da column|Min|float|Minimum value possible}}
{{2da column|Max|float|Maximum value possible}}
{{2da column|UIMapping|int|}}
{{2da column|NameStrId|int|}}
{{2da column|DescStrId|int|}}
{{2da column|NonCombatEffect|int|}}
{{2da column|CombatEffect|int|}}
{{2da column|EngineLink|int|See above}}
{{2da column|ToolsetName|string|}}
{{2da column|bShowInToolset|int|}}
{{2da column|Constant|comment|}}
{{2da column|bShowInPartyPicker|int|}}
{{2da column|SortOrder|int|Sorts ascending, negative values allowed}}
{{2da end}}

{{2da start|HeroicPartyStats}}
{{2da column|Stat|string|Human Readable statname}}
{{2da column|Type|string|SIMPLE, ATTRIBUTE, DEPLETABLE}}
{{2da column|Min|float|Minimum value possible}}
{{2da column|Max|float|Maximum value possible}}
{{2da column|UIMapping|int|}}
{{2da column|NameStrId|int|}}
{{2da column|DescStrId|int|}}
{{2da column|NonCombatEffect|int|}}
{{2da column|CombatEffect|int|}}
{{2da column|EngineLink|int|See above}}
{{2da column|ToolsetName|string|}}
{{2da column|bShowInToolset|int|}}
{{2da column|Constant|comment|}}
{{2da column|bShowInPartyPicker|int|}}
{{2da column|SortOrder|int|Sorts ascending, negative values allowed}}
{{2da end}}

[[Category:2DAs]]

Rules

2009-10-27T19:03:38Z

Georg Zoeller: /* Overview */

=== Overview ===

The Core Game rules of Dragon Age are implemented mostly in the Scripting Language and Data. This page details the organization of the rules system, design principles, technical implementation details and limitations.

{| width="100%"
|-
| valign="top" height="100%" |

{| style="margin:0; background:#f5fffa; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em; width:100%; height:100%"
|-
| valign="top"|
<h2 style="margin:0; background:#cef2e0; font-size:150%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;"> Categories </h2>
|-
|
* [[Creature Properties]] - Attributes, Stats and other numbers that make up a character.
* [[Classes]] - Technical information on the implementation of character classes.
* [[Combat Rules]] - The rules of conflict resolution. Who hits. When. For how much.
* [[Ability|Abilities]] - Spells, Skills, Talents and Item Abilities.
|}
|}

=== Detailed Description ===

[[Category:Scripts]]

Ability

2009-10-27T19:00:48Z

Georg Zoeller: linkified