Redesigning COMPANIONLIST and Companion Leveladjustment - Revision history

LegacyKing: /* Old Proposal */

2012-03-09T22:38:18Z

‎Old Proposal

LegacyKing: /* Intro to new Proposal */

2012-03-09T22:37:53Z

‎Intro to new Proposal

LegacyKing at 22:37, 9 March 2012

2012-03-09T22:37:07Z

LegacyKing at 22:28, 9 March 2012

2012-03-09T22:28:50Z

Maredudd at 20:18, 9 March 2012

2012-03-09T20:18:02Z

LegacyKing: /* Andrew's monkey wrench */

2012-03-09T19:10:08Z

‎Andrew's monkey wrench

LegacyKing: /* COMPANIONGROUP:x|y */

2012-03-09T18:59:28Z

‎COMPANIONGROUP:x|y

LegacyKing: /* COMPANIONGROUP:x|y */

2012-03-09T18:57:17Z

‎COMPANIONGROUP:x|y

LegacyKing: /* Tom's Proposal */

2012-03-09T18:15:55Z

‎Tom's Proposal

Maredudd: Edit made to reformat to the documentation standard format.

2012-03-09T17:23:36Z

Edit made to reformat to the documentation standard format.

@@ Line 9: / Line 9: @@
 == Old Proposal ==
-Proposal Rejected after looking at the various core books, they are to arbitary to take a standard formula approach, hence it'd be more work and effort for essentially no gain at this point.   [[User:LegacyKing|LegacyKing]] 09:28, 10 March 2012 (EST)
+Proposal Rejected after looking at the various core books, they are to arbitrary to take a standard formula approach, hence it'd be more work and effort for essentially no gain at this point.   [[User:LegacyKing|LegacyKing]] 09:28, 10 March 2012 (EST)
 == Proposal Intro ==

@@ Line 2: / Line 2: @@
 == Intro to new Proposal ==
-Using COMPANIONTYPE will allow creatures to alter the Effective Master Level based upon any method we need. Does not alter COMPANIONLIST or require conversion.
+Using COMPANIONTYPE will allow creatures to alter the Effective Master Level based upon any method we need. Does not alter COMPANIONLIST to be deprecated or require conversion. COMPANIONTYPE will be added to COMPANIONLIST.
 == Old Proposal ==

← Older revision		Revision as of 22:37, 9 March 2012
Line 1:		Line 1:
		+
		+	== Intro to new Proposal ==
		+
		+	Using COMPANIONTYPE will allow creatures to alter the Effective Master Level based upon any method we need. Does not alter COMPANIONLIST or require conversion.
		+
		+
		+
		+
		+
		+
		+	== Old Proposal ==
		+
	Proposal Rejected after looking at the various core books, they are to arbitary to take a standard formula approach, hence it'd be more work and effort for essentially no gain at this point. [[User:LegacyKing\|LegacyKing]] 09:28, 10 March 2012 (EST)		Proposal Rejected after looking at the various core books, they are to arbitary to take a standard formula approach, hence it'd be more work and effort for essentially no gain at this point. [[User:LegacyKing\|LegacyKing]] 09:28, 10 March 2012 (EST)

← Older revision		Revision as of 22:28, 9 March 2012
Line 1:		Line 1:
		+	Proposal Rejected after looking at the various core books, they are to arbitary to take a standard formula approach, hence it'd be more work and effort for essentially no gain at this point. [[User:LegacyKing\|LegacyKing]] 09:28, 10 March 2012 (EST)
		+
	== Proposal Intro ==		== Proposal Intro ==
	This is a redesign of How to Assign Companions to and Assign them to their groups and how to adjust individual creatures		This is a redesign of How to Assign Companions to and Assign them to their groups and how to adjust individual creatures

@@ Line 21: / Line 21: @@
 ::Variables Used (x): Text (Name of the COMPANIONGROUP)
 ::Variables Used (y): Text (Race Name)
-::Variables Used (y): COMPANIONTYPE=z
+::Variables Used (y): COMPANIONTYPE=Text
-::Variables Used (y): RACESUBTYPE=z
+::Variables Used (y): RACESUBTYPE=Text
-::Variables Used (y): RACETYPE=z
+::Variables Used (y): RACETYPE=Text
 :NOTES:
-::COMPANIONTYPE=z (Listed Companion Type would be available as part of the COMPANIONGROUP)
+::COMPANIONTYPE=Text (Listed Companion Type would be available as part of the COMPANIONGROUP)
-::RACETYPE=z      (Listed Race Type would be available as part of the COMPANIONGROUP)
+::RACETYPE=Text      (Listed Race Type would be available as part of the COMPANIONGROUP)
-::RACESUBTYPE=z   (Listed Race Sub Type would be available as part of the COMPANIONGROUP)
+::RACESUBTYPE=Text   (Listed Race Sub Type would be available as part of the COMPANIONGROUP)
 :Example:

@@ Line 66: / Line 66: @@
 By Andrew - Only one issue I see thus far, we currently use variables (and in some cases) multiple variables for the same 'Group'. We'd need to be able to specify WHAT is being affected by the -3 Effective Levels we are citing.
-::'''COMPANIONGROUP:'''Animal Companion <> '''BASECR:'''1 <> '''MASTERVAR=CompLevel:'''3
+::'''COMPANIONGROUP:'''Animal Companion <> '''BASECR:'''1 <> '''MASTERVAR:CompLevel|3'''
-::'''COMPANIONGROUP:'''Mystical Mount   <> '''BASECR:'''2 <> '''MASTERVAR=SMLvl:'''3
+::'''COMPANIONGROUP:'''Mystical Mount   <> '''BASECR:'''2 <> '''MASTERVAR:SMLvl|3'''
-''This is imperative as the CompanionMod list isn't set based upon a Class Level per se, but a variable that is based upon a class level, so other classes may bonus that variable. Animal Companions are using CompLevel, other critters use 'SMLevel' or 'FSLevel', so having a define file or gamemode section file to set the exact 'variable' used will be required, cause in some cases I do not want all the vars assigned to a type to be reduced, they may have another function.''
+''This is imperative as the CompanionMod list isn't set based upon a Class Level per se, but a variable that is based upon a class level, so other classes may bonus that variable. Animal Companions are using CompLevel, other critters use 'SMLevel' or 'FSLevel', so having a define file or gamemode section file to set the exact 'variable' used will be required, cause in some cases I do not want all the vars assigned to a type to be reduced, they may have another function. ''
 ''The second wrench, some games may not even use CR for their factor, it may be another value - so having a flexible system in place to handle exceptions might be something to consider. I only cited the RSRD rules as that's the structure we have in place. [[User:LegacyKing|LegacyKing]] 05:15, 10 March 2012 (EST)''
 == Back to Tom ==

@@ Line 19: / Line 19: @@
 === COMPANIONGROUP:x|y ===
-::Variables Used (x): Text (Group Type)
+::Variables Used (x): Text (Name of the COMPANIONGROUP)
 ::Variables Used (y): Text (Race Name)
 ::Variables Used (y): COMPANIONTYPE=z
@@ Line 33: / Line 33: @@
 :Example:
 ::'''COMPANIONGROUP:Animal Companion|Dog|Fox'''
-::''Would assign 'Dog' and 'Fox' to the 'Animal Companion' group''
+::''Would assign 'Dog' and 'Fox' Race to the 'Animal Companion' COMPANIONGROUP''
 ::'''COMPANIONGROUP:Mystical Mount|COMPANIONTYPE=Special Mount'''
-::''Would assign any race with the 'Special Mount' type to the 'Mystical Mount' group''
+::''Would assign any race with the COMPANIONTYPE of 'Special Mount' to the 'Mystical Mount' COMPANIONGROUP''
-That takes care of the replacement token for COMPANIONLIST. Next we need to redo how the Master Level is adjusted.
+That takes care of the replacement token for COMPANIONLIST. Next we need to redo how the Master Level is adjusted. Tom has made a proposal for that based upon CR.
 === Tom's Proposal ===

@@ Line 55: / Line 55: @@
 :(4) Gives us a check in the LST files that the items we are using in COMPANIONLIST are actually valid (and not misspelled) - since we have a master source from the Game Mode file.
-:Andrew's monkey wrench:
-Only one issue I see thus far, we currently use variables (and in some cases) multiple variables for the same 'Group'. We'd need to be able to specify WHAT is being affected by the -3 Effective Levels we are citing.
+=== Andrew's monkey wrench ===
 ::'''COMPANIONGROUP:'''Animal Companion <> '''BASECR:'''1 <> '''MASTERVAR=CompLevel:'''3
@@ Line 63: / Line 64: @@
 ''This is imperative as the CompanionMod list isn't set based upon a Class Level per se, but a variable that is based upon a class level, so other classes may bonus that variable. Animal Companions are using CompLevel, other critters use 'SMLevel' or 'FSLevel', so having a define file or gamemode section file to set the exact 'variable' used will be required, cause in some cases I do not want all the vars assigned to a type to be reduced, they may have another function.''
-The second wrench, some games may not even use CR for their factor, it may be another value - so having a flexible system in place to handle exceptions might be something to consider. I only cited the RSRD rules as that's the structure we have in place.
+''The second wrench, some games may not even use CR for their factor, it may be another value - so having a flexible system in place to handle exceptions might be something to consider. I only cited the RSRD rules as that's the structure we have in place. [[User:LegacyKing|LegacyKing]] 05:15, 10 March 2012 (EST)''
 (*Note: Open to having this more than Game Mode, as I know we are trying to get away from things solely in game mode.  So we can do Game Mode plus have an additional file for companionlist by itself, or Game Mode plus have an additional file that can load various types as we transfer things out of Game Mode - up for discussion).
@@ Line 75: / Line 78: @@
 ===== Follow up / Comments =====
-In eclipse I am allowed to purchases a Template (+2 ECL) for the express purposes of decreasing the CR for the Level Adjustment Factor by 1 or 2 (Depending on the GM, but let's say 1 for now).
+:Andrew's Reply: ''In eclipse I am allowed to purchases a Template (+2 ECL) for the express purposes of decreasing the CR for the Level Adjustment Factor by 1 or 2 (Depending on the GM, but let's say 1 for now).''
 :Tom's Reply: I was kinda expecting these types of exceptions.
 We can add '''COMPANIONECLBONUS:<integer>''' as a new Template token. (obviously name up for debate), which will add that number to the ECL before the calculation is done. ...or even '''COMPANIONCR:<integer>''' as a new Race/Template token that can be applied to certain races in order to modify the CR solely during the calculation done for '''COMPANIONGROUP'''. (again, name up for debate)
-''Tom - Any reason we wouldn't allow a JEP Var in place of the Integer? I know static values are easier on processing, but there might be a case where having a formula in a special case would be handy [[User:LegacyKing|LegacyKing]] 16:21, 9 March 2012 (EST)''
+Andrew's Reply: ''Tom - Any reason we wouldn't allow a JEP Var in place of the Integer? I know static values are easier on processing, but there might be a case where having a formula in a special case would be handy [[User:LegacyKing|LegacyKing]] 16:21, 9 March 2012 (EST)''