T4 Modules Howto Guide/Talents - Revision history

Grazz: /* Talent Definitions */

2013-10-21T07:42:56Z

‎Talent Definitions

BDota at 14:57, 29 September 2013

2013-09-29T14:57:04Z

Castler at 02:15, 19 July 2013

2013-07-19T02:15:25Z

Ibanix: Ibanix moved page Dev-Talents to T4 Modules Howto Guide/Talents: namespace collision prevention

2013-07-08T18:35:15Z

Ibanix moved page Dev-Talents to T4 Modules Howto Guide/Talents: namespace collision prevention

Ibanix at 21:10, 6 July 2013

2013-07-06T21:10:24Z

66.225.111.10: /* Talent Targeting */

2013-05-29T04:46:23Z

‎Talent Targeting

66.225.111.10 at 04:44, 29 May 2013

2013-05-29T04:44:51Z

98.225.252.147: improved arguments a tiny bit

2013-05-29T00:20:28Z

improved arguments a tiny bit

66.225.111.10 at 23:46, 28 May 2013

2013-05-28T23:46:56Z

66.225.111.10: Created page with "

Talents: Your special skills

Talent Definitions

By default, Talent definitions are stored in the /data/talents.lua file. This file c..."

2013-05-28T23:46:35Z

Created page with "<h1 id="toc0">Talents: Your special skills</h1> <h2 id="toc1">Talent Definitions</h2> <p>By default, Talent definitions are stored in the /data/talents.lua file. This file c..."

New page

<h1 id="toc0">Talents: Your special skills</h1>

<h2 id="toc1">Talent Definitions</h2>
<p>By default, Talent definitions are stored in the /data/talents.lua file. This file can include other files through the use of the Load(file) method.</p>

<p>Talent definitions require talent type definitions first. These are defined in newTalentType{...} blocks.</p>

<table>
<tr>
<th>Important TalentType Variables</th>
<th>Effect</th>
</tr>
<tr>
<td>name</td>
<td>Display name of this talent type. REQUIRED.</td>
</tr>
<tr>
<td>type</td>
<td>Identifier of this talent type. REQUIRED.</td>
</tr>
<tr>
<td>description</td>
<td>String description of this talent type.</td>
</tr>
<tr>
<td>points</td>
<td>Maximum amount of points in this talent type.</td>
</tr>
</table>

<p>Talent definitions are defined in newTalent{...} blocks.</p>

<table>
<tr>
<th>Important Talent Variables</th>
<th>Effect</th>
</tr>
<tr>
<td>name</td>
<td>Displayed Talent name. REQUIRED.</td>
</tr>
<tr>
<td>short_name</td>
<td>Talent identifier. name is used if unset.</td>
</tr>
<tr>
<td>points</td>
<td>Maximum amount of points that can be put into the talent.</td>
</tr>
<tr>
<td>require</td>
<td>Requirements table for adding points. See the requirements definition below.</td>
</tr>
<tr>
<td>mode</td>
<td>Talent mode. One of either: "passive" - always on, "sustained" - can be turned on or off and "activated" - can be used. Default is "activated".</td>
</tr>
<tr>
<td>info</td>
<td>String description of the talent. REQUIRED.</td>
</tr>
<tr>
<td>type</td>
<td>Talent group. REQUIRED.</td>
</tr>
<tr>
<td>cooldown</td>
<td>Amount of turns to wait before a talent can be used again.</td>
</tr>
<tr>
<td>range</td>
<td>Range of talent. May be a number or function, but use getTalentRange(t) below as a getter in that case.</td>
</tr>
</table>

<p>Identifiers for the talents are created by uppercasing the short_name (or name if no short_name is defined), replacing spaces with underscores ('_') and appending T_ in the front. These can then be accessed statically through [ActorTalents.*].</p>

<p>In this way the talent "Wind Walk" can be accessed by [ActorTalents.T_WIND_WALK].</p>

<p>Some talent variables require functions to be defined. These are of the form function(self, t), where self is the invoking actor and t is the talent being invoked.</p>

<table>
<tr>
<th>Important Talent Functions</th>
<th>Use</th>
</tr>
<tr>
<td>action</td>
<td>"activated" mode talents only. Function that gets used when talent is activated.</td>
</tr>
<tr>
<td>activate</td>
<td>"sustained" mode talents only. Function that gets used when talent gets turned on.</td>
</tr>
<tr>
<td>deactivate</td>
<td>"sustained" mode talents only. Function that gets used when talent gets turned off.</td>
</tr>
<tr>
<td>on_learn</td>
<td>Function that gets used when talent is learned.</td>
</tr>
<tr>
<td>on_unlearn</td>
<td>Function that gets used when talent is unlearned.</td>
</tr>
</table>

<p>In order to add stat, level or other talent requirements, a requirement table is required. These are the recognised variables.</p>

<table>
<tr>
<th>Requirement Definition</th>
<th>Use</th>
</tr>
<tr>
<td>stat</td>
<td>Actor must have these stats at these levels.</td>
</tr>
<tr>
<td>level</td>
<td>Actor must be at least this level.</td>
</tr>
<tr>
<td>talent</td>
<td>Prerequisite talents.</td>
</tr>
</table>

<p>For instance if a talent requires another talent and stats you can use:<br />

<pre>require = { stat = { str = 10, dex = 10 }, talent = { Talents.T_STONE_SKIN }, },</pre>

<br />
If a talent requires that another talent NOT be taken you can use<br />

<pre>require = { talent = { { Talents.T_STONE_SKIN, false }, }, },</pre>

</p>

<h2 id="toc2">Talent Targeting</h2>
<p>Many activatable talents require some user targeting input. This is done through a coroutine. This is an example of the standard targeting and dealing damage case:<br />

<pre>local tg = {type="bolt", range=self:getTalentRange(t), talent=t}
local x, y = self:getTarget(tg)
if not x or not y then return nil end
self:project(tg, x, y, DamageType.FIRE, 10, nil)</pre>

</p>

<p>In this case, tg contains the targeting and damage settings. Possible variables are:<br />

<table>
<tr>
<th>Targeting Settings</th>
<th>Effect</th>
</tr>
<tr>
<td>type</td>
<td>Targeting type. See below.</td>
</tr>
<tr>
<td>range</td>
<td>Range limit. Usually always self:getTalentRange(t).</td>
</tr>
<tr>
<td>talent</td>
<td>The talent being used.</td>
</tr>
<tr>
<td>friendlyfire</td>
<td>(?) Defaults to true.</td>
</tr>
<tr>
<td>no_restrict</td>
<td>(?)</td>
</tr>
<tr>
<td>radius</td>
<td>"ball" and "cone" targeting modes use this.</td>
</tr>
<tr>
<td>cone_angle</td>
<td>"cone" targeting mode uses this. Defaults to 55.</td>
</tr>
<tr>
<td>nolock</td>
<td>Free targeting mode.</td>
</tr>
<tr>
<td>msg</td>
<td>Message to display during targeting.</td>
</tr>
</table>

</p>

<p>The possible targeting modes are:<br />

<table>
<tr>
<th>type</th>
<th>Effect</th>
</tr>
<tr>
<td>hit</td>
<td>Simple single target.</td>
</tr>
<tr>
<td>bolt</td>
<td>Hits first thing in path.</td>
</tr>
<tr>
<td>beam</td>
<td>Hits everything in path.</td>
</tr>
<tr>
<td>ball</td>
<td>Hits everything in a ball around the target.</td>
</tr>
<tr>
<td>cone</td>
<td>Hits everything in a cone in the direction.</td>
</tr>
</table>

</p>

<p>getTarget(tg) is a method that is overriden by an AI for NPCs, or by the game module class.</p>

<p>Note that the last parameter of the project() method is the particle system to use.</p>

<h2 id="toc3">ActorTalents Class</h2>
<p>By default, Actors inherit from the ActorTalents class, even in the example module. This class provides an interface for manipulating and accessing talents. These are some of the valuable methods.</p>

<table>
<tr>
<th>Useful Talent Related ActorTalents class methods</th>
<th>Use</th>
</tr>
<tr>
<td>useTalent(t)</td>
<td>Forces the Actor to use the talent.</td>
</tr>
<tr>
<td>useTalents()</td>
<td>Shows the use talent dialog.</td>
</tr>
<tr>
<td>knowTalent(t)</td>
<td>Returns true if the talent is known.</td>
</tr>
<tr>
<td>knowTalentType(tt)</td>
<td>Returns true if the talent group is known.</td>
</tr>
<tr>
<td>learnTalent(t, force, nb)</td>
<td>Has an Actor learn a talent. force prevents a canLearnTalent(t) test. nb is the amount of points to put into the talent.</td>
</tr>
<tr>
<td>unlearnTalent(t)</td>
<td>Makes the Actor forget the talent.</td>
</tr>
<tr>
<td>learnTalentType(tt, v)</td>
<td>Has the Actor learns a Talent Type. (v is true or false?)</td>
</tr>
<tr>
<td>unlearnTalentType(tt)</td>
<td>Has the Actor forget a Talent Type.</td>
</tr>
<tr>
<td>canLearnTalent(t)</td>
<td>Returns true if the Actor meets the requirements for the talent.</td>
</tr>
<tr>
<td>getTalentLevel(t)</td>
<td>Gets the amount of points in talent. 0 if unlearned.</td>
</tr>
<tr>
<td>isTalentCoolingDown(t)</td>
<td>Returns true if the specified talent is in the process of cooldown.</td>
</tr>
<tr>
<td>getTalentRange(t)</td>
<td>Returns the talent range. Use this instead of checking the range variable, since this allows the range variable to be either a function or a number.</td>
</tr>
<tr>
<td>cooldownTalents()</td>
<td>Cools down all talents by 1. This needs to be in your act() method.</td>
</tr>
</table>

<p>All of the above methods can also be redefined in your own class if their functionality needs to be expanded. In addition, the following may also be useful to redefine:</p>

<table>
<tr>
<th>Method</th>
<th>Use</th>
</tr>
<tr>
<td>preUseTalent(t)</td>
<td>Called before an actor uses a talent. Not returning true stops the talent from invoking.</td>
</tr>
<tr>
<td>postUseTalent(t)</td>
<td>Called after an actor uses a talent. Not returning true stops stops cooldown or sustained state from happening.</td>
</tr>
<tr>
<td>getTalentFullDescription(t)</td>
<td>Used in Dialogs. Overload to add more information such as mana use.</td>
</tr>
</table>

← Older revision		Revision as of 14:57, 29 September 2013
Line 309:		Line 309:

	Go back to [[T4 Modules Howto Guide]]		Go back to [[T4 Modules Howto Guide]]
		+
		+	{{Module Guides}}

← Older revision		Revision as of 21:10, 6 July 2013
Line 329:		Line 329:
	</table>		</table>

−	Go back to [[~~T4modules-module-howto-guides~~]]	+	Go back to [[T4 Modules Howto Guide]]

← Older revision		Revision as of 04:46, 29 May 2013
Line 241:		Line 241:

	<p>Note that the last parameter of the project() method is the particle system to use.</p>		<p>Note that the last parameter of the project() method is the particle system to use.</p>
−

	==ActorTalents Class==		==ActorTalents Class==

← Older revision		Revision as of 23:46, 28 May 2013
Line 329:		Line 329:
	</tr>		</tr>
	</table>		</table>
		+
		+	Go back to [[T4modules-module-howto-guides]]

@@ Line 29: / Line 29: @@
      </tr>
 </table>
 Talent definitions are defined in newTalent{...} blocks.

@@ Line 2: / Line 2: @@
 ==Talent Definitions==
-<p>Talent definitions require talent type definitions first.  These are defined in newTalentType{...} blocks.</p>
+By default, Talent definitions are stored in the /data/talents.lua file.  This file can include other files through the use of the Load(file) method.
+<table class="wikitable">
 <table>
      <tr>
          <th>Important TalentType Variables</th>
@@ Line 31: / Line 30: @@
 </table>
-<p>Talent definitions are defined in newTalent{...} blocks.</p>
+Talent definitions are defined in newTalent{...} blocks.
-−
-−
-<table>
+<table class="wikitable">
      <tr>
          <th>Important Talent Variables</th>
@@ Line 78: / Line 75: @@
 </table>
-<p>Identifiers for the talents are created by uppercasing the short_name (or name if no short_name is defined), replacing spaces with underscores ('_') and appending T_ in the front.  These can then be accessed statically through [ActorTalents.*].</p>
+Identifiers for the talents are created by uppercasing the short_name (or name if no short_name is defined), replacing spaces with underscores ('_') and appending T_ in the front.  These can then be accessed statically through [ActorTalents.*].
-<p>In this way the talent &quot;Wind Walk&quot; can be accessed by [ActorTalents.T_WIND_WALK].</p>
+In this way the talent &quot;Wind Walk&quot; can be accessed by [ActorTalents.T_WIND_WALK].
-<p>Some talent variables require functions to be defined.  These are of the form function(self, t), where self is the invoking actor and t is the talent being invoked.</p>
+Some talent variables require functions to be defined.  These are of the form function(self, t), where self is the invoking actor and t is the talent being invoked.
+<table class="wikitable">
-−
 <table>
      <tr>
          <th>Important Talent Functions</th>
@@ Line 113: / Line 108: @@
 </table>
-<p>In order to add stat, level or other talent requirements, a requirement table is required.  These are the recognised variables.</p>
+In order to add stat, level or other talent requirements, a requirement table is required.  These are the recognised variables.
-−
-−
-<table>
+<table class="wikitable">
      <tr>
          <th>Requirement Definition</th>
@@ Line 136: / Line 129: @@
 </table>
-<p>For instance if a talent requires another talent and stats you can use:<br />
+For instance if a talent requires another talent and stats you can use:
 <pre>require = { stat = { str = 10, dex = 10 }, talent = { Talents.T_STONE_SKIN }, },</pre>
-<br />
+If a talent requires that another talent NOT be taken you can use
-If a talent requires that another talent NOT be taken you can use<br />
 <pre>require = { talent = { { Talents.T_STONE_SKIN, false }, }, },</pre>
-</p>
+==Talent Targeting==
 Many activatable talents require some user targeting input.  This is done through a coroutine.  This is an example of the standard targeting and dealing damage case:
-==Talent Targeting==
-<p>Many activatable talents require some user targeting input.  This is done through a coroutine.  This is an example of the standard targeting and dealing damage case:<br />
 <pre>local tg = {type=&quot;bolt&quot;, range=self:getTalentRange(t), talent=t}
@@ Line 156: / Line 146: @@
 self:project(tg, x, y, DamageType.FIRE, 10, nil)</pre>
-</p>
+In this case, tg contains the targeting and damage settings.  Possible variables are:
-−
-<p>In this case, tg contains the targeting and damage settings.  Possible variables are:<br />
-−
-<table>
+<table class="wikitable">
      <tr>
          <th>Targeting Settings</th>
@@ Line 204: / Line 191: @@
 </table>
-</p>
+The possible targeting modes are:
-<p>The possible targeting modes are:<br />
+<table class="wikitable">
-−
-−
 <table>
      <tr>
          <th>type</th>
@@ Line 236: / Line 220: @@
 </table>
-</p>
+getTarget(tg) is a method that is overriden by an AI for NPCs, or by the game module class.
-<p>getTarget(tg) is a method that is overriden by an AI for NPCs, or by the game module class.</p>
+Note that the last parameter of the project() method is the particle system to use.
-−
-<p>Note that the last parameter of the project() method is the particle system to use.</p>
 ==ActorTalents Class==
-<table>
+<table class="wikitable">
      <tr>
          <th>Useful Talent Related ActorTalents class methods</th>
@@ Line 306: / Line 287: @@
 </table>
-<p>All of the above methods can also be redefined in your own class if their functionality needs to be expanded.  In addition, the following may also be useful to redefine:</p>
+All of the above methods can also be redefined in your own class if their functionality needs to be expanded.  In addition, the following may also be useful to redefine:
-−
-−
-<table>
+<table class="wikitable">
      <tr>
          <th>Method</th>

← Older revision	Revision as of 18:35, 8 July 2013
(No difference)

@@ Line 1: / Line 1: @@
-<h1 id="toc0">Talents: Your special skills</h1>
+=Talents: Your special skills=
-<h2 id="toc1">Talent Definitions</h2>
+==Talent Definitions==
 <p>By default, Talent definitions are stored in the /data/talents.lua file.  This file can include other files through the use of the Load(file) method.</p>
@@ Line 148: / Line 148: @@
-<h2 id="toc2">Talent Targeting</h2>
+==Talent Targeting==
 <p>Many activatable talents require some user targeting input.  This is done through a coroutine.  This is an example of the standard targeting and dealing damage case:<br />
@@ Line 243: / Line 243: @@
-<h2 id="toc3">ActorTalents Class</h2>
+==ActorTalents Class==
 <p>By default, Actors inherit from the ActorTalents class, even in the example module.  This class provides an interface for manipulating and accessing talents.  These are some of the valuable methods.</p>

@@ Line 184: / Line 184: @@
      <tr>
          <td>no_restrict</td>
-         <td>(?)</td>
+         <td>Makes no restrictions regarding targeting</td>
      </tr>
      <tr>
@@ Line 193: / Line 197: @@
          <td>cone_angle</td>
          <td>&quot;cone&quot; targeting mode uses this.  Defaults to 55.</td>
      </tr>
      <tr>