T4 Modules Howto Guide/NPCs - Revision history

QuixoticScamp: Formatting. Image section

2021-01-16T18:03:17Z

Formatting. Image section

Show changes

Zireael: add rarities example

2015-04-29T15:41:14Z

add rarities example

Grazz: warning on setting rarity to 0

2013-10-19T16:44:20Z

warning on setting rarity to 0

BDota at 14:57, 29 September 2013

2013-09-29T14:57:35Z

Castler at 02:03, 19 July 2013

2013-07-19T02:03:43Z

Ibanix: Ibanix moved page NPCs to T4 Modules Howto Guide/NPCs: namespace collision prevention

2013-07-08T18:36:30Z

Ibanix moved page NPCs to T4 Modules Howto Guide/NPCs: namespace collision prevention

Ibanix at 21:15, 6 July 2013

2013-07-06T21:15:17Z

66.225.111.10 at 04:59, 29 May 2013

2013-05-29T04:59:06Z

66.225.111.10 at 23:58, 28 May 2013

2013-05-28T23:58:07Z

66.225.111.10: Created page with "

Actors: NPCs and Monsters

Important NPC Definitions

Note that these are also used in the copy table in a player descriptor.
The..."

2013-05-28T23:54:26Z

Created page with "<h1 id="toc0">Actors: NPCs and Monsters</h1> <h2 id="toc1">Important NPC Definitions</h2> <p>Note that these are also used in the copy table in a player descriptor.<br /> The..."

New page

<h1 id="toc0">Actors: NPCs and Monsters</h1>

<h2 id="toc1">Important NPC Definitions</h2>
<p>Note that these are also used in the copy table in a player descriptor.<br />
These expand on the properties available to all entities, see <a class="" style="" href="/web/20130220053818/http://te4.org/wiki/t4modules-entities">t4modules entities</a>.</p>

<table>
<tr>
<th>Variable</th>
<th>Effect</th>
</tr>
<tr>
<td>name</td>
<td>Displayed NPC name.</td>
</tr>
<tr>
<td>short_name</td>
<td>NPC identifier. name is used if unset</td>
</tr>
<tr>
<td>desc</td>
<td>Optional description of NPC.</td>
</tr>
<tr>
<td>type</td>
<td>NPC Type (No known hardcoded types)</td>
</tr>
<tr>
<td>subtype</td>
<td>Better categorization for NPC.</td>
</tr>
<tr>
<td>display</td>
<td>Character that the NPC is displayed as in text mode.</td>
</tr>
<tr>
<td>faction</td>
<td>Actor faction. Defaults to "enemies".</td>
</tr>
<tr>
<td>ai</td>
<td>Selects which ai to use for NPC.</td>
</tr>
<tr>
<td>ai_state</td>
<td>(?) Depends on AI class.</td>
</tr>
<tr>
<td>rarity</td>
<td>How common this NPC is to generate. Higher is rarer. If not set will not ever generate.</td>
</tr>
<tr>
<td>level_range</td>
<td>Minimum and maximum levels for NPC. Read NPC Level Scaling below.</td>
</tr>
<tr>
<td>autolevel</td>
<td>Which leveling function to use to level up NPC. Read NPC Level Scaling below.</td>
</tr>
<tr>
<td>max_life</td>
<td>Max life at level 1.</td>
</tr>
<tr>
<td>energy.mod</td>
<td>Scales how much energy is gained per tick. Defaults to 1.</td>
</tr>
<tr>
<td>sight</td>
<td>Sight radius.</td>
</tr>
<tr>
<td>exp_mod</td>
<td>Scales how much exp is needed to reach a new level. Defaults to 1.</td>
</tr>
<tr>
<td>exp_worth</td>
<td>Indicator of Actor exp value. By default, exp for killing an Actor is its level times this value.</td>
</tr>
<tr>
<td>egos</td>
<td>See <a class="" style="" href="/web/20130220053818/http://te4.org/wiki/t4modules-egos">t4modules egos</a>.</td>
</tr>
<tr>
<td>egos_chance</td>
<td>See <a class="" style="" href="/web/20130220053818/http://te4.org/wiki/t4modules-egos">t4modules egos</a>.</td>
</tr>
</table>

<p>These variables are not set in the definitions file, though they can be. They can be useful to access in code however.</p>

<table>
<tr>
<th>Important runtime variables</th>
<th>Effect</th>
</tr>
<tr>
<td>energy.value</td>
<td>Current energy of this actor. Defaults to 0.</td>
</tr>
<tr>
<td>self.energy.used</td>
<td>Set to true if some energy was used this tick.</td>
</tr>
<tr>
<td>life</td>
<td>Current life. Defaults to max_life.</td>
</tr>
<tr>
<td>dead</td>
<td>true if entity is dead. Different from undead.</td>
</tr>
<tr>
<td>level</td>
<td>Current Actor level.</td>
</tr>
<tr>
<td>exp</td>
<td>Current experience.</td>
</tr>
<tr>
<td>max_level</td>
<td>Maximum level for the Actor.</td>
</tr>
</table>

<p>The example module implements several other variables in its Actor class and Combat interface. These are not hardcoded, but can be used as a base or example for implementing your own module.</p>

<table>
<tr>
<th>Variable</th>
<th>Effect</th>
</tr>
<tr>
<td>combat_armor</td>
<td>Removes this amount from damage taken.</td>
</tr>
<tr>
<td>combat.dam</td>
<td>This is added to strength to determine the damage done by attacks.</td>
</tr>
</table>

<h2 id="toc2">Actor class important methods</h2>
<p>For more information, read the documentation.</p>

<table>
<tr>
<th>Method</th>
<th>Purpose</th>
</tr>
<tr>
<td>act()</td>
<td>Code that gets executed every time the entity gets to act.</td>
</tr>
<tr>
<td>canSee(actor)</td>
<td>Test if the actor can see the target actor. This does not check LOS or such, only the actual ability to see it, such as influenced by stealth, invisibility or telepathy. Returns true or false and a number from 0 to 100 representing the 'chance' to be seen.</td>
</tr>
<tr>
<td>getTarget()</td>
<td>Gets the Actor target. Redefined by player and AI.</td>
</tr>
<tr>
<td>setTarget(target)</td>
<td>Sets the actor target. Redefined by player and AI.</td>
</tr>
<tr>
<td>move(x, y, force)</td>
<td style="text-align: left;">Do NOT manually set the actor's x and y values. Use this method instead. Set force to true to not test for the presence of other entities. Returns true if a move was attempted and energy should propably be used.</td>
</tr>
<tr>
<td>moveDir(dir)</td>
<td>Moves in a certain direction. Calls move() internally.</td>
</tr>
<tr>
<td>canMove(x, y, terrain_only)</td>
<td>Checks if the Actor can go there. if terrain_only is true it only checks terrain and ignores the presence of actors and other entities.</td>
</tr>
<tr>
<td>teleportRandom(x, y, dist, min_dist)</td>
<td>Teleports randomly to x,y. dist is the radius of the effect, min_dist is a minimum radius of the effect and defaults to 0. Set dist to 0 for precise teleport.</td>
</tr>
<tr>
<td>useEnergy(amount)</td>
<td>Amount of energy to subtract from the actor in energy based time systems. Often used in the act() method after taking an action that takes time.</td>
</tr>
<tr>
<td>reactionToward(target)</td>
<td>Uses factions to check for hostility. -100 is fully hostile, 0 is neutral and 100 is friendly.</td>
</tr>
<tr>
<td>addTemporaryValue(prop, v, noupdate)</td>
<td>Changes a property on the actor, but returns an id so the value change can be reversed with a call to removeTemporaryValue(). If noupdate is true the property is not actually changed.</td>
</tr>
<tr>
<td>removeTemporaryValue(prop, id, noupdate)</td>
<td>Reverses a previous call to addTemporaryValue(). Use its returned id to reverse its change.</td>
</tr>
<tr>
<td>onTemporaryValueChange(prop, sub, v)</td>
<td>Does nothing. Redefine to perform some action when temporary values are applied or removed.</td>
</tr>
<tr>
<td>attr(prop, v, fix)</td>
<td>Non-temporarily increases or decreases an actor property. Use this for compatibility with temporary values above. If fix is set the property is set to v, not increased or decreased. Commonly, attr(prop) alone is used to check for the existance of a property instead of modifying it.</td>
</tr>
<tr>
<td>isNear(x, y, radius)</td>
<td>Checks whether the actor is within a certain radius of the passed coordinate.</td>
</tr>
</table>

<p>In addition, defining stats automatically creates a getStat() function. For example, defining the stat str creates a getStr() function for you.</p>

<h2 id="toc3">NPC Egos</h2>

<h2 id="toc4">NPC Level Scaling</h2>
<p>Depending on the zone settings, the spawned creatures can actually level with the player. This requires a level_range variable to be properly set and a levelup() method in the Actor class.</p>

<p>The level_range variable defines the possible range the creature can be.<br />
The entity will always be leveled up to at least its minimum level in the level range. It will also never be leveled above that range either.</p>

<p>The leveling method should be defined in Actor.lua. In ToME this method adds to the life, stamina and mana of actors. Alternatively you can create several, and use the autolevel variable to pick which to call.</p>

<p>All creatures are always generated at level 1, then leveled up to reach their required level. Keep this is mind when creating the NPC descriptor. Note also that you can create your own levelup() function in the NPC descriptor if a unique levelup method is needed.</p>

<p>See [[Dev-Zones]] for more info</p>

@@ Line 227: / Line 227: @@
 <p>See [[Dev-Zones]] for more info</p>
 Go back to [[T4 Modules Howto Guide]]
 {{Module Guides}}

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

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

← Older revision		Revision as of 21:15, 6 July 2013
Line 236:		Line 236:
	<p>See [[Dev-Zones]] for more info</p>		<p>See [[Dev-Zones]] for more info</p>

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

@@ Line 48: / Line 48: @@
      <tr>
          <td>rarity</td>
-         <td>How common this NPC is to generate.  Higher is rarer.  If not set will not ever generate.</td>
+         <td>How common this NPC is to generate.  Higher is rarer.  If not set will not ever generate. Do not set to 0, this is bad.</td>
      </tr>
      <tr>

@@ Line 2: / Line 2: @@
 <h2 id="toc1">Important NPC Definitions</h2>
-<table>
+Note that these are also used in the copy table in a player descriptor. These expand on the properties available to all entities, see [[Entities]].
      <tr>
          <th>Variable</th>
@@ Line 87: / Line 88: @@
 </table>
-<p>These variables are not set in the definitions file, though they can be.  They can be useful to access in code however.</p>
+<table class="wikitable">
-−
-−
-−
 <table>
      <tr>
          <th>Important runtime variables</th>
@@ Line 127: / Line 125: @@
 </table>
-<p>The example module implements several other variables in its Actor class and Combat interface.  These are not hardcoded, but can be used as a base or example for implementing your own module.</p>
+The example module implements several other variables in its Actor class and Combat interface.  These are not hardcoded, but can be used as a base or example for implementing your own module.
+<table class="wikitable">
-−
 <table>
      <tr>
          <th>Variable</th>
@@ Line 145: / Line 141: @@
      </tr>
 </table>
 <h2 id="toc2">Actor class important methods</h2>
-<table>
+<table class="wikitable">
      <tr>
          <th>Method</th>
@@ Line 219: / Line 213: @@
 </table>
-<p>In addition, defining stats automatically creates a getStat() function.  For example, defining the stat str creates a getStr() function for you.</p>
+In addition, defining stats automatically creates a getStat() function.  For example, defining the stat str creates a getStr() function for you.
-−
 <h2 id="toc3">NPC Egos</h2>
@@ Line 227: / Line 220: @@
 <p>Depending on the zone settings, the spawned creatures can actually level with the player.  This requires a level_range variable to be properly set and a levelup() method in the Actor class.</p>
-<p>The level_range variable defines the possible range the creature can be.<br />
+<p>The level_range variable defines the possible range the creature can be. The entity will always be leveled up to at least its minimum level in the level range.  It will also never be leveled above that range either.</p>
 The entity will always be leveled up to at least its minimum level in the level range.  It will also never be leveled above that range either.</p>
-<p>The leveling method should be defined in Actor.lua.  In ToME this method adds to the life, stamina and mana of actors.  Alternatively you can create several, and use the autolevel variable to pick which to call.</p>
+<p>The leveling method should be defined in Actor.lua.  In ToME this method adds to the life, stamina and mana of actors.  Alternatively, you can create several, and use the autolevel variable to pick which to call.</p>
 <p>All creatures are always generated at level 1, then leveled up to reach their required level.  Keep this is mind when creating the NPC descriptor.  Note also that you can create your own levelup() function in the NPC descriptor if a unique levelup method is needed.</p>

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

@@ Line 3: / Line 3: @@
 <h2 id="toc1">Important NPC Definitions</h2>
 <p>Note that these are also used in the copy table in a player descriptor.<br />
-These expand on the properties available to all entities, see <a class="" style="" href="/web/20130220053818/http://te4.org/wiki/t4modules-entities">t4modules entities</a>.</p>
+These expand on the properties available to all entities, see [[Entities]]</p>
@@ Line 82: / Line 82: @@
      <tr>
          <td>egos</td>
-         <td>See <a class="" style="" href="/web/20130220053818/http://te4.org/wiki/t4modules-egos">t4modules egos</a>.</td>
+         <td>See ego section in [[Entities]]</td>
      </tr>
      <tr>
          <td>egos_chance</td>
-         <td>See <a class="" style="" href="/web/20130220053818/http://te4.org/wiki/t4modules-egos">t4modules egos</a>.</td>
+         <td>See ego section in [[Entities]]</td>
      </tr>
 </table>
@@ Line 237: / Line 237: @@
 <p>See [[Dev-Zones]] for more info</p>