Attributes (Savage) - Revision history

Rob: /* Add Attributes for Game System */

2009-01-28T02:13:04Z

Add Attributes for Game System

← Older revision		Revision as of 02:13, 28 January 2009
Line 13:		Line 13:
	Once we're confident that we have all the necessary mechanics in place for managing attributes properly, we need to define them. Open up the file "thing_attributes.dat" and we'll start adding each new attribute. [Note: For the moment, do not delete the sample attribute.]		Once we're confident that we have all the necessary mechanics in place for managing attributes properly, we need to define them. Open up the file "thing_attributes.dat" and we'll start adding each new attribute. [Note: For the moment, do not delete the sample attribute.]

	Since all of the mechanics for handling attributes is orchestrated by the underlying components, the definition of each attribute is incredibly simple. You can copy the sample attribute provided and adapt it appropriately for each attribute of the game system. Be sure to assign a suitable "explicit" tag to each attribute, with the value corresponding to the order in which the attributes are to be shown to the user. The "Agility" attribute is shown as an example below.		Since all of the mechanics for handling attributes is orchestrated by the underlying components, the definition of each attribute is incredibly simple. You can copy the sample attribute provided and adapt it appropriately for each attribute of the game system. Be sure to specify the "trtAbbrev" field with an abbreviation for the attribute. Also, be sure to assign a suitable "explicit" tag to each attribute, with the value corresponding to the order in which the attributes are to be shown to the user. The "Agility" attribute is shown as an example below.

	<pre>		<pre>
Line 22:		Line 22:
	isunique="yes"		isunique="yes"
	description="Agility is your hero's nimbleness, quickness, and dexterity.">		description="Agility is your hero's nimbleness, quickness, and dexterity.">
			<fieldval field="trtAbbrev" value="Agi"/>
	<tag group="explicit" tag="1"/>		<tag group="explicit" tag="1"/>
	</thing>		</thing>
	</pre>		</pre>

	Once you've added all the new attributes, reload the data files and verify that they all show up properly.		Once you've added all the new attributes, reload the data files and verify that they all show up properly.

	===Delete Sample Attribute===		===Delete Sample Attribute===

Rob: Attributes (Skeleton) moved to Attributes (Savage)

2008-12-18T04:16:06Z

Attributes (Skeleton) moved to Attributes (Savage)

← Older revision	Revision as of 04:16, 18 December 2008
(No difference)

Rob at 11:22, 17 December 2008

2008-12-17T11:22:51Z

← Older revision		Revision as of 11:22, 17 December 2008
Line 13:		Line 13:
	Once we're confident that we have all the necessary mechanics in place for managing attributes properly, we need to define them. Open up the file "thing_attributes.dat" and we'll start adding each new attribute. [Note: For the moment, do not delete the sample attribute.]		Once we're confident that we have all the necessary mechanics in place for managing attributes properly, we need to define them. Open up the file "thing_attributes.dat" and we'll start adding each new attribute. [Note: For the moment, do not delete the sample attribute.]

	Since all of the mechanics for handling attributes is ~~handled~~ by the underlying components, the definition of each attribute is incredibly simple. You can copy the sample attribute provided and adapt it appropriately for each attribute of the game system. The "Agility" attribute is shown as an example below.		Since all of the mechanics for handling attributes is orchestrated by the underlying components, the definition of each attribute is incredibly simple. You can copy the sample attribute provided and adapt it appropriately for each attribute of the game system. Be sure to assign a suitable "explicit" tag to each attribute, with the value corresponding to the order in which the attributes are to be shown to the user. The "Agility" attribute is shown as an example below.

	<pre>		<pre>

Rob at 03:17, 17 December 2008

2008-12-17T03:17:47Z

← Older revision		Revision as of 03:17, 17 December 2008
Line 1:		Line 1:
	{{context\|Authoring Examples\|Savage Worlds Walk-Through}}		{{context\|Authoring Examples\|Savage Worlds Walk-Through}}

			===Overview===

	Every game system has a core set of attributes, although they are sometimes referred to using a different term (e.g. stats, characteristics, etc.). These attributes are the cornerstone of the game system and everything builds upon them, so they are the natural next step.		Every game system has a core set of attributes, although they are sometimes referred to using a different term (e.g. stats, characteristics, etc.). These attributes are the cornerstone of the game system and everything builds upon them, so they are the natural next step.

Rob: New page: {{context|Authoring Examples|Savage Worlds Walk-Through}} Every game system has a core set of attributes, although they are sometimes referred to using a different term (e.g. stats, chara...

2008-12-17T02:58:53Z

New page: {{context|Authoring Examples|Savage Worlds Walk-Through}} Every game system has a core set of attributes, although they are sometimes referred to using a different term (e.g. stats, chara...

New page

{{context|Authoring Examples|Savage Worlds Walk-Through}}

Every game system has a core set of attributes, although they are sometimes referred to using a different term (e.g. stats, characteristics, etc.). These attributes are the cornerstone of the game system and everything builds upon them, so they are the natural next step.

===How to Handle Attributes?===

Looking at how Savage Worlds works, there are five core attributes to the game, and we've already made a number of changes that apply to traits in general. But is there anything else of interest the needs to be handled specifically for attributes? Nothing else is apparent, so we don't need to make any changes to the "Attribute" component at this point.

===Add Attributes for Game System===

Once we're confident that we have all the necessary mechanics in place for managing attributes properly, we need to define them. Open up the file "thing_attributes.dat" and we'll start adding each new attribute. [Note: For the moment, do not delete the sample attribute.]

Since all of the mechanics for handling attributes is handled by the underlying components, the definition of each attribute is incredibly simple. You can copy the sample attribute provided and adapt it appropriately for each attribute of the game system. The "Agility" attribute is shown as an example below.

<pre>
<thing
id="attrAgi"
name="Agility"
compset="Attribute"
isunique="yes"
description="Agility is your hero's nimbleness, quickness, and dexterity.">
<tag group="explicit" tag="1"/>
</thing>
</pre>

Once you've added all the new attributes, reload the data files and verify that they all show up properly.

===Delete Sample Attribute===

Now that our attributes appear to be working properly, we can delete the sample attribute. Unfortunately, this will cause our data files to cease compiling successfully. The reason is that the sample attribute is actually referenced in places within the Skeleton data files (and now our game system). So we need to locate those places and correct them.

The only place of importance where the sample attribute is referenced happens to be as the linked attribute for the skills given in "thing_skills.dat". Open this file and locate references to "attrSam" - there should be three of them. We're going to be re-working skills in a moment, so we simply need a temporary fix to make the compiler happy. Change each of the skills to reference a different attribute instead, such as "attrAgi".

At this point, you should be able to compile and reload the data files. The five attributes for Savage Worlds are now in place and behaving as they should.