Race Racial Trait Swapping - Revision history

Tom Parker: /* Considerations */

2018-03-09T03:22:53Z

‎Considerations

Tom Parker: /* Array */

2018-03-09T03:22:08Z

‎Array

Tom Parker: /* Filler Object */

2018-03-09T03:19:25Z

‎Filler Object

Tom Parker: /* Filler Object */

2018-03-09T03:18:16Z

‎Filler Object

Tom Parker at 03:15, 9 March 2018

2018-03-09T03:15:56Z

LegacyKing: Created page with "Concern: Race is granted 'default' traits as a standard. Paizo has introduced two systems of concern: 1) "Race Package" where a race is granted specific non-default traits,..."

2018-03-08T22:55:18Z

Created page with "Concern: Race is granted 'default' traits as a standard. Paizo has introduced two systems of concern: 1) "Race Package" where a race is granted specific non-default traits,..."

New page

Concern:

Race is granted 'default' traits as a standard. Paizo has introduced two systems of concern:

1) "Race Package" where a race is granted specific non-default traits, and/or a choice between two or more additional choices

2) Racial Trait that is chosen by the player actually removes 2 or more existing default traits

@@ Line 90: / Line 90: @@
 ===Considerations===
-In this case, we need to look at what it would be like for a class to replace only one of the class features at that level.
+In this case, we need to look at what it would be like for a class to replace only one of the features.
 On our Trait we can do:

@@ Line 71: / Line 71: @@
 ==Array==
-One possible alternative would be to have an ARRAY[CLASSFEATURE] that contains all of the traits for a given level.
+One possible alternative would be to have an ARRAY[RACEFEATURE] that contains all of the traits for a given level.
-So on our class we had:
+In VARIABLE file:
 <pre>
-MODIFY:Level_3_Features|ADD|Default_L3_Feature_Lucky+Default_L3_Feature_Good
+LOCAL:RACE|ARRAY[RACEFEATURE]=Features
 </pre>
 On our Trait we can do:
 <pre>
-MODIFYOTHER:CLASS|Fighter|Level_3_Features|SET|SuperFeature|PRIORITY=400
+MODIFYOTHER:RACE|Elf|Features|SET|SuperFeature|PRIORITY=400
 </pre>
@@ Line 89: / Line 94: @@
 On our Trait we can do:
 <pre>
-MODIFYOTHER:CLASS|Fighter|Level_3_Features|SET|value()-Default_L3_Feature_Good+Default_L3_Feature_Better|PRIORITY=400
+MODIFYOTHER:RACE|Elf|Features|SET|value()-Default_Feature_Good+Default_Feature_Better|PRIORITY=400
 </pre>
 or alternatively:
 <pre>
-MODIFYOTHER:CLASS|Fighter|Level_3_Features|ADD|Default_L3_Feature_Better|PRIORITY=400
+MODIFYOTHER:RACE|Elf|Features|ADD|Default_Feature_Better|PRIORITY=400
-MODIFYOTHER:CLASS|Fighter|Level_3_Features|REMOVE|Default_L3_Feature_Good|PRIORITY=400
+MODIFYOTHER:RACE|Elf|Features|REMOVE|Default_Feature_Good|PRIORITY=400
 </pre>
@@ Line 101: / Line 106: @@
 # We have avoided adding an empty shell to the PC
 # We are making (risky?) assumptions of what we are replacing
-# We start to get into order of operations problems between Archetypes that both touch the same level, but different parts, so it increases the cross-data interaction
+# We start to get into order of operations problems between features that touch different features (think of this more broadly in terms of Archetypes that can impact different items at the same level both being usable together), so it increases the cross-data interaction
 In general, I think this is a bad idea due to the built-in assumptions.

← Older revision		Revision as of 03:19, 9 March 2018
Line 35:		Line 35:

	Let's assume we have a Racial Trait "Super" that replaces "Good" and "Lucky".		Let's assume we have a Racial Trait "Super" that replaces "Good" and "Lucky".
		+
		+	This presumes we have done:
		+	<pre>
		+	DYNAMICSCOPE:RACEFEATURE
		+	</pre>
		+
		+	In VARIABLE file:
		+	<pre>
		+	LOCAL:RACE\|RACEFEATURE=Feature_Lucky
		+	LOCAL:RACE\|RACEFEATURE=Feature_Good
		+	</pre>

	So on our race we had:		So on our race we had:

@@ Line 36: / Line 36: @@
 Let's assume we have a Racial Trait "Super" that replaces "Good" and "Lucky".
-So on our class we had:
+So on our race we had:
 <pre>
-MODIFY:Level_3_Feature_Lucky|SET|Default_L3_Feature_Lucky
+MODIFY:Feature_Lucky|SET|Default_Feature_Lucky
-MODIFY:Level_3_Feature_Good|SET|Default_L3_Feature_Good
+MODIFY:Feature_Good|SET|Default_Feature_Good
 </pre>
 On our Trait we can do:
 <pre>
-MODIFYOTHER:CLASS|Fighter|Level_3_Feature_Good|SET|SuperFeature|PRIORITY=400
+MODIFYOTHER:RACE|Elf|Feature_Good|SET|SuperFeature|PRIORITY=400
 </pre>
 Then we need to remove Default_L3_Feature_Lucky.  I would probably recommend something like:
 <pre>
-MODIFYOTHER:CLASS|Fighter|Level_3_Feature_Lucky|SET|EmptyFeature|PRIORITY=400
+MODIFYOTHER:RACE|Elf|Feature_Lucky|SET|EmptyFeature|PRIORITY=400
 </pre>
@@ Line 56: / Line 56: @@
 ===Justification===
-Keep in mind if we have a DYNAMIC of CLASSFEATURE (which Default_L3_Feature_Lucky is one implementation) then we need a default value for that object type.  So it's already likely that we have an "EmptyFeature" set up to be the default value for a variable of the CLASSFEATURE FORMAT.
+Keep in mind if we have a DYNAMIC of RACEFEATURE (which Default_Feature_Lucky is one implementation) then we need a default value for that object type.  So it's already likely that we have an "EmptyFeature" set up to be the default value for a variable of the RACEFEATURE FORMAT.
 ==Array==

@@ Line 1: / Line 1: @@
-Concern:
+{| align="right"
 Race is granted 'default' traits as a standard. Paizo has introduced two systems of concern:
-) "Race Package" where a race is granted specific non-default traits, and/or a choice between two or more additional choices
+Considerations:
-) Racial Trait that is chosen by the player actually removes 2 or more existing default traits
+In general, I think this is a bad idea due to the built-in assumptions.