Creature Customization (Savage) - Revision history

Rob: /* Bounding the Derived Traits */

2009-02-12T01:53:49Z

Bounding the Derived Traits

← Older revision		Revision as of 01:53, 12 February 2009
Line 129:		Line 129:
	<pre>		<pre>
	~setup the proper floor values for each trait		~setup the proper floor values for each trait
	hero.child[trPace].field[trtFloor].value = 1		hero.child[trPace].field[trtFloor].value = 0
	hero.child[trParry].field[trtFloor].value = 2		hero.child[trParry].field[trtFloor].value = 2
	hero.child[trTough].field[trtFloor].value = 2		hero.child[trTough].field[trtFloor].value = 2

Rob: /* Alternate Field for User Adjustment */

2009-02-12T01:01:02Z

Alternate Field for User Adjustment

← Older revision		Revision as of 01:01, 12 February 2009
Line 51:		Line 51:
	<!-- Display the final calculated value to the user -->		<!-- Display the final calculated value to the user -->
	<finalize><![CDATA[		<finalize><![CDATA[
	@text = field[~~trtDisplay~~].~~text~~		@text = field[trtFinal].value
	]]></finalize>		]]></finalize>
	</field>		</field>

Rob: /* Alternate Field for User Adjustment */

2009-02-12T01:00:45Z

Alternate Field for User Adjustment

← Older revision		Revision as of 01:00, 12 February 2009
Line 33:		Line 33:
	The good news is that we can simply create a '''''different''''' field for our needs and proceed with our original plan. Our new field will behave very similarly to "trtUser", so we'll start by cloning it. The field is only needed for derived traits, so we'll add it to the "Derived" component.		The good news is that we can simply create a '''''different''''' field for our needs and proceed with our original plan. Our new field will behave very similarly to "trtUser", so we'll start by cloning it. The field is only needed for derived traits, so we'll add it to the "Derived" component.

	We can re-use the "trtMinimum" and "trtMaximum" fields for bounding, and we won't need to do any special handling of the bounds. We want to display the final value within the incrementer, which we can pull from the "trtDisplay" field. Lastly, we want to allow the user to edit that value directly, so we'll include delta handling for our field. Our resulting field should look like the following.		We can re-use the "trtMinimum" and "trtMaximum" fields for bounding, and we won't need to do any special handling of the bounds. We want to display the final value within the incrementer, which we can pull from the "trtFinal" field. We do not want to use the "trtDisplay" field, because the that field may contain secondary movement (e.g. "6/10" for burrowing) and it won't fit within the incrementer. Lastly, we want to allow the user to edit that value directly, so we'll include delta handling for our field. Our resulting field should look like the following.

	<pre>		<pre>

Rob at 05:00, 11 February 2009

2009-02-11T05:00:05Z

← Older revision		Revision as of 05:00, 11 February 2009
Line 392:		Line 392:

	With the script in place, we can reload the data files and everything works the way we want it. We can easily mix and match bootstrapped abilities with user-added abilities, and the user can properly customize any abilities that he adds.		With the script in place, we can reload the data files and everything works the way we want it. We can easily mix and match bootstrapped abilities with user-added abilities, and the user can properly customize any abilities that he adds.

	~~===Next===~~

Rob: /* Next */

2009-02-11T04:56:22Z

Show changes

Rob: /* User Manipulation of Derived Traits */

2009-02-11T04:52:10Z

User Manipulation of Derived Traits

← Older revision		Revision as of 04:52, 11 February 2009
Line 75:		Line 75:
	</pre>		</pre>

	===User Manipulation ~~of Derived Traits~~===		====Hookup User Manipulation====

	At this point, we have the basic internal workings in place. Before we spend more time here, let's see how things work within the interface. We need to expose the field value for change by the user. This entails modifying the "baTrtPick" template that is used to show derived traits on the "Basics" tab. If we want the user to modify the value, we need to add a new incrementer portal. We can use a simple incrementer style that is provided by the Skeleton files, which results in the new portal shown below.		At this point, we have the basic internal workings in place. Before we spend more time here, let's see how things work within the interface. We need to expose the field value for change by the user. This entails modifying the "baTrtPick" template that is used to show derived traits on the "Basics" tab. If we want the user to modify the value, we need to add a new incrementer portal. We can use a simple incrementer style that is provided by the Skeleton files, which results in the new portal shown below.

Rob at 04:51, 11 February 2009

2009-02-11T04:51:16Z

Show changes

Rob: /* Assigning Derived Traits */

2009-02-11T04:36:55Z

Assigning Derived Traits

Show changes

Rob: /* Next */

2009-02-11T04:07:54Z

Show changes

Rob: New page: {{context|Authoring Examples|Savage Worlds Walk-Through}} ===Overview=== In the previous sections, we managed to get creatures working smoothly. However, there was one area where we defi...

2009-02-11T04:06:33Z

New page: {{context|Authoring Examples|Savage Worlds Walk-Through}} ===Overview=== In the previous sections, we managed to get creatures working smoothly. However, there was one area where we defi...

New page

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

===Overview===

In the previous sections, we managed to get creatures working smoothly. However, there was one area where we definitely could have provided a bit more flexibility. We allowed the user to customize attributes and skills from their starting points, but we did not do so for derived traits and abilities.

What if the GM wants a creature that's a little bit faster or tougher than normal? The answer is that we should allow him to adjust any of the creature's derived traits in whatever way suits his needs.

What if the GM wants to create an undead version of a normal creature? The simple solution would be to add the "Undead" ability to that creature, which will automatically add the Toughness adjustment and other notes for reference.

The focus of the sections below is on adding that flexibility to our data files.

===Next===