Tips and Tricks for Community Packs
1) Dealing with the Basic Pack inside of the other Packs
I just remembered I left something out of the pdf document. The ignore list for each "Pack" above will ignore any file from the Basic Pack. But to be able to have Pathfinder load the 3PP Pack it requires the Basic Pack.
So you should setup the Basic Pack repository into its own folder. Then do sync of the latest files. Then "Copy" the COM_ files from the Basic Pack folder over to the folder holding your 3PP Local Repository.
Its one extra step but really lets us reuse allot features in multiple Packs. In example when we start to do the Psionic Bestiary the GM Pack monster things that Frumple has created are going to be very useful. I have already moved his Disease helpers into the Basic Pack for this reason.
2) Source Page Number and Source Book Information for Classes/Archetypes.
So I see editors are correctly filling in "Source Page Number" but the "Source Book Information" field does not show in the editor. You have to manually fill in "srcBookInf" value using the "Fields" blue button at the top right for each class. Without this the page number info will not display on print outs.
3) Correctly Aligning scripts?
See
THIS post for details.
4) Why are Foreach loops bad and we shouldn't use them?
See
THIS post for full details.
5) If you are a regular editor please setup instant notifications for this thread.
To all "Editors" please setup yourself up to get "Instant Notifications" from this thread. So that any "announcements" I do you see. So how do you do that? Do a new post to this thread and scroll down to "
Notification Type:" section. And pick "
Instant Email notification".
6) Which "Things" should be source marked and which ones should not be?
A: You should be Source Marking anything that is visible to be selected by a gamer. So the Things that should not be source marked are "
Racial Specials" and "
Class Specials". "Abilities" are sometimes source marked and sometimes no. In example if you add a new "DR" ability that should NOT be source marked and it should be in placed in the Basic Pack even. If you add an Ability to support a specific feat or Thing then you can feel free to source mark it.
NOTE: ALL THINGS must be product ID marked to the "HL Community" please. No Exception to this rule!
7) When doing a Pre-Req for validation script for Feats how do I check for level?
A: At the minimum you should be using
#featlevelcount[] instead of
#levelcount[]. This allows classes that "Count As" the class to select these feats still. For some of the 3PP stuff like Ultimate Psionics you should be calling a procedure like so:
Code:
var classcheck as string
var levels as number
classcheck = "Cryptic"
call PUPreReqs
validif (levels >= 6)
8) How to delete or remove a Thing from a Pack?
A: We don't ever "delete" something from a Pack. If it went live at some point with this 'Thing ID' we need to deprecate it NOT delete it. Deleting can break the Pack or guaranteed to cause someones character to toss errors about a Missing Thing. Then I have get emails, PMs, Message Posts about the error. Meaning it causes me time to "support" this.
What we want to do is add the Thing ID to the
*HIDDEN tab and then move the XML into the file called "
- Deprecated Things.user". If a Pack does not have this yet then create it new.
9) How to use a Generic Class Ability script that works for 95% of all Class Abilities.
A: Please see
THIS post.