Weapons (Savage) - Revision history

Rob at 05:51, 18 February 2009

2009-02-18T05:51:47Z

@@ Line 157: / Line 157: @@
 Since we'll want to always use this field for showing damage to the user, it needs to exist for all weapons. That means it needs to be defined on the "WeaponBase" component. If we have a ranged weapon that doesn't include the "wpDie" field, we must be careful not to try accessing the non-existent field. We can safeguard against this by checking for the "component.WeapMelee" tag before accessing the weapon die logic.
-The role of our new field will be solely for display of the final damage for a weapon, so we'll name it accordingly. We also need to make sure to append any weapon bonus to the final damage. Putting all this together results in the new field definition shown below.
+The role of our new field will be solely for display of the final damage for a weapon, so we'll name it accordingly. Putting all this together results in the new field definition shown below.
 <pre>
@@ Line 178: / Line 178: @@
          endif
        @text = "Str+d" & die
        endif
      ]]></finalize>
@@ Line 342: / Line 337: @@
 At this point, our strength requirements logic should be operating properly.
 ===Add Hand Weapons===

Rob: /* Minimum Strength Requirement */

2009-02-12T00:33:49Z

Minimum Strength Requirement

← Older revision		Revision as of 00:33, 12 February 2009
Line 53:		Line 53:

	~apply any penalty required with the specific weapon		~apply any penalty required with the specific weapon
	field[wpPenalty].value = #trait[attrStr] - field[wpStrReq].value		if (#trait[attrStr] < field[wpStrReq].value) then
			field[wpPenalty].value = #trait[attrStr] - field[wpStrReq].value
			endif

	~if not equipped, there's nothing more to do		~if not equipped, there's nothing more to do

Rob: /* Revise Table for Hand Weapons */

2009-02-10T04:29:31Z

Revise Table for Hand Weapons

← Older revision		Revision as of 04:29, 10 February 2009
Line 520:		Line 520:
	~position the attack portal to the left of damage column; we want the		~position the attack portal to the left of damage column; we want the
	~attack to be centered in its own column relative to a centerpoint position		~attack to be centered in its own column relative to a centerpoint position
	perform portal[attack].centerpoint[horz,~~195~~]		perform portal[attack].centerpoint[horz,190]

	~position the name on the left and let it use all available space		~position the name on the left and let it use all available space

Rob: /* Revise Table for Hand Weapons */

2009-02-10T04:16:07Z

Revise Table for Hand Weapons

← Older revision		Revision as of 04:16, 10 February 2009
Line 508:		Line 508:
	~position the range portal to the left of the delete button; we want the		~position the range portal to the left of the delete button; we want the
	~damage to be centered in its own column relative to a centerpoint position		~damage to be centered in its own column relative to a centerpoint position
	perform portal[range].centerpoint[horz,~~335~~]		perform portal[range].centerpoint[horz,340]

	~position the AP portal to the left of the range column; we want the AP to		~position the AP portal to the left of the range column; we want the AP to
	~be centered in its own column relative to a centerpoint position		~be centered in its own column relative to a centerpoint position
	perform portal[piercing].centerpoint[horz,~~280~~]		perform portal[piercing].centerpoint[horz,290]

	~position the damage portal to the left of the AP column; we want the damage		~position the damage portal to the left of the AP column; we want the damage

Rob: /* Add Hand Weapons */

2009-02-10T04:10:01Z

Add Hand Weapons

← Older revision		Revision as of 04:10, 10 February 2009
Line 350:		Line 350:
	name="Greatsword"		name="Greatsword"
	compset="Melee"		compset="Melee"
	description="~~Description goes here~~">		description="">
	~~<fieldval field="wpDamage" value="Str+4"/>~~
	~~<fieldval field="wpStrReq" value="5"/~~>
	<fieldval field="wpParry" value="-1"/>		<fieldval field="wpParry" value="-1"/>
	<fieldval field="grCost" value="400"/>		<fieldval field="grCost" value="400"/>
	<fieldval field="~~grWeight~~" value="12"/>		<fieldval field="gearWeight" value="12"/>
	<usesource id="TimeMedi"/>		<usesource source="TimeMedi"/>
	<usesource id="TimePowder"/>		<usesource source="TimePowder"/>
			<tag group="WeaponDie" tag="5"/>
	<tag group="WeaponType" tag="MedBlades"/>		<tag group="WeaponType" tag="MedBlades"/>
	<tag group="Equipment" tag="TwoHand"/>		<tag group="Equipment" tag="TwoHand"/>
Line 366:		Line 365:
	name="Spear"		name="Spear"
	compset="Melee"		compset="Melee"
	description="~~Description goes here~~">		description="">
	~~<fieldval field="wpDamage" value="Str+2"/>~~
	~~<fieldval field="wpStrReq" value="3"/~~>
	<fieldval field="wpParry" value="1"/>		<fieldval field="wpParry" value="1"/>
	<fieldval field="wpReach" value="1"/>		<fieldval field="wpReach" value="1"/>
	<fieldval field="grCost" value="~~250~~"/>		<fieldval field="grCost" value="100"/>
	<fieldval field="~~grWeight~~" value="5"/>		<fieldval field="gearWeight" value="5"/>
	<usesource id="TimeMedi"/>		<usesource source="TimeMedi"/>
	<usesource id="TimePowder"/>		<usesource source="TimePowder"/>
			<tag group="WeaponDie" tag="3"/>
	<tag group="WeaponType" tag="MedPoles"/>		<tag group="WeaponType" tag="MedPoles"/>
	<tag group="Equipment" tag="TwoHand"/>		<tag group="Equipment" tag="TwoHand"/>
Line 383:		Line 381:
	name="Survival Knife"		name="Survival Knife"
	compset="Melee"		compset="Melee"
	description="~~Description goes here~~">		description="">
	~~<fieldval field="wpDamage" value="Str+1"/~~>
	<fieldval field="wpSpecial" value="Contains supplies that add +1 to Survival rolls"/>		<fieldval field="wpSpecial" value="Contains supplies that add +1 to Survival rolls"/>
	<fieldval field="grCost" value="50"/>		<fieldval field="grCost" value="50"/>
	<fieldval field="~~grWeight~~" value="3"/>		<fieldval field="gearWeight" value="3"/>
	<usesource id="TimeModern"/>		<usesource source="TimeModern"/>
			<tag group="WeaponDie" tag="2"/>
	<tag group="WeaponType" tag="ModMelee"/>		<tag group="WeaponType" tag="ModMelee"/>
	<eval index="1" phase="PreTraits" priority="5000">		<eval index="1" phase="PreTraits" priority="5000">
	<before name="Calc trtFinal"/><![CDATA[		<before name="Calc trtFinal"/><![CDATA[
	#traitroll[skSurvival] += 1		perform #traitroll[skSurvival,+,1,"Survival Knife"]
	]]></eval>		]]></eval>
	</thing>		</thing>
	~~</pre>~~

	While we're adding all of the hand weapons, we also need to revamp the provided "Unarmed Strike" weapon so that it behaves properly as a Savage Worlds weapon. The revised version should look similar to the following.		While we're adding all of the hand weapons, we also need to revamp the provided "Unarmed Strike" weapon so that it behaves properly as a Savage Worlds weapon. The revised version should look similar to the following.
Line 404:		Line 401:
	name="Unarmed Strike"		name="Unarmed Strike"
	compset="Melee"		compset="Melee"
	description="~~Description goes here~~"		description=""
	isunique="yes"		isunique="yes"
	holdable="no">		holdable="no">
Line 410:		Line 407:
	<fieldval field="wpSpecial" value=""/>		<fieldval field="wpSpecial" value=""/>
	<fieldval field="grCost" value="0"/>		<fieldval field="grCost" value="0"/>
	<fieldval field="~~grWeight~~" value="0"/>		<fieldval field="gearWeight" value="0"/>
	<tag group="Equipment" tag="Natural"/>		<tag group="Equipment" tag="Natural"/>
	</thing>		</thing>
	</pre>		</pre>

Rob: /* Parry and Reach */

2009-02-10T03:47:16Z

Parry and Reach

← Older revision		Revision as of 03:47, 10 February 2009
Line 213:		Line 213:
	<after name="Downgrade Weapon Die"/><![CDATA[		<after name="Downgrade Weapon Die"/><![CDATA[
	if (field[grIsEquip].value <> 0) then		if (field[grIsEquip].value <> 0) then
	if (tagis[Helper.BadStrReq] = 0) then		~negative adjustments are always applied
			if (field[wpParry].value < 0) then
			perform #traitadjust[trParry,+,field[wpParry].value,"Equipped Weapon"]
			~otherwise, adjustments are only applied when the strength is satisfied
			elseif (tagis[Helper.BadStrReq] = 0) then
	perform #traitadjust[trParry,+,field[wpParry].value,"Equipped Weapon"]		perform #traitadjust[trParry,+,field[wpParry].value,"Equipped Weapon"]
	endif		endif

Rob: /* Parry and Reach */

2009-02-10T03:29:23Z

Parry and Reach

← Older revision		Revision as of 03:29, 10 February 2009
Line 219:		Line 219:
	</pre>		</pre>

	Again as we did for armor piercing, we need to add these ratings to the weapon description details. This can be done within the "InfoMelee" procedure within the file "procedures.dat". Since the rulebook omits these ratings unless they are non-zero, we'll do the same within the description text. This yields code that should look similar to the following.		Again as we did for armor piercing, we need to add these ratings to the weapon description details. This can be done within the "InfoMelee" procedure within the file "procedures.dat". Since the rulebook omits these ratings unless they are non-zero, we'll do the same within the description text. It would be ideal if we can indicate to the user when these abilities don't apply for a weapon. We could accomplish that by highlighting the adjustments in red when the weapon does not satisfy the strength requirements. This yields code that should look similar to the following.

	<pre>		<pre>
Line 230:		Line 230:
	if (field[wpReach].value > 0) then		if (field[wpReach].value > 0) then
	iteminfo &= "Reach: " & field[wpReach].value & "{br}"		iteminfo &= "Reach: " & field[wpReach].value & "{br}"
			endif

			~if the weapon fails its strength requirement, change color and style
			if (empty(special) = 0) then
			if (tagis[Helper.BadStrReq] <> 0) then
			special = "{text a00000}{i}" & special & "{/i}{text 010101}"
			endif
	endif		endif
	</pre>		</pre>

	Our last task is to add these two ratings to the special notes shown for weapons on the Armory tab. This can be done via the Eval script within the "WeapMelee" component that performs this function. Since the logic is basically the same, we can use the code from adding the armor piercing as a template. The new lines of code should look like below.		Our last task is to add these two ratings to the special notes shown for weapons on the Armory tab. This can be done via the Eval script within the "WeapMelee" component that performs this function. Since the logic is basically the same, we can use the code from adding the armor piercing as a template. As we did above, we'll highlight the abilities if they aren't available due to insufficient Strength. The new lines of code should look like below.

	<pre>		<pre>
			~if the weapon fails its strength requirement, change color and style
			if (tagis[Helper.BadStrReq] <> 0) then
			iteminfo &= "{text a00000}{i}"
			endif

	~report the parry adjustment of the weapon (if any)		~report the parry adjustment of the weapon (if any)
	if (field[wpParry].value <> 0) then		if (field[wpParry].value <> 0) then
Line 251:		Line 263:
	special &= "Reach " & field[wpReach].value		special &= "Reach " & field[wpReach].value
	endif		endif

			~if the weapon fails its strength requirement, restore color and style
			if (tagis[Helper.BadStrReq] <> 0) then
			iteminfo &= "{/i}{text 010101}"
			endif
	</pre>		</pre>

Rob: /* Parry and Reach */

2009-02-10T03:14:30Z

Parry and Reach

← Older revision		Revision as of 03:14, 10 February 2009
Line 190:		Line 190:
	===Parry and Reach===		===Parry and Reach===

	There are two remaining aspects of hand weapons that differ from what's provided by the Skeleton files. The first is the parry adjustment, and the second is the weapon's reach. As with how we handled armor piercing, both of these aspects are numeric ratings, so we'll add new fields to track both of them. Since these aspects only apply to hand weapons, we'll add them to the "WeapMelee" component~~, which is in the file "equipment.str"~~. The new fields should look similar to the ones shown below.		There are two remaining aspects of hand weapons that differ from what's provided by the Skeleton files. The first is the parry adjustment, and the second is the weapon's reach. As with how we handled armor piercing, both of these aspects are numeric ratings, so we'll add new fields to track both of them. Since these aspects only apply to hand weapons, we'll add them to the "WeapMelee" component. The new fields should look similar to the ones shown below.

	<pre>		<pre>
Line 206:		Line 206:
	</pre>		</pre>

	With the tracking of the Parry adjustment, we need to apply that adjustment appropriately when the weapon is equipped. That entails defining a new Eval script for the component. All it needs to do is apply the proper adjustment to Parry, which ~~is achieved via~~ the script below.		With the tracking of the Parry adjustment, we need to apply that adjustment appropriately when the weapon is equipped. That entails defining a new Eval script for the component. All it needs to do is apply the proper adjustment to Parry prior to when the final Parry value is calculated. However, there is an important wrinkle. If the weapon die requirement is not satisfied, the Parry bonus is not applied. This means we also have to schedule our script after we downgrade the weapon die. Fortunately, there is a small window in which we can achieve this, resulting in the script below.

	<pre>		<pre>
	<eval index="4" phase="~~PreTraits~~" priority="5000">		<eval index="5" phase="Traits" priority="5000">
	<before name="~~Calc~~ trtFinal"/><![CDATA[		<before name="Derived trtFinal"/>
			<after name="Downgrade Weapon Die"/><![CDATA[
	if (field[grIsEquip].value <> 0) then		if (field[grIsEquip].value <> 0) then
	#~~traitbonus~~[trParry] += field[wpParry].value		if (tagis[Helper.BadStrReq] = 0) then
			perform #traitadjust[trParry,+,field[wpParry].value,"Equipped Weapon"]
			endif
	endif		endif
	~~]]></eval>~~
	</pre>		</pre>

Rob at 02:55, 10 February 2009

2009-02-10T02:55:57Z

Show changes

Rob: /* Dependencies on Strength */

2009-02-10T02:55:17Z

Dependencies on Strength

@@ Line 188: / Line 188: @@
 The handling of the weapon die is now in place. However, we'll need to remember to always use the "wpShowDmg" field for displaying weapon damage. The Skeleton files assume the "wpDamage" field is used, so we need to go through everywhere and change the reference where appropriate. The list is lengthy, so we won't go through each here. You can do a search for "wpDamage" within all the data files and replace it will "wpShowDmg" anywhere that it is being used for display or output of some sort. In general, the only exception would be the definitions of weapons themselves.
-===Dependencies on Strength===
+===Revised Strength Requirements===
 ===Parry and Reach===