Tactical Console (Savage) - Revision history

Rob: /* Basic Actor Information */

2009-01-31T11:38:32Z

Basic Actor Information

← Older revision		Revision as of 11:38, 31 January 2009
Line 44:		Line 44:

	~append the parry trait		~append the parry trait
	@text &= "{horz 10}{size 30}Pa: {size 36}" & #trait[trParry]		@text &= "{horz 10}{size 30}Pr: {size 36}" & #trait[trParry]

	~append the toughness trait		~append the toughness trait

Rob: /* Non-Combat Content */

2009-01-28T00:10:47Z

Non-Combat Content

← Older revision		Revision as of 00:10, 28 January 2009
Line 83:		Line 83:
	Since we copied our things when defining them, many of the standard skills are assigned the tag, while others are not. In addition, special skills like the arcane skills are not being assigned the tag, which means they are not included in the list. The arcane skills are just as important and should be displayed. We probably can't fit all skills in the available space, so we need to choose the skills to include. So let's go through all the skills and decide which ones should (or shouldn't) be included in the list. Be sure to check all skills, including those associated with arcane background and powers. Any skill to be shown must be assigned the tag.		Since we copied our things when defining them, many of the standard skills are assigned the tag, while others are not. In addition, special skills like the arcane skills are not being assigned the tag, which means they are not included in the list. The arcane skills are just as important and should be displayed. We probably can't fit all skills in the available space, so we need to choose the skills to include. So let's go through all the skills and decide which ones should (or shouldn't) be included in the list. Be sure to check all skills, including those associated with arcane background and powers. Any skill to be shown must be assigned the tag.

	Once we've identified the appropriate skills, we need to review the output being generated. Everything looks good, ~~except for Knowledge skills. Any skill with a domain~~ is ~~not including that domain. So we need to revise the output slightly. In the center of the Label script for the "peace" portal, the name needs~~ to ~~be determined differently. Replace the current line of code with the lines shown below.~~		Once we've identified the appropriate skills, we need to review the output being generated. Everything looks good, so our non-combat content is ready to go.

	~~<pre>~~
	~~~use the short name for display and append any domain~~
	~~name = eachpick.field[shortname].text~~
	~~if (eachpick.tagis[component.Skill] + eachpick.tagis[User.NeedDomain] >= 2) then~~
	~~name &= "(" & eachpick.field[domDomain]~~.~~text & ")"~~
	~~endif~~
	~~</pre>~~

	===Combat Content===		===Combat Content===

Rob: /* Damage and Other Actor Manipulations */

2009-01-26T12:00:25Z

Damage and Other Actor Manipulations

← Older revision		Revision as of 12:00, 26 January 2009
Line 123:		Line 123:

	===Damage and Other Actor Manipulations===		===Damage and Other Actor Manipulations===

			To the lower right of the basic character information, a button appears with a skull on it. Clicking this button brings up a form where various in-play adjustments can be made directly to the character. This includes damage, resource tracking, activation of abilities, and even the tracking of combat notes.

			The contents of this form are controlled in the file "form_manipulate.dat". However, it's unlikely you'll need to make any adjustments. The form utilizes the same layout that is defined for use on the "In-Play" tab. As such, any changes or refinements you make to the "In-Play" tab are automatically incorporated into this form. The only time you'll need to make changes is when you want to do something different for manipulation through the TacCon that doesn't appear on the "In-Play" tab. For our purposes, the form has everything we need on it, so there's nothing for us to do.

Rob: /* Initiative Handling */

2009-01-26T11:53:29Z

Initiative Handling

← Older revision		Revision as of 11:53, 26 January 2009
Line 119:		Line 119:

	===Initiative Handling===		===Initiative Handling===

			During combat, an increment appears on the far right where you can manipulate the initiative for each character. For most game systems, initiative is a relatively quick and painless process. However, Savage Worlds uses a very different approach to initiative - a deck of cards. The Kit can support this non-standard mechanism, but it's not nearly as easy as a more traditional initiative. Since integrating the proper initiative for Savage Worlds will entail quite a few steps, we'll cover the initiative in a completely separate entry in this walk-through.

	===Damage and Other Actor Manipulations===		===Damage and Other Actor Manipulations===

Rob: /* Combat Actions */

2009-01-26T11:49:08Z

Combat Actions

@@ Line 100: / Line 100: @@
 ===Combat Actions===
 ===Initiative Handling===
 ===Damage and Other Actor Manipulations===

Rob: /* Combat Content */

2009-01-26T10:35:25Z

Combat Content

← Older revision		Revision as of 10:35, 26 January 2009
Line 94:		Line 94:

	===Combat Content===		===Combat Content===

			Once combat begins, the skills shown in the center region are swapped out for information that is more appropriate during combat. More specifically, the first three weapons possessed by the character are shown, with any equipped weapon(s) being shown before unequipped weapons. For each weapon, the attack roll and damage are shown. This is handled by the "weapon" portal, which uses a Label script to synthesize its output.

			The default output provided by the Skeleton files is perfectly reasonable, so there really isn't anything we need to do here.

	===Combat Actions===		===Combat Actions===

Rob: /* Important Traits */

2009-01-26T10:27:18Z

Important Traits

← Older revision		Revision as of 10:27, 26 January 2009
Line 73:		Line 73:
	===Important Traits===		===Important Traits===

	The column of traits to the right of the basic character information is managed via the "traits" portal. All of the traits that should appear in the list are identified by the "DashTacCon.Traits" tag. Since there are four derived traits in Savage Worlds, we~~'ll~~ include ~~all of them~~ in the list. Open the file "thing_traits.dat" and make sure that ~~the four~~ derived traits possess the tag.		The column of traits to the right of the basic character information is managed via the "traits" portal. All of the traits that should appear in the list are identified by the "DashTacCon.Traits" tag. There is room to show up to three different traits in this portal. Since there are four derived traits in Savage Worlds, we need to decide which one to include in the list. Since we already show Parry and Toughness in the basic information region, we really don't need to duplicate them here, so we only include Pace and Charisma. Open the file "thing_traits.dat" and make sure that these two derived traits possess the tag.

	===Non-Combat Content===		===Non-Combat Content===

Rob: /* Non-Combat Content */

2009-01-26T10:18:47Z

Non-Combat Content

← Older revision		Revision as of 10:18, 26 January 2009
Line 82:		Line 82:

	Since we copied our things when defining them, many of the standard skills are assigned the tag, while others are not. In addition, special skills like the arcane skills are not being assigned the tag, which means they are not included in the list. The arcane skills are just as important and should be displayed. We probably can't fit all skills in the available space, so we need to choose the skills to include. So let's go through all the skills and decide which ones should (or shouldn't) be included in the list. Be sure to check all skills, including those associated with arcane background and powers. Any skill to be shown must be assigned the tag.		Since we copied our things when defining them, many of the standard skills are assigned the tag, while others are not. In addition, special skills like the arcane skills are not being assigned the tag, which means they are not included in the list. The arcane skills are just as important and should be displayed. We probably can't fit all skills in the available space, so we need to choose the skills to include. So let's go through all the skills and decide which ones should (or shouldn't) be included in the list. Be sure to check all skills, including those associated with arcane background and powers. Any skill to be shown must be assigned the tag.

			Once we've identified the appropriate skills, we need to review the output being generated. Everything looks good, except for Knowledge skills. Any skill with a domain is not including that domain. So we need to revise the output slightly. In the center of the Label script for the "peace" portal, the name needs to be determined differently. Replace the current line of code with the lines shown below.

			<pre>
			~use the short name for display and append any domain
			name = eachpick.field[shortname].text
			if (eachpick.tagis[component.Skill] + eachpick.tagis[User.NeedDomain] >= 2) then
			name &= "(" & eachpick.field[domDomain].text & ")"
			endif
			</pre>

	===Combat Content===		===Combat Content===

Rob: /* Non-Combat Content */

2009-01-26T10:03:40Z

Non-Combat Content

← Older revision		Revision as of 10:03, 26 January 2009
Line 76:		Line 76:

	===Non-Combat Content===		===Non-Combat Content===

			The information shown in the center changes based on whether the party is in combat or not. When not in combat, the region should show useful facets of the character that a GM will refer to during play. For example, the character's skills, or perhaps just the most commonly used skills in a game where all characters possess a large number of skills.

			In Savage Worlds, characters purchase their skills, so we can simply show all of the skills for each character. The region is controlled via the "peace" portal, which uses a Label script to synthesize its contents. All of the items shown in the region are identified by possessing the "DashTacCon.NonCombat" tag.

			Since we copied our things when defining them, many of the standard skills are assigned the tag, while others are not. In addition, special skills like the arcane skills are not being assigned the tag, which means they are not included in the list. The arcane skills are just as important and should be displayed. We probably can't fit all skills in the available space, so we need to choose the skills to include. So let's go through all the skills and decide which ones should (or shouldn't) be included in the list. Be sure to check all skills, including those associated with arcane background and powers. Any skill to be shown must be assigned the tag.

	===Combat Content===		===Combat Content===

Rob at 09:46, 26 January 2009

2009-01-26T09:46:59Z

← Older revision		Revision as of 09:46, 26 January 2009
Line 44:		Line 44:

	~append the parry trait		~append the parry trait
	@text &= "{horz 6}{size 30}Pa: {size 36}" & #trait[trParry]		@text &= "{horz 10}{size 30}Pa: {size 36}" & #trait[trParry]

	~append the toughness trait		~append the toughness trait
Line 70:		Line 70:
	</portal>		</portal>
	</pre>		</pre>

			===Important Traits===

			The column of traits to the right of the basic character information is managed via the "traits" portal. All of the traits that should appear in the list are identified by the "DashTacCon.Traits" tag. Since there are four derived traits in Savage Worlds, we'll include all of them in the list. Open the file "thing_traits.dat" and make sure that the four derived traits possess the tag.

	===Non-Combat Content===		===Non-Combat Content===