T4 Modules Howto Guide/Player Descriptors - Revision history

Soadzombi: /* Guide */

2014-10-12T05:17:39Z

‎Guide

Soadzombi: /* Guide */

2014-10-12T05:02:12Z

‎Guide

BDota at 14:56, 29 September 2013

2013-09-29T14:56:53Z

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

2013-07-08T18:34:35Z

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

Ibanix at 21:08, 6 July 2013

2013-07-06T21:08:25Z

66.225.111.10 at 04:43, 29 May 2013

2013-05-29T04:43:55Z

66.225.111.10 at 04:42, 29 May 2013

2013-05-29T04:42:24Z

66.225.111.10 at 23:44, 28 May 2013

2013-05-28T23:44:40Z

66.225.111.10: Created page with "

Player Descriptors: Who do you want to be today?

Important variables

Variable

Effect

2013-05-28T23:44:21Z

Created page with "<h1 id="toc0">Player Descriptors: Who do you want to be today?</h1> <h2 id="toc1">Important variables</h2> <table> <tr> <th>Variable</th> <th>Effect</th..."

New page

<h1 id="toc0">Player Descriptors: Who do you want to be today?</h1>

<h2 id="toc1">Important variables</h2>

<table>
<tr>
<th>Variable</th>
<th>Effect</th>
</tr>
<tr>
<td>name</td>
<td>Display name of this option in the selection menu. REQUIRED.</td>
</tr>
<tr>
<td>short_name</td>
<td>Identifier of this option. name is used if unset.</td>
</tr>
<tr>
<td>type</td>
<td>Defines which birth stage this descriptor belongs to. REQUIRED.</td>
</tr>
<tr>
<td>descriptor_choices</td>
<td>Selects which later descriptors are allowed or disallowed.</td>
</tr>
<tr>
<td>talents_types</td>
<td>Talent types learned at start of game</td>
</tr>
<tr>
<td>talents</td>
<td>List of starting learned talents.</td>
</tr>
<tr>
<td>desc</td>
<td>String that describes the descriptor. Appears in the selection menu. REQUIRED.</td>
</tr>
<tr>
<td>body</td>
<td>Initializes available slots. Requires ActorInventory defineInventory() calls in load.lua beforehand(?) which is NOT done in the example module.</td>
</tr>
<tr>
<td>copy</td>
<td>These variables and values will be copied to the resulting player object. See <a class="" style="" href="/web/20120511162450/http://te4.org/wiki/t4modules-npcs">t4modules npcs</a> for values.</td>
</tr>
<tr>
<td>experience</td>
<td>Experience rate. 1 being normal experience gain.</td>
</tr>
<tr>
<td>stats</td>
<td>Initial stats for character. Is added to default stat values.</td>
</tr>
</table>

<p>Important to note is that these variables do not overwrite, they add every time. If your race adds 2 strength, and your class adds 2 strength again you will end up with 4 strength. The exception to this is the copy variable. All elements in this will overwrite previous copy elements.</p>

<h2 id="toc2">Editing the Example Module for your own use</h2>
<p>At the time of writing, ToME has descriptors for world, race, subrace, sex, class and subclass. However, the example module only has a descriptor for role.</p>

<p>If you want to expand this and introduce your own descriptors for races and classes like ToME, or different descriptors entirely, you need to edit the following line in your /class/Game.lua file:</p>

<pre>local birth = Birther.new(self.player, {"base", "role" }, function()</pre>

<p>For comparison, ToME has this line:</p>

<pre>local birth = Birther.new(self.player, {"base", "world", "race", "subrace", "sex", "class", "subclass" }, function()</pre>

<p>Now you just need to create your own descriptors in the /data/birth/descriptors.lua file. If you want to organize your descriptors in multiple files for organization such as ToME does, remember to make a load call with your file path, such as the following ToME uses for its elf descriptor file.</p>

<pre>load("/data/birth/races/elf.lua")</pre>

<h2 id="toc3">Leveling up</h2>
<p>Once you gain enough xp to level, the levelup() method on the player gets called.<br />
Use this method to include specific special code that runs on a new level up, such as gaining hp and stats.</p>

<p>Note that if you make use of NPC level scaling, its important to define a levelup() on the Actor class as well. Since Player inherits from Actor, you can have the Player class call Actor's levelup() method through:</p>

<pre>mod.class.Actor.levelup(self)</pre>

<h2 id="toc4">Guide</h2>
<p>This guide is roughly based on the [[t4modules t3modules module_guide_part_1|te3 player descriptor guide]].</p>

<p>In the default ToME module, you get to choose from a race, a sub-race, gender, a background, a class, and then a subclass. To the T-Engine, these are all the same thing, called 'player descriptors' (Charcter descriptors would be more accurate, but that's nitpicking), or PDs for short. PDs are what let you alter the player character in all sorts of different ways. Player descriptors typically stack, so any modifications done to one will usually add with any other modifications, rather than replacing them.</p>

<p>There's no definition or distinction between different types of PDs by the engine. They can all have the same functionality, the only place any consistency is found is by the module author. So, if you only want stats to come from races, and skills from classes, you will have to make sure that only races gain stat bonuses and only classes have skill bonuses. The engine will not discriminate against this for you.</p>

<p>All the example below will be from the ToME module, so you should be able to see pretty easily where everything came from and can easily modify it and see what happens.</p>

<p>Possibly the most important PD is the one that the player will never see, the base descriptor, found in /data/birth/descriptors.lua. This is the one that is loaded for every character, and provides the universal traits that each character will share. This one has been edited slightly for clarity.</p>

<pre>newBirthDescriptor{
type = "base",
name = "base",
desc = {
},
talents = {},
experience = 1.0,
body = { INVEN = 1000, MAINHAND=1, OFFHAND=1, BODY=1, QUIVER=1 },

copy = {
-- Mages are unheard of at first, nobody but them regenerates mana
mana_rating = 6,
mana_regen = 0,

max_level = 50,
money = 10,
resolvers.equip{ id=true,
{type="lite", subtype="lite", name="brass lantern"},
},
resolvers.inventory{ id=true,
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of lesser healing", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of cure poison", ego_chance=-1000},
{type="potion", subtype="potion", name="potion of cure poison", ego_chance=-1000},
},
resolvers.generic(function(e)
e.hotkey[9] = {"inventory", "potion of lesser healing"}
end),
},
}</pre>

<p>This defines out the body and inventory slots for each character, the base experience rate and starting gold and the minimum equipment each character will need to have.</p>

<p>The second PD applied by the ToME module is your race, followed by subrace, found appropriate in /data/birth/races/. Races are where ToME typically grants the charcter their most unique abilities and major stat adjustments. Below is the PD for elves, and then a subrace of elf.</p>

<pre>newBirthDescriptor{
type = "race",
name = "Elf",
desc = {
"Quendi are Elves, the first children of Eru.",
"The first Elves awoke by Cuiviénen, the Water of Awakening in the far east of Middle-earth, long Ages before the Rising of the Sun or Moon.",
"Unlike Men, the Elves are not subject to death by old age.",
},
descriptor_choices =
{
subrace =
{
Nandor = "allow",
Avari = "allow",
__ALL__ = "never",
},
},
talents = {
-- [ActorTalents.T_IMPROVED_MANA_I]=1,
},
copy = {
type = "humanoid", subtype="elf",
default_wilderness = {39, 17},
starting_zone = "tower-amon-sul",
starting_quest = "start-dunadan",
starting_intro = "elf",
},
experience = 1.05,
}

newBirthDescriptor
{
type = "subrace",
name = "Nandor",
desc = {
"Elves who turned aside from the Great Journey in the early days and settled in th east of the Misty Mountains.",
"Both the Wood-Elves of Mirkwood and the Elves of Lórien are Nandor.",
"They posses the Grace of the Eldar talent which allows them a boost of speed every once in a while.",
},
stats = { str=-2, mag=2, wil=3, cun=1, dex=1, con=0 },
experience = 1.3,
talents = { [ActorTalents.T_NANDOR_SPEED]=1 },
copy = {
life_rating = 9,
},
}</pre>

← Older revision		Revision as of 05:17, 12 October 2014
Line 133:		Line 133:
	<p>This defines out the body and inventory slots for each character, the base experience rate and starting gold and the minimum equipment each character will need to have.</p>		<p>This defines out the body and inventory slots for each character, the base experience rate and starting gold and the minimum equipment each character will need to have.</p>

−	<p>The second PD applied by the ToME module is your race, followed by subrace, found appropriate in /data/birth/races/. Races are where ToME typically grants the ~~charcter~~ their most unique abilities and major stat adjustments. Below is the PD for elves, and then a subrace of elf.</p>	+	<p>The second PD applied by the ToME module is your race, followed by subrace, found appropriate in /data/birth/races/. Races are where ToME typically grants the character their most unique abilities and major stat adjustments. Below is the PD for elves, and then a subrace of elf.</p>

← Older revision		Revision as of 14:56, 29 September 2013
Line 184:		Line 184:

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

← Older revision		Revision as of 21:08, 6 July 2013
Line 183:		Line 183:
	}</pre>		}</pre>

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

@@ Line 1: / Line 1: @@
-<h1 id="toc0">Player Descriptors: Who do you want to be today?</h1>
+=Who do you want to be today?=
-<h2 id="toc1">Important variables</h2>
+==Important variables==
@@ Line 43: / Line 43: @@
      <tr>
          <td>copy</td>
-         <td>These variables and values will be copied to the resulting player object.  See <a class="" style="" href="/web/20120511162450/http://te4.org/wiki/t4modules-npcs">t4modules npcs</a> for values.</td>
+         <td>These variables and values will be copied to the resulting player object.  See [[NPCs|NPCs]] for values.</td>
      </tr>
      <tr>

← Older revision		Revision as of 23:44, 28 May 2013
Line 182:		Line 182:
	},		},
	}</pre>		}</pre>
		+
		+	Go back to [[T4modules-module-howto-guides]]

@@ Line 90: / Line 90: @@
 <p>This guide is roughly based on the [[t4modules t3modules module_guide_part_1|te3 player descriptor guide]].</p>
-<p>In the default ToME module, you get to choose from a race, a sub-race, gender, a background, a class, and then a subclass. To the T-Engine, these are all the same thing, called 'player descriptors' (Charcter descriptors would be more accurate, but that's nitpicking), or PDs for short. PDs are what let you alter the player character in all sorts of different ways. Player descriptors typically stack, so any modifications done to one will usually add with any other modifications, rather than replacing them.</p>
+<p>In the default ToME module, you get to choose from a race, a sub-race, gender, a background, a class, and then a subclass. To the T-Engine, these are all the same thing, called 'player descriptors' (Character descriptors would be more accurate, but that's nitpicking), or PDs for short. PDs are what let you alter the player character in all sorts of different ways. Player descriptors typically stack, so any modifications done to one will usually add with any other modifications, rather than replacing them.</p>
 <p>There's no definition or distinction between different types of PDs by the engine. They can all have the same functionality, the only place any consistency is found is by the module author. So, if you only want stats to come from races, and skills from classes, you will have to make sure that only races gain stat bonuses and only classes have skill bonuses. The engine will not discriminate against this for you.</p>
-<p>All the example below will be from the ToME module, so you should be able to see pretty easily where everything came from and can easily modify it and see what happens.</p>
+<p>All the examples below will be from the ToME module, so you should be able to see pretty easily where everything came from and can easily modify it and see what happens.</p>
 <p>Possibly the most important PD is the one that the player will never see, the base descriptor, found in /data/birth/descriptors.lua. This is the one that is loaded for every character, and provides the universal traits that each character will share.  This one has been edited slightly for clarity.</p>

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

@@ Line 77: / Line 77: @@
-<h2 id="toc3">Leveling up</h2>
+==Leveling up==
 <p>Once you gain enough xp to level, the levelup() method on the player gets called.<br />
 Use this method to include specific special code that runs on a new level up, such as gaining hp and stats.</p>
@@ Line 87: / Line 87: @@
-<h2 id="toc4">Guide</h2>
+==Guide==
 <p>This guide is roughly based on the [[t4modules t3modules module_guide_part_1|te3 player descriptor guide]].</p>