Pathfinder feat progression - Revision history

James: Remove post 5.16 stuff and link to it

2008-09-27T05:12:45Z

Remove post 5.16 stuff and link to it

2008-08-12T14:59:26Z

LEVELSPERFEAT, not FEATSPERLEVEL. D'Oh!

2008-08-12T12:10:01Z

5.16 proposal, and tabled post 5.16 spec on same page.

2008-08-09T20:35:10Z

2008-07-15T15:32:37Z

2008-07-15T15:24:18Z

2008-07-15T15:23:43Z

2008-07-15T15:19:44Z

2008-07-15T15:10:36Z

2008-07-15T15:08:42Z

@@ Line 1: / Line 1: @@
-This will be implemented under the following code FREQ:<br>
+This has been implemented under the following code FREQ:<br>
-[http://sourceforge.net/tracker/index.php?func=detail&aid=2044260&group_id=25576&atid=384722 2044260 Pathfinder bonus feat progression]
+[https://sourceforge.net/tracker/?func=detail&atid=384722&aid=2048071&group_id=25576 2048071 Pathfinder LEVELSPERFEAT expansion]
-This is a freq/proposal for the implementation of code to support the Pathfinder PRG.
+This is a freq/proposal for the implementation of code to support the Pathfinder RPG.
 Monsters and characters have different progressions for feats per level. While characters get a feat for each odd character level, feats for racial hit dice are still done as in D&D 3.5, i.e. one at 1 HD, and then one more for each 3 HD.
@@ Line 30: / Line 30: @@
 == Post 5.16 (tabled discussion ) ==
-The following discussion / proposal is currently tabled until after 5.16.  The clean up in GameMode does need to happen, but tearing out that code will delay 5.16.  Discussion should continue after 5.16, since this structure change will help ambiguity in the 6.0 code.
+See [[Pathfinder bonus feat progression]]

@@ Line 12: / Line 12: @@
 === LST Token change (Code) ===
-class line: FEATSPERLEVEL tag
+class line: LEVELSPERFEAT tag
-FEATSPERLEVEL:x|LEVELTYPE=y
+LEVELSPERFEAT:x|LEVELTYPE=y
 x = formula / number, # of feats per class level of given class.
@@ Line 23: / Line 23: @@
 === Data structure change ===
-.0 / 3.5e Monster classes will need |LEVELTYPE=Monster to all FEATSPERLEVEL tags.  This will fix a Bug in monsters with PC classes feats at wrong level bug.
+.0 / 3.5e Monster classes will need |LEVELTYPE=Monster to all LEVELSPERFEAT tags.  This will fix a Bug in monsters with PC classes feats at wrong level bug.
 Possibly a Scripted (PL) change.

← Older revision		Revision as of 12:10, 12 August 2008
Line 7:		Line 7:

	An example: Consider a 7th level fire giant barbarian. As a fire giant he has 15 racial hit dice. He gets feats at hit dice 1, 3, 6, 9, 12, and 15, just as in D&D 3.5. For his class levels, however, he gets feats at levels 1, 3, 5, and 7 (in D&D he would get two more, at hit dice 18 and 21).		An example: Consider a 7th level fire giant barbarian. As a fire giant he has 15 racial hit dice. He gets feats at hit dice 1, 3, 6, 9, 12, and 15, just as in D&D 3.5. For his class levels, however, he gets feats at levels 1, 3, 5, and 7 (in D&D he would get two more, at hit dice 18 and 21).
		+
		+	== 5.16 proposal ==
		+
		+	=== LST Token change (Code) ===
		+
		+	class line: FEATSPERLEVEL tag
		+
		+	FEATSPERLEVEL:x\|LEVELTYPE=y
		+
		+	x = formula / number, # of feats per class level of given class.
		+	y = text, name of group.
		+
		+	Fractional numbers will be stacked together within LEVELTYPE, but not between groups.
		+
		+	=== Data structure change ===
		+
		+	3.0 / 3.5e Monster classes will need \|LEVELTYPE=Monster to all FEATSPERLEVEL tags. This will fix a Bug in monsters with PC classes feats at wrong level bug.
		+
		+	Possibly a Scripted (PL) change.
		+
		+
		+	== Post 5.16 (tabled discussion ) ==
		+
		+	The following discussion / proposal is currently tabled until after 5.16. The clean up in GameMode does need to happen, but tearing out that code will delay 5.16. Discussion should continue after 5.16, since this structure change will help ambiguity in the 6.0 code.

	----		----

@@ Line 1: / Line 1: @@
 This is a freq/proposal for the implementation of code to support the Pathfinder PRG.
-Monsters and characters have different progressions for feats per level. While characters get a feat for each odd character level, feats for racial hit dice are stil done as in D&D 3.5, i.e. one at 1 HD, and then one more for each 3 HD.
+Monsters and characters have different progressions for feats per level. While characters get a feat for each odd character level, feats for racial hit dice are still done as in D&D 3.5, i.e. one at 1 HD, and then one more for each 3 HD.
 An example: Consider a 7th level fire giant barbarian. As a fire giant he has 15 racial hit dice. He gets feats at hit dice 1, 3, 6, 9, 12, and 15, just as in D&D 3.5. For his class levels, however, he gets feats at levels 1, 3, 5, and 7 (in D&D he would get two more, at hit dice 18 and 21).

@@ Line 40: / Line 40: @@
 Example usage:
-MONSTERCLASSTYPES:Monster
+<tt>MONSTERCLASSTYPES:Monster<br>
-{|
+CLASSGROUP:PC      CR:CL  <tab> BONUSFEATLEVELSTARTINTERVAL:3|3<br>
-|CLASSGROUP:PC || CR:CL || BONUSFEATLEVELSTARTINTERVAL:3|3
+CLASSGROUP:NPC     CR:max(CL-1,0) BONUSFEATLEVELSTARTINTERVAL:3|3<br>
-|-
+CLASSGROUP:Monster CR:0 BONUSFEATLEVELSTARTINTERVAL:3|3</tt>

← Older revision		Revision as of 15:24, 15 July 2008
Line 41:		Line 41:

	MONSTERCLASSTYPES:Monster		MONSTERCLASSTYPES:Monster
		+
	IMMUNETOXPPENALTYCLASSTYPES:Prestige,Monster		IMMUNETOXPPENALTYCLASSTYPES:Prestige,Monster

← Older revision		Revision as of 15:19, 15 July 2008
Line 35:		Line 35:

	[http://tech.groups.yahoo.com/group/pcgen_experimental/message/11022 See this post] for an in-depth explanation of the rational behind this proposal.		[http://tech.groups.yahoo.com/group/pcgen_experimental/message/11022 See this post] for an in-depth explanation of the rational behind this proposal.
		+
		+	----
		+
		+	Example usage:
		+
		+	MONSTERCLASSTYPES:Monster
		+	IMMUNETOXPPENALTYCLASSTYPES:Prestige,Monster
		+
		+	CLASSGROUP:PC CR:CL BONUSFEATLEVELSTARTINTERVAL:3\|3
		+	CLASSGROUP:NPC CR:max(CL-1,0) BONUSFEATLEVELSTARTINTERVAL:3\|3
		+	CLASSGROUP:Monster CR:0 BONUSFEATLEVELSTARTINTERVAL:3\|3

← Older revision		Revision as of 15:10, 15 July 2008
Line 34:		Line 34:
	The only problem will be if a class doesn't have a TYPE that is using a CLASSTYPE: line from Misc Info.		The only problem will be if a class doesn't have a TYPE that is using a CLASSTYPE: line from Misc Info.

−	~~See this post for an~~ [~~in-depth(~~http://tech.groups.yahoo.com/group/pcgen_experimental/message/11022)] explanation of the rational behind this proposal.	+	[http://tech.groups.yahoo.com/group/pcgen_experimental/message/11022 See this post] for an in-depth explanation of the rational behind this proposal.

← Older revision		Revision as of 15:08, 15 July 2008
Line 34:		Line 34:
	The only problem will be if a class doesn't have a TYPE that is using a CLASSTYPE: line from Misc Info.		The only problem will be if a class doesn't have a TYPE that is using a CLASSTYPE: line from Misc Info.

−	See this post for an [[in-depth(http://tech.groups.yahoo.com/group/pcgen_experimental/message/11022)]] explanation of the rational behind this proposal.	+	See this post for an [in-depth(http://tech.groups.yahoo.com/group/pcgen_experimental/message/11022)] explanation of the rational behind this proposal.