Weird Science Gizmos (Savage) - Revision history

Rob: /* Revising the Template */

2009-01-31T12:12:28Z

Revising the Template

← Older revision		Revision as of 12:12, 31 January 2009
Line 197:		Line 197:
	<portal		<portal
	id="menu"		id="menu"
	style="~~menuNormal~~">		style="menuSmall">
	<menu_things		<menu_things
	field="powSkill"		field="powSkill"
Line 268:		Line 268:
	~position the gizmo-related portals horizontally		~position the gizmo-related portals horizontally
	portal[lblmenu].left = portal[details].left		portal[lblmenu].left = portal[details].left
	perform portal[menu].alignrel[ltor,lblmenu,2]		perform portal[menu].alignrel[ltor,lblmenu,3]
	portal[menu].width = ~~105~~		portal[menu].width = 135
	perform portal[lblstorage].alignrel[ltor,menu,15]		perform portal[lblstorage].alignrel[ltor,menu,10]
	perform portal[storage].alignrel[ltor,lblstorage,2]		perform portal[storage].alignrel[ltor,lblstorage,2]
	portal[storage].width = 25		portal[storage].width = 25

Rob: /* Tracking Power Points */

2009-01-24T02:30:15Z

Tracking Power Points

← Older revision		Revision as of 02:30, 24 January 2009
Line 305:		Line 305:
	</pre>		</pre>

	The next thing we need to do is setup each gizmo to possess the proper number of power points. The actual number of power points used by the tracker is pulled from the "trkMax" field. So we need to make sure that this field is setup correctly. We'll define a new Eval script for this purpose. In the script, we'll pull the power points for a foreign gizmo from the "powStorage" field that the user will specify. For a gizmo belonging to a character with "Weird Science", we need to use the character's maximum power, which can be obtained from the "trkPower" tracker. Since the value we set must be in place before the tracker calculates the amount remaining, we must be sure to schedule our new script before the calculation occurs. This yields the new Eval script below.		The next thing we need to do is setup each gizmo to possess the proper number of power points. The actual number of power points used by the tracker is pulled from the "trkMax" field. So we need to make sure that this field is setup correctly. We'll define a new Eval script for this purpose. In the script, we'll pull the power points for a foreign gizmo from the "powStorage" field that the user will specify. For a gizmo belonging to a character with "Weird Science", we need to use the character's maximum power, which can be obtained from the "trkPower" tracker. Since the value we set must be in place before the tracker calculates the amount remaining, we must be sure to schedule our new script before the calculation occurs. This yields the new Eval script below, which we'll define for the component.

	<pre>		<pre>

Rob: /* Adding the Fields */

2009-01-24T02:29:34Z

Adding the Fields

← Older revision		Revision as of 02:29, 24 January 2009
Line 167:		Line 167:
	</pre>		</pre>

	Now that we've added the fields, we should also determine when we'll be using them. This will be dictated by the presence of the "Helper.Gizmo" and "Helper.Foreign" tags. The latter tag will be handled exclusively via the table portal itself, with shared gizmos receiving the tag. However, the "Helper.Gizmo" tag needs to be assigned correctly, so we'll add an Eval script for that purpose. There are two situations when we need to assign the tag. The first is when the power has the "Helper.Foreign" tag, since we know the power is intended for use as a shared gizmo. The second is when the character possesses the "Weird Science" arcane background, since all of his powers must be treated as gizmos. This results in the Eval script below.		Now that we've added the fields, we should also determine when we'll be using them. This will be dictated by the presence of the "Helper.Gizmo" and "Helper.Foreign" tags. The latter tag will be handled exclusively via the table portal itself, with shared gizmos receiving the tag. However, the "Helper.Gizmo" tag needs to be assigned correctly, so we'll add an Eval script to the component for that purpose. There are two situations when we need to assign the tag. The first is when the power has the "Helper.Foreign" tag, since we know the power is intended for use as a shared gizmo. The second is when the character possesses the "Weird Science" arcane background, since all of his powers must be treated as gizmos. This results in the Eval script below.

	<pre>		<pre>

Rob: /* Validation */

2009-01-24T02:28:46Z

Validation

@@ Line 336: / Line 336: @@
 ===Validation===
--verify gizmos have linked skill assigned
+There are a couple things left that we have not done. Conditions exist that we should be reporting as an error to the user. If a user doesn't select a skill for a gizmo, we should report it as an error. Similarly, if the user doesn't specify a non-zero number of power points for a foreign gizmo, we should also report an error. We can resolve each of these by adding suitable Eval Rule scripts to the component, as shown below.
--verify foreign gizmos have non-zero power points assigned
--highlight menu in red if no selection is chosen
+<pre>

Rob: /* Tracking Power Points */

2009-01-24T02:22:52Z

Tracking Power Points

← Older revision		Revision as of 02:22, 24 January 2009
Line 326:		Line 326:
	</pre>		</pre>

			We can now test out how gizmos are working. The trackers show up properly for each gizmo, and the total points for each gizmo reflect the proper values. The only problem is that resetting a gizmo on the "In-Play" tab sets the value to zero. When a gizmo is reset, it should be assigned the maximum. We can fix this by changing the behavior of the tracker, which requires assigning the "Helper.ResetMax" tag. Since we need this behavior on all gizmos, we can assign it to the "Power" component with the line below.

			<pre>
			<tag group="Helper" tag="ResetMax"/>
			</pre>

			Gizmos are now working the way the should.
	~~Add a gizmo to all gizmos start with~~ the ~~full number of power points, we're going to need them to b~~

	~~-add tag to reset trackers to maximum~~

	===Validation===		===Validation===

Rob: /* Tracking Power Points */

2009-01-24T02:19:10Z

Tracking Power Points

@@ Line 279: / Line 279: @@
 ===Tracking Power Points===
--add Tracker component to Power compset
+Gizmos are now appearing as they should within the tables, but they still aren't behaving correctly. Each gizmo needs to appear in the list of trackers on the "In-Play" tab. This requires that we make every power incorporate all the behaviors of a tracker. To do that, we must modify the "Power" component set to include the "Tracker" component, which yields the revised component set below.
 -add tag to reset trackers to maximum
 ===Validation===

Rob: /* Revising the Template */

2009-01-24T02:04:49Z

Revising the Template

@@ Line 226: / Line 226: @@
 </pre>
-Now that the portals are defined, we can manage them appropriately within the Position script.
+Now that the portals are defined, we can manage them appropriately within the Position script. Since the visibility of the gizmo-related portals will influence the total height of the template, we need to determine their visibility first. The menu portal and its associated label are only shown for gizmos. The power points edit portal and its associated label are only shown for foreign gizmos. This results in the new script code below being inserted at the top.
--determine whether menu and edit portals are visible - impacts height of template
+<pre>
--position menu and edit portals
+~determine if the menu portal and label should be visible or not
 ===Tracking Power Points===

Rob: /* Revising the Template */

2009-01-24T01:44:46Z

Revising the Template

@@ Line 180: / Line 180: @@
 ===Revising the Template===
--add portals to template for specifying skill and power points
+Arcane powers for a character with the "Weird Science" arcane background must be treated as gizmos on the "Arcane" tab. So the same template will be used for both arcane powers and gizmos. We're also going to be using this template to assign the power points for shared gizmos on the "Gear" tab.
 -determine whether menu and edit portals are visible - impacts height of template
 -position menu and edit portals

Rob at 01:29, 24 January 2009

2009-01-24T01:29:58Z

← Older revision		Revision as of 01:29, 24 January 2009
Line 179:		Line 179:

	===Revising the Template===		===Revising the Template===

			-add portals to template for specifying skill and power points
			-determine whether menu and edit portals are visible - impacts height of template
			-position menu and edit portals

	===Tracking Power Points===		===Tracking Power Points===

	~~===Validation===~~


	~~-add fields for linked skill and power points~~
	-add Tracker component to Power compset		-add Tracker component to Power compset
	~~-add portals to template for specifying skill and power points~~
	~~-determine whether menu and edit portals are visible - impacts height of template~~
	~~-position menu and edit portals~~
	-add tag to reset trackers to maximum		-add tag to reset trackers to maximum
			-modify script to hide non-gizmos from tracker list on in-play tab
	-add script to setup power points		-add script to setup power points
	-hide non-gizmos from list of trackers on in-play tab		-hide non-gizmos from list of trackers on in-play tab

			===Validation===

	-verify gizmos have linked skill assigned		-verify gizmos have linked skill assigned
	-verify foreign gizmos have non-zero power points assigned		-verify foreign gizmos have non-zero power points assigned
	-highlight menu in red if no selection is chosen		-highlight menu in red if no selection is chosen

Rob: /* Adding the Fields */

2009-01-24T01:28:05Z

Adding the Fields

← Older revision		Revision as of 01:28, 24 January 2009
Line 167:		Line 167:
	</pre>		</pre>

	Now that we've added the fields, we should also determine when ~~to use~~ them.		Now that we've added the fields, we should also determine when we'll be using them. This will be dictated by the presence of the "Helper.Gizmo" and "Helper.Foreign" tags. The latter tag will be handled exclusively via the table portal itself, with shared gizmos receiving the tag. However, the "Helper.Gizmo" tag needs to be assigned correctly, so we'll add an Eval script for that purpose. There are two situations when we need to assign the tag. The first is when the power has the "Helper.Foreign" tag, since we know the power is intended for use as a shared gizmo. The second is when the character possesses the "Weird Science" arcane background, since all of his powers must be treated as gizmos. This results in the Eval script below.

	~~While we're modifying~~ the "~~Power~~" ~~component~~, ~~we might as well also handle~~ the ~~assignment of~~ the "Helper.Gizmo" tag~~. We haven't done this yet~~, ~~and~~ we'~~re going to be putting it to use shortly~~. There are two situations ~~where~~ we~~'ll~~

			<pre>
			<eval index="3" phase="Setup" priority="5000"><![CDATA[
			~it's a gizmo if it's foreign or if the character is a weird scientist
			if (tagis[Helper.Foreign] + hero.tagis[Arcane.WeirdSci] <> 0) then
			perform assign[Helper.Gizmo]
			endif
			]]></eval>
			</pre>

	===Revising the Template===		===Revising the Template===