Pathfinder RPG Best Practices - Revision history

Aaron at 23:05, 23 February 2018

2018-02-23T23:05:03Z

← Older revision		Revision as of 23:05, 23 February 2018
Line 293:		Line 293:

	* Make sure all characters you create in all portfolios are set to "NPC" and "enemy of the party" on the configure hero form.		* Make sure all characters you create in all portfolios are set to "NPC" and "enemy of the party" on the configure hero form.

			* For any characters which are novel to this adventure path (that is, have full statblocks defined within the pages of the issue) go to the NPC tab and enter in a value for the "Id/SKU" and "Sourcebook Name". The "SKU" is usually in the format of "PZOXXXXX" where the Xs are an ID unique to the book in question. "PZO90123" for example is the 123rd issue of the Paizo Adventure Path line. The Sourcebook Name will be the adventure name, unless it is an adventure path issue, in which case it should follow the format of "Path Name: Chapter Name". Do not include chapter or issue numbers. A valid example would be "Ruins of Azlant: The Flooded Cathedral".

	* For any NPC in a portfolio (either imported from the encounter builder or created by yourself), check that the statblock output matches what's shown in the "Output Hero Statblock" window (found in the File menu). If anything there is wrong, try to figure out why - is it a mistake you made, or a mistake made by the authors of the encounter?		* For any NPC in a portfolio (either imported from the encounter builder or created by yourself), check that the statblock output matches what's shown in the "Output Hero Statblock" window (found in the File menu). If anything there is wrong, try to figure out why - is it a mistake you made, or a mistake made by the authors of the encounter?
Line 352:		Line 354:
	Chapter 1 - Burnt Offerings\Part 1 - Festival and Fire\p16 - Goblin Pyros (CR2).por		Chapter 1 - Burnt Offerings\Part 1 - Festival and Fire\p16 - Goblin Pyros (CR2).por
	Chapter 1 - Burnt Offerings\Part 1 - Festival and Fire\p17 - Die, Dog, Die!.por		Chapter 1 - Burnt Offerings\Part 1 - Festival and Fire\p17 - Die, Dog, Die!.por
	Chapter 1 - Burnt Offerings\Part 2 - Local Heroes\p19 - The Desecrated Vault (CR ½).por		Chapter 1 - Burnt Offerings\Part 2 - Local Heroes\p19 - The Desecrated Vault (CR 0.5).por
	Chapter 1 - Burnt Offerings\Part 3 - Glass and Wrath\p33 - B1 - Guard Cave (CR 2).por		Chapter 1 - Burnt Offerings\Part 3 - Glass and Wrath\p33 - B1 - Guard Cave (CR 2).por
	Chapter 1 - Burnt Offerings\Part 3 - Glass and Wrath\p34 - B4 - Washing Pool (CR 2).por		Chapter 1 - Burnt Offerings\Part 3 - Glass and Wrath\p34 - B4 - Washing Pool (CR 2).por
Line 375:		Line 377:

	== Step 3 - Check Appendices ==		== Step 3 - Check Appendices ==
	Most APs and some modules include a section on random encounters, which should be represented in Hero Lab in a specific way. Where the encounter describes a variable number of monsters encountered, the portfolio should ~~only~~ include a ~~single~~ representative ~~monster~~, with ~~a "#1"~~ appended to the name~~, and the portfolio name should not display the "average CR"~~. The number serves as a reminder that there are probably more than one in the encounter, and prompts the user to use the incrementer to select the true number in the encounter.		Most APs and some modules include a section on random encounters, which should be represented in Hero Lab in a specific way.

			In general, monster names should match that displayed in the table (usually lower case), and the "average CR" should not be included in the name of the portfolio (but see Special Encounters below).

			For random encounters are with a single monster, the name should just be the monsters race, with no numbers. For example, if the table entry is something like "23-27 - 1 manticore", then the name of the hero in the portfolio will be simply "Manticore".

			If the encounter is with 2 or more monsters, append numerals to each hero in the portfolio, to distinguish them. For example, if the table entry is "55-60 - 3 shadows" there will be 3 heroes in the portfolio "Shadow #1", "Shadow #2", and "Shadow #3".

			Where the random encounter describes a variable number of monsters encountered, the portfolio should include a representative number of monsters equal to the minimum roll of the dice, with numerals appended to the name as described above. The number serves as a reminder that there are probably more than one in the encounter, and prompts the user to use the incrementer to select the true number in the encounter when importing.

	If, on the other hand, the encounter is with a specific group of monsters and described in detail, you should append the CR to the portfolio name and add the encounter description to the Personal tab for the monsters.		If, on the other hand, the encounter is with a specific group of monsters and described in detail in the text, you should append the CR to the portfolio name and add the encounter description to the Personal tab for the monsters.

	Many issues also have Bestiaries in the appendix. Not all monsters defined there may have been used during the earlier parts of the adventure, so make sure there is a .stock file created that includes all such races. Test them as with any race (see above), comparing the statblocks between HL and the book.		Many issues also have Bestiaries in the appendix. Not all monsters defined there may have been used during the earlier parts of the adventure, so make sure there is a .stock file created that includes all such races. Test them as with any race (see above), comparing the statblocks between HL and the book.

Colen: /* Deliverable 1 - Create portfolios for every encounter and NPC in the module */

2017-06-07T14:45:45Z

Deliverable 1 - Create portfolios for every encounter and NPC in the module

Aaron: /* Deliverable 1 - Create portfolios for every encounter and NPC in the module */

2017-06-06T17:40:58Z

Deliverable 1 - Create portfolios for every encounter and NPC in the module

← Older revision		Revision as of 17:40, 6 June 2017
Line 285:		Line 285:

	* Some NPCs (e.g. Pavo Vos on page 18 of Fangwood Keep) will need a full Hero Lab character created for them. In those cases, create the character. Don't create statblocks for NPCs we don't have enough information about. For example, if the text mentions "Merlin (elf wizard 4) might be hanging around the sanctum", don't create an NPC for him - we can't, because we don't know anything useful about him to create the NPC with.		* Some NPCs (e.g. Pavo Vos on page 18 of Fangwood Keep) will need a full Hero Lab character created for them. In those cases, create the character. Don't create statblocks for NPCs we don't have enough information about. For example, if the text mentions "Merlin (elf wizard 4) might be hanging around the sanctum", don't create an NPC for him - we can't, because we don't know anything useful about him to create the NPC with.

			* Do not forget to include the sections in the Appendix! Adventure paths reproduce star characters in the appendix, and such characters should be restored to their "fresh" state. For example, an NPC who was discovered wounded during the course of the adventure, when represented in the appendix section, would be at full hit points. Another common part of the appendix is a random encounter table, but there may be other sections with their own statblocks which need representation as well.

	* When building an NPC, you'll need to reverse-engineer the Hero Lab character from the statblock. For example, the character's hit points will come from a combination of class levels, favored class bonuses, and other sources - use average hit points for the class levels (which on NPCs, alternate from one level to the next). Generally favored class bonuses will be used to add additional hit points, but not always.		* When building an NPC, you'll need to reverse-engineer the Hero Lab character from the statblock. For example, the character's hit points will come from a combination of class levels, favored class bonuses, and other sources - use average hit points for the class levels (which on NPCs, alternate from one level to the next). Generally favored class bonuses will be used to add additional hit points, but not always.

Aaron: /* Deliverable 1 - Create portfolios for every encounter and NPC in the module */

2017-06-06T17:24:14Z

Deliverable 1 - Create portfolios for every encounter and NPC in the module

← Older revision		Revision as of 17:24, 6 June 2017
Line 265:		Line 265:
	Please keep the following in mind when entering portfolios:		Please keep the following in mind when entering portfolios:

	* Portfolio names '''must''' be correct before we accept this deliverable - don't submit files with names like "encounter1.por" "encounter2.por" etc, as it makes things harder to QA.		* Portfolio names '''must''' be correct before we accept this deliverable - don't submit files with names like "encounter1.por" "encounter2.por" etc, as it makes things harder to QA.

			* Portfolio name format is important! For most encounters, the format is "PAGE - SECTION/MAP AREA - ENCOUNTER NAME (OTHER INFO, CR)". Note that not all general encounters will include all elements of the format.

			# PAGE is the abbreviation "pg" and the page number the encounter starts on, and includes a preceding 0 when necessary to bring things to 2 digits. For example, "pg 07" or "pg 82"
			# SECTION/MAP AREA is what identifies where in the module structure the encounter appears. It usually precedes the name. For example "Event 3" or "B3".
			# ENCOUNTER NAME is the name of the encounter, which should be in Title Case. For example, "Trader in the Dark" or "Khardajeen's Rest".
			# OTHER INFO is rarely used, most often to distinguish one version of an encounter from another. For example, "If idol is active" or "While alarm is raised".
			# CR is the challenge rating of the encounter, which is usually in the AP, but may be omitted for encounters which are non-combat. It should NOT include a preceding 0 when it is below 2 digits.

			* An exception to the above are encounters in a random encounter table. There, the format is "ROLL RANGE - ENCOUNTER NAME".

			# ROLL RANGE is the numbers which must be rolled in order to meet this encounter. It should include preceding 0 when below 2 digits. For example, "01-05", "08-12", "33-40".
			# ENCOUNTER NAME is the name of the encounter, whose case varies here. It should be in Sentence case for most of these encounters (for example "1d6 peuchen" or "1 griffon"), but special encounters (those given a writeup near the table) should be in Title Case (for example, "Scout Patrol" or "Mausoleum of Bacchus").

	* Don't create a portfolio unless there's at least a partial statblock present in the module. A partial statblock will typically show the basic stats of the monster, then refer you to a Bestiary - for those, you can import the monster from the encounter builder, and make any changes as required (for example, you might need to apply a template to it, or swap out weapons).		* Don't create a portfolio unless there's at least a partial statblock present in the module. A partial statblock will typically show the basic stats of the monster, then refer you to a Bestiary - for those, you can import the monster from the encounter builder, and make any changes as required (for example, you might need to apply a template to it, or swap out weapons).
Line 296:		Line 309:
	# If you can't get the skills to match up for an obvious reason, then don't worry about the problem. For example, a common issue is that NPCs have too much gear, so they're encumbered, so their skills in HL are lower than the portfolio says they should be - that's a case where we should leave them at the "correct" values and let the GM decide what to do. Another common issue is the creator might have forgotten that a skill is a class skill, leaving it 3 points off.		# If you can't get the skills to match up for an obvious reason, then don't worry about the problem. For example, a common issue is that NPCs have too much gear, so they're encumbered, so their skills in HL are lower than the portfolio says they should be - that's a case where we should leave them at the "correct" values and let the GM decide what to do. Another common issue is the creator might have forgotten that a skill is a class skill, leaving it 3 points off.

	* Make sure to enter text that's relevant during combat for the NPC (usually just the "Morale" or "During Combat" sections from the statblock, which should be entered on the NPC tab), but '''don't''' enter any "Character" or "Development" text that appears around the statblock. Text from those sections shouldn't be included in the Hero Lab portfolio (this is a change from what we've done in the past).		* Make sure to enter text that's relevant during combat for the NPC (usually just the "Before Combat", "Morale", and "During Combat" sections from the statblock, which should be entered on the NPC tab), but '''don't''' enter any "Character" or "Development" text that appears around the statblock. Text from those sections shouldn't be included in the Hero Lab portfolio (this is a change from what we've done in the past). Statblocks often include adjustments due to actions described in the "Before Combat" section, in which case you should go to the adjust tab and apply appropriate adjustments. If any of these preparations are from personally cast spells, go to the Spells tab and mark those off as cast.

	* On the Personal tab, include any portrait of the character from the book. If you can't extract those images from the PDF using a tool like Photoshop, let us know and we can supply them. If no portrait is provided in the book, just leave it as the default portrait from the Encounter Builder.		* On the Personal tab, include any portrait of the character from the book. If you can't extract those images from the PDF using a tool like Photoshop, let us know and we can supply them. If no portrait is provided in the book, just leave it as the default portrait from the Encounter Builder.

Aaron: /* Populate the NPC tab */

2017-06-06T16:37:44Z

Populate the NPC tab

← Older revision		Revision as of 16:37, 6 June 2017
Line 250:		Line 250:

	== Populate the NPC tab ==		== Populate the NPC tab ==
	* Make sure the sourcebook name and SKU is set properly for the character. This is the book that this specific NPC is printed in. For example, if the NPC was printed in "Goblins of Golarion" but uses a race from the Bestiary, enter the sourcebook as "Goblins of Golarion", not the Bestiary.		* Make sure the sourcebook name and SKU is set properly for the character. This is the book that this specific NPC is printed in. For example, if the NPC was printed in "Goblins of Golarion" but uses a race from the Bestiary, enter the sourcebook as "Goblins of Golarion", not the Bestiary. For multiple issue series, like adventure paths, the sourcebook name should include both the overarching series and the specific issue, for example "Ironfang Invasion: Siege of Stone"
	* Add any appropriate tactics, ecology, etc NPC information from the NPC's entry.		* Add any appropriate tactics, ecology, etc NPC information from the NPC's entry.

Aaron: /* Spell-Like Ability Name */

2017-06-06T16:30:45Z

Spell-Like Ability Name

← Older revision		Revision as of 16:30, 6 June 2017
Line 160:		Line 160:

	=== Spell-Like Ability Name ===		=== Spell-Like Ability Name ===
	Many spell like abilities have limitations or modifications in how they work, and these should be recorded in the ~~livename~~ field when bootstrapping~~, within parenthesis after the name~~. For example, many outsiders have the ability to use greater teleport as a SLA, but only on themselves and 50 lbs of gear, so this spell like ability would be bootstrapped with a ~~livename~~ of "~~Teleport, Greater (~~self plus 50 lbs. of objects only)"		Many spell like abilities have limitations or modifications in how they work, and these should be recorded in the sNameMod field when bootstrapping. For example, many outsiders have the ability to use greater teleport as a SLA, but only on themselves and 50 lbs of gear, so this spell like ability would be bootstrapped with a sNameMod of "self plus 50 lbs. of objects only"

	''Warning''		''Warning''

Colen: /* Deliverable 1 - Create portfolios for every encounter and NPC in the module */

2017-03-23T20:50:31Z

Deliverable 1 - Create portfolios for every encounter and NPC in the module

← Older revision		Revision as of 20:50, 23 March 2017
Line 297:		Line 297:

	* Make sure to enter text that's relevant during combat for the NPC (usually just the "Morale" or "During Combat" sections from the statblock, which should be entered on the NPC tab), but '''don't''' enter any "Character" or "Development" text that appears around the statblock. Text from those sections shouldn't be included in the Hero Lab portfolio (this is a change from what we've done in the past).		* Make sure to enter text that's relevant during combat for the NPC (usually just the "Morale" or "During Combat" sections from the statblock, which should be entered on the NPC tab), but '''don't''' enter any "Character" or "Development" text that appears around the statblock. Text from those sections shouldn't be included in the Hero Lab portfolio (this is a change from what we've done in the past).

			* On the Personal tab, include any portrait of the character from the book. If you can't extract those images from the PDF using a tool like Photoshop, let us know and we can supply them. If no portrait is provided in the book, just leave it as the default portrait from the Encounter Builder.

	== Deliverable 2 - Notes ==		== Deliverable 2 - Notes ==

Colen: /* Deliverable 1 - Create portfolios for every encounter and NPC in the module */

2017-02-22T17:23:51Z

Deliverable 1 - Create portfolios for every encounter and NPC in the module

← Older revision		Revision as of 17:23, 22 February 2017
Line 263:		Line 263:
	Every statblock, or partial statblock, printed in the module / adventure path / whatever must have a portfolio created in Hero Lab. The portfolio filenames are what appear in the Encounter Library, so they should be chosen based on the rules in "step 1" of the "testing encounter libraries" section below.		Every statblock, or partial statblock, printed in the module / adventure path / whatever must have a portfolio created in Hero Lab. The portfolio filenames are what appear in the Encounter Library, so they should be chosen based on the rules in "step 1" of the "testing encounter libraries" section below.

	~~Portfolio names '''must''' be correct before we accept this deliverable - don't submit files with names like "encounter1.por" "encounter2.por" etc, as it makes things harder to QA.~~		Please keep the following in mind when entering portfolios:

	~~Don~~'t ~~create a portfolio unless there's at least a partial statblock present in the module~~. ~~A partial statblock will typically show the basic stats of the monster~~, ~~then refer you to a Bestiary - for those, you can import the monster from the encounter builder, and make any changes~~ as ~~required (for example, you might need to apply a template~~ to ~~it, or swap out weapons)~~.		* Portfolio names '''must''' be correct before we accept this deliverable - don't submit files with names like "encounter1.por" "encounter2.por" etc, as it makes things harder to QA.

	~~If an encounter includes multiple copies~~ of ~~an NPC~~, import ~~that many copies into~~ the ~~portfolio. If you need to~~ make changes (~~like adding templates) it will probably be easier~~ to ~~make one,~~ apply ~~any changes~~, ~~then duplicate it from the Portfolio menu instead~~.		* Don't create a portfolio unless there's at least a partial statblock present in the module. A partial statblock will typically show the basic stats of the monster, then refer you to a Bestiary - for those, you can import the monster from the encounter builder, and make any changes as required (for example, you might need to apply a template to it, or swap out weapons).

	~~Some NPCs (e.g. Pavo Vos on page 18~~ of ~~Fangwood Keep) will need a full Hero Lab character created for them. In those cases~~, ~~create~~ the ~~character~~. ~~Don't create statblocks for NPCs we don't have enough information about. For example, if the text mentions "Merlin~~ (~~elf wizard 4~~) ~~might~~ be ~~hanging around the sanctum"~~, ~~don't create an NPC for him - we can't~~, ~~because we don't know anything useful about him to create~~ the ~~NPC with~~.		* If an encounter includes multiple copies of an NPC, import that many copies into the portfolio. If you need to make changes (like adding templates) it will probably be easier to make one, apply any changes, then duplicate it from the Portfolio menu instead.

	~~When building an NPC, you'll~~ need ~~to reverse-engineer the~~ Hero Lab character ~~from the statblock~~. ~~For example~~, the character'~~s hit points will come from a combination of class levels, favored class bonuses, and other sources - use average hit points~~ for ~~the class levels (which on~~ NPCs, ~~alternate from one level to~~ the ~~next~~)~~. Generally favored class bonuses will~~ be ~~used~~ to ~~add additional hit points, but not always~~.		* Some NPCs (e.g. Pavo Vos on page 18 of Fangwood Keep) will need a full Hero Lab character created for them. In those cases, create the character. Don't create statblocks for NPCs we don't have enough information about. For example, if the text mentions "Merlin (elf wizard 4) might be hanging around the sanctum", don't create an NPC for him - we can't, because we don't know anything useful about him to create the NPC with.

	~~Make sure all characters~~ you ~~create in all portfolios are set~~ to ~~"NPC"~~ and ~~"enemy of~~ the ~~party"~~ on the ~~configure hero form~~.		* When building an NPC, you'll need to reverse-engineer the Hero Lab character from the statblock. For example, the character's hit points will come from a combination of class levels, favored class bonuses, and other sources - use average hit points for the class levels (which on NPCs, alternate from one level to the next). Generally favored class bonuses will be used to add additional hit points, but not always.

	~~For any~~ NPC ~~in a portfolio (either imported from the encounter builder or created by yourself), check that the statblock output matches what's shown in~~ the "~~Output Hero Statblock" window (found in~~ the ~~File menu)~~. ~~If anything there is wrong, try to figure out why - is it a mistake you made, or a mistake made by the authors of the encounter?~~		* Make sure all characters you create in all portfolios are set to "NPC" and "enemy of the party" on the configure hero form.

	~~A convenient way to~~ check ~~whether~~ the statblock ~~is correct is to turn on~~ the "~~statblock summary info~~ window~~" for~~ the ~~portfolio~~ - you ~~can find it about 80% of the way down the "hero settings" in the configure hero form. Turn on "show full statblock summary window" and the first info window will be replaced~~ by the ~~character statblock. This allows you to check things without having to go to~~ the ~~File menu every time.~~		* For any NPC in a portfolio (either imported from the encounter builder or created by yourself), check that the statblock output matches what's shown in the "Output Hero Statblock" window (found in the File menu). If anything there is wrong, try to figure out why - is it a mistake you made, or a mistake made by the authors of the encounter?

	~~In general, set~~ "~~base values~~" ~~before~~ "~~derived values~~". ~~For example, set~~ the character~~'s ability scores first, then their skills - if~~ you ~~change ability scores after setting their skills,~~ the ~~skill values will change~~.		* A convenient way to check whether the statblock is correct is to turn on the "statblock summary info window" for the portfolio - you can find it about 80% of the way down the "hero settings" in the configure hero form. Turn on "show full statblock summary window" and the first info window will be replaced by the character statblock. This allows you to check things without having to go to the File menu every time.

	~~If you make any tweaks to~~ the character ~~after checking the statblock~~, ~~you need to re~~-~~check the statblock for any changes. Remember,~~ if you change an ability ~~score, that can affect~~ skills, ~~ability~~ values~~, etc~~.		* In general, set "base values" before "derived values". For example, set the character's ability scores first, then their skills - if you change ability scores after setting their skills, the skill values will change.

	~~Set the "buy for free" checkbox~~ to ~~buy~~ the character~~'s gear for free~~, ~~then set their "starting cash"~~ to be any ~~cash the portfolio indicates they have~~.		* If you make any tweaks to the character after checking the statblock, you need to re-check the statblock for any changes. Remember, if you change an ability score, that can affect skills, ability values, etc.

	~~Many NPCs will list~~ "~~longbow with 20 arrows~~" ~~for gear -~~ to ~~make that appear correctly on~~ the ~~statblock, add the longbow, add the arrows~~, then ~~put the arrows~~ "~~into~~" the ~~bow using the "gear" button (the little bag) on the arrows~~.		* Set the "buy for free" checkbox to buy the character's gear for free, then set their "starting cash" to be any cash the portfolio indicates they have.

	~~Remember~~ to ~~set important things like composite~~ longbow ~~strength bonuses~~, ~~holy symbol details~~, ~~etc~~.		* Many NPCs will list "longbow with 20 arrows" for gear - to make that appear correctly on the statblock, add the longbow, add the arrows, then put the arrows "into" the bow using the "gear" button (the little bag) on the arrows.

	~~If you find differences between Hero Lab's statblock and what's in the book~~, ~~try to do what the creators "meant"~~, ~~even if that means the character will have validation errors~~. ~~Examples:~~		* Remember to set important things like composite longbow strength bonuses, holy symbol details, etc.

	~~1) if~~ the ~~character has too many feats or skill points~~, ~~that's fine - just~~ do what the ~~module says. The GM~~ will ~~see any~~ errors ~~when they import the portfolio, and it's up to them what to do about them~~.		* If you find differences between Hero Lab's statblock and what's in the book, try to do what the creators "meant", even if that means the character will have validation errors. Examples:

	2) If you can't get the skills to match up for an obvious reason, then don't worry about the problem. For example, a common issue is that NPCs have too much gear, so they're encumbered, so their skills in HL are lower than the portfolio says they should be - that's a case where we should leave them at the "correct" values and let the GM decide what to do. Another common issue is the creator might have forgotten that a skill is a class skill, leaving it 3 points off.		# if the character has too many feats or skill points, that's fine - just do what the module says. The GM will see any errors when they import the portfolio, and it's up to them what to do about them.
			# If you can't get the skills to match up for an obvious reason, then don't worry about the problem. For example, a common issue is that NPCs have too much gear, so they're encumbered, so their skills in HL are lower than the portfolio says they should be - that's a case where we should leave them at the "correct" values and let the GM decide what to do. Another common issue is the creator might have forgotten that a skill is a class skill, leaving it 3 points off.

			* Make sure to enter text that's relevant during combat for the NPC (usually just the "Morale" or "During Combat" sections from the statblock, which should be entered on the NPC tab), but '''don't''' enter any "Character" or "Development" text that appears around the statblock. Text from those sections shouldn't be included in the Hero Lab portfolio (this is a change from what we've done in the past).

	== Deliverable 2 - Notes ==		== Deliverable 2 - Notes ==

Colen: /* General Issues */

2017-01-08T00:58:55Z

General Issues

← Older revision		Revision as of 00:58, 8 January 2017
Line 12:		Line 12:

	= General Issues =		= General Issues =
			== Only use official LWD content when creating data files or portfolios ==
			When building data files or entering portfolios, make sure you don't have any "third party" data files installed. Content in "third party" data files isn't available to everyone, and can cause problems with what you're entering. You can check to make sure you don't have any installed by going to Tools -> Manage Third Party Updates in Hero Lab.

			If you do have third party content installed, you should either delete it before working on stuff for us, or download a separate copy of the Pathfinder game system that you use to work on stuff for us. You can do this by downloading the latest Pathfinder update from the "Find Updates" screen, then changing the folder at the bottom-left of the screen to something like "pathfinder_lwd". Make sure you edit all portfolios only with the "pathfinder_lwd" version of Pathfinder, to avoid introducing or referencing third party content.


	== What content from an Adventure Path issue should be added? ==		== What content from an Adventure Path issue should be added? ==
	Add any content which could be used by a player during the course of the AP. This usually means all magic items in the Treasures section, or any feats/traits listed in the first issue of the AP. In most cases, the bestiary section does not need to be entered, unless one of the monsters within can be used as a familiar or animal companion to a PC. Another exception is that some Construct races may have information on the cost to buy them, and in that case the race and the minion object should both be created.		Add any content which could be used by a player during the course of the AP. This usually means all magic items in the Treasures section, or any feats/traits listed in the first issue of the AP. In most cases, the bestiary section does not need to be entered, unless one of the monsters within can be used as a familiar or animal companion to a PC. Another exception is that some Construct races may have information on the cost to buy them, and in that case the race and the minion object should both be created.

Colen: /* Details to check for Weapons, Armor, Magic Items, and Gear */

2016-12-13T15:12:26Z

Details to check for Weapons, Armor, Magic Items, and Gear

← Older revision		Revision as of 15:12, 13 December 2016
Line 231:		Line 231:
	*Step 6 If the item should be shown on the specials tab, go there and take a look at it's summary. If the summary is too long and gets cut off, try to condense it further so all pertinent info is shown (see [[#Constructing a Summary\|Constructing a Summary]]).		*Step 6 If the item should be shown on the specials tab, go there and take a look at it's summary. If the summary is too long and gets cut off, try to condense it further so all pertinent info is shown (see [[#Constructing a Summary\|Constructing a Summary]]).

	= Details to ~~check~~ for Weapons, Armor, Magic Items, and Gear =		= Details to Check for Weapons, Armor, Magic Items, and Gear =

	* If there is equipment in this book from an exotic source, like high-tech items, or stone-age items, or firearms, in the Configure Hero settings, go to the "Equipment, Weapons & Armor to show" section, and turn on the option(s) that should hide this exotic content. Then, search the various tables for content from this book, and make sure that it is hidden as intended. If not, set the appropriate tag in the "Special Groupings" list for the category.		* If there is equipment in this book from an exotic source, like high-tech items, or stone-age items, or firearms, in the Configure Hero settings, go to the "Equipment, Weapons & Armor to show" section, and turn on the option(s) that should hide this exotic content. Then, search the various tables for content from this book, and make sure that it is hidden as intended. If not, set the appropriate tag in the "Special Groupings" list for the category.
Line 240:		Line 240:

	* Go to the weapons, armor, magic, and gear tabs, and filter for "- no description -" (note the spaces between the - and the words). Make sure none of the content from your book is among this material - everything new should have a description.		* Go to the weapons, armor, magic, and gear tabs, and filter for "- no description -" (note the spaces between the - and the words). Make sure none of the content from your book is among this material - everything new should have a description.


	= Entering Stock Heroes =		= Entering Stock Heroes =

← Older revision		Revision as of 14:45, 7 June 2017
Line 269:		Line 269:
	* Portfolio name format is important! For most encounters, the format is "PAGE - SECTION/MAP AREA - ENCOUNTER NAME (OTHER INFO, CR)". Note that not all general encounters will include all elements of the format.		* Portfolio name format is important! For most encounters, the format is "PAGE - SECTION/MAP AREA - ENCOUNTER NAME (OTHER INFO, CR)". Note that not all general encounters will include all elements of the format.

	# PAGE is the abbreviation "pg" and the page number the encounter starts on, and includes a preceding 0 when necessary to bring things to 2 digits. For example, "~~pg 07~~" or "~~pg 82~~"		# PAGE is the abbreviation "p" and the page number the encounter starts on, and includes a preceding 0 when necessary to bring things to 2 digits. For example, "p07" or "p82".
	# SECTION/MAP AREA is what identifies where in the module structure the encounter appears. It usually precedes the name. For example "Event 3" or "B3".		# SECTION/MAP AREA is what identifies where in the module structure the encounter appears. It usually precedes the name. For example "Event 3" or "B3".
	# ENCOUNTER NAME is the name of the encounter, which should be in Title Case. For example, "Trader in the Dark" or "Khardajeen's Rest".		# ENCOUNTER NAME is the name of the encounter, which should be in Title Case. For example, "Trader in the Dark" or "Khardajeen's Rest".
	# OTHER INFO is rarely used, most often to distinguish one version of an encounter from another. For example, "If idol is active" or "While alarm is raised".		# OTHER INFO is rarely used, most often to distinguish one version of an encounter from another. For example, "If idol is active" or "While alarm is raised".
	# CR is the challenge rating of the encounter, which is usually in the AP, but may be omitted for encounters which are non-combat. It should NOT include a preceding 0 when it is below 2 digits.		# CR is the challenge rating of the encounter, which is usually in the AP, but may be omitted for encounters which are non-combat. It should NOT include a preceding 0 when it is below 2 digits. There should be a space between "CR" and the number.
			# For example: p30 - J23 - Strategy Room (CR 5).por

	* An exception to the above are encounters in a random encounter table. There, the format is "ROLL RANGE - ENCOUNTER NAME".		* An exception to the above are encounters in a random encounter table. There, the format is "ROLL RANGE - ENCOUNTER NAME".
Line 279:		Line 280:
	# ROLL RANGE is the numbers which must be rolled in order to meet this encounter. It should include preceding 0 when below 2 digits. For example, "01-05", "08-12", "33-40".		# ROLL RANGE is the numbers which must be rolled in order to meet this encounter. It should include preceding 0 when below 2 digits. For example, "01-05", "08-12", "33-40".
	# ENCOUNTER NAME is the name of the encounter, whose case varies here. It should be in Sentence case for most of these encounters (for example "1d6 peuchen" or "1 griffon"), but special encounters (those given a writeup near the table) should be in Title Case (for example, "Scout Patrol" or "Mausoleum of Bacchus").		# ENCOUNTER NAME is the name of the encounter, whose case varies here. It should be in Sentence case for most of these encounters (for example "1d6 peuchen" or "1 griffon"), but special encounters (those given a writeup near the table) should be in Title Case (for example, "Scout Patrol" or "Mausoleum of Bacchus").
			# For example: 95-97 - 2 deathwebs.por

	* Don't create a portfolio unless there's at least a partial statblock present in the module. A partial statblock will typically show the basic stats of the monster, then refer you to a Bestiary - for those, you can import the monster from the encounter builder, and make any changes as required (for example, you might need to apply a template to it, or swap out weapons).		* Don't create a portfolio unless there's at least a partial statblock present in the module. A partial statblock will typically show the basic stats of the monster, then refer you to a Bestiary - for those, you can import the monster from the encounter builder, and make any changes as required (for example, you might need to apply a template to it, or swap out weapons).