PCGen Wiki - User contributions [en]

Further notes on CMP to RSRD

2012-03-01T18:44:01Z

FerretDave:

Miscellaneous comments on migrating CMP etc datasets to RSRD.

These comments are generic, and can easily apply to other game modes and other datasets, and are just what I've found to be useful, I'm offering them here to help those that wish to do similar, and in no way imply that you should be doing this.
Standard disclaimer - you break it yourself, you fix it yourself. However, there are lots of VERY helpful people on the Lst Help Forum, just ask questions in a generic manner to avoid closed content issues please.
These comments are just to try and help you avoid some of the pitfalls others have discovered.

First off, nearly all of these comments apply to the SRD just as easily as RSRD, take your preference, but stick to it, changing your mind half way through just confuses the issue.

Change the GAMEMODE in the appropriate PCC's from the CMP/Whatever, to 3e or 35e for SRD, RSRD respectively.

My own reasons for migrating to the RSRD gamemode, rather than using the CMP gamemode are based around being able to use new functionality, such as abilities instead of SAB, and reusing improved code for things like Turning/Rage etc, which then output to the printed character sheet in more definable ways.
CMP reinvented the wheel completely for their datasets, so they had to duplicate the effort in building their own version of the SRD, and while they added better descriptions, these sets are full of typo's and errors, whereas the PCGen SRD is maintained and corrected.
For example, my Forgotten Realms version(s) of the various Half Elves merely pretty much just mod the standard SRD Half Elf, and add the FR template - no need to rebuild all the features over again

Even if you do wish to keep the CMP gamemode, the guidance here should be of some help (I hope!)

I found that removing all SOURCESHORT:Blah and SOURCELONG:Blah (with various typo's of 'Blah'!) from data lines, and just have two such entries at the top of each file, makes editing the files easier. Obviously leave the SOURCEPAGE entries in place.

If there's a duplicate (or similar) 'thing' (Race/Class/Spell etc) in the RSRD, seriously consider altering your new entry to be a .COPY or .MOD of the RSRD 'thing'. You get the benefit of various data set fixes and improvements ([R]SRD datasets are actively maintained for PCGen, so take advantage of other people finding and fixing issues and typos) along with the improvements brought about by many things being moved to 'abilities' and other improvements.

Conversely, when you convert, if you're only doing one dataset at a time, chances are you'll get warnings that various things don't exist, as there's a lot of cross referencing.
You can either try and convert multiple sets at once (or at least, the RSRD/base set along with whatever you're currently working on *or* temporarily have the new pcc include the RSRD standard set, so you have everything defined during the conversion), OR just ignore the warnings for now, and later on (when you actually load the RSRD and the new set as a source in PCGen), then go through and fix anything that is still an issue.

A principle to follow - you may have several datasets, and numerous races/classes therein, but this is *your* homebrew, so the only bits you need to focus on are those that are actively used in your campaign.
Sure, run the whole lot through all the converters and get it to a stage where it loads, but then seriously consider commenting out anything that you don't actually use in your games.
Who cares if 90% of the Forgotten Realms races give errors on loading, if the 5 or 6 your characters need actually work fine.
Comment out the rest (add a '#' to the begining of the line in the .lst file) and then ignore it until you specifically need that race/class/equipment, and then fix just the one thing you need). Leave yourself more time for gaming :-)

For instance, (at least initially) you may not need any epic classes, any wondrous items, and perhaps not even any prestige classes. If you're only creating 'standard' PC's, then you may not even need the monster races either. If you're methodical about the process, you can get things that you need working quickly, and build up to the other bits later.

If you want things to appear in the GUI lists, so you have a reminder of it existing, but don't feel inclined to fix it immediately, then consider creating a copy of the lst entry (temporarily comment out the original entry), and remove any coding bits from the copy that are causing errors, and replace them with a SAB and/or DESC to indicate the gist of what you've removed, so you can still use it, and have some text available to indicate that it does roughly (working adding a 'TODO' note to the SAB/DESC as a reminder to fix it later).

For instance, rather than a feat with a massive PRExxx definition, and various calculations and vfeats with cross references(that may not work), change it to: 
FeatNameBlah DESC:doessomething SAB:has loads of PRExx and provides vfeat:blah 

Same principle for every LST.

I'll reiterate that point - as you cannot share any closed content homebrew (outside your own gaming group anyway), you only need to cater for a few people, so concentrate on making the bits your group actually *use* work, and only worry about the rest as and when you need it.

Errors for SA:.CLEAR can be fixed (manually) by noting that its often granting an SA(B) at one level, and then replacing it with a better SA(B) at another, so remove the .CLEAR entry completely, and suffix the initial SA(B) with |PRELEVEL:MAX=xx where xx is one less than the level that had the CLEAR (and gives the new replacement)
Perhaps use PRECLASSLEVEL and specify the current class...
And if needs be, add |PRELEVEL:MIN=zz if there are multiple variants of the SAB.
(In future, you can consider migrating these SAB's to ABILITIES, but that's a whole separate piece of work)

EQMODs - check out \data\d20ogl\srd35\basics\rsrd_equipmods_base.lst and rsrd_equipmods_enhancing.lst to verify what the current set is. Generally work on the basis that things like 'WEAP_PLUS_1' get changed to 'PLUS1W' (possibly 'PLUS1M' [for Martial?] now)

After all this conversion, when loading homebrew datasets, I highly recommend starting PCGen from a batch file, modified from the 'low mem' sample provided with any installation, with higher memory allocation (as much as you can spare) - not just for the extra memory but primarily to ensure you see any warnings/errors as sources are included when PCGen starts up(before you even load them).
I.e if there are PCC errors, you will see them in the batch files shell window, but by the time the GUI is up and you can see sources, those errors may be hidden.

More 'technical' detail on search/replace can be found here: [[Further Notes on CMP to RSRD Migration, part2]]

Further notes on CMP to RSRD

2012-03-01T18:37:59Z

FerretDave: Notes on CMP to RSRD conversion

Miscellaneous comments on migrating CMP etc datasets to RSRD.

These comments are generic, and can easily apply to other game modes and other datasets, and are just what I've found to be useful, I'm offering them here to help those that wish to do similar, and in no way imply that you should be doing this.
Standard disclaimer - you break it yourself, you fix it yourself. However, there are lots of VERY helpful people on the Lst Help Forum, just ask questions in a generic manner to avoid closed content issues please.
These comments are just to try and help you avoid some of the pitfalls others have discovered.

First off, nearly all of these comments apply to the SRD just as easily as RSRD, take your preference, but stick to it, changing your mind half way through just confuses the issue.

Change the GAMEMODE in the appropriate PCC's from the CMP/Whatever, to 3e or 35e for SRD, RSRD respectively.

I found that removing all SOURCESHORT:Blah and SOURCELONG:Blah (with various typo's of 'Blah'!) from data lines, and just have two such entries at the top of each file, makes editing the files easier. Obviously leave the SOURCEPAGE entries in place.

If there's a duplicate (or similar) 'thing' (Race/Class/Spell etc) in the RSRD, seriously consider altering your new entry to be a .COPY or .MOD of the RSRD 'thing'. You get the benefit of various data set fixes and improvements ([R]SRD datasets are actively maintained for PCGen, so take advantage of other people finding and fixing issues and typos) along with the improvements brought about by many things being moved to 'abilities' and other improvements.

Conversely, when you convert, if you're only doing one dataset at a time, chances are you'll get warnings that various things don't exist, as there's a lot of cross referencing.
You can either try and convert multiple sets at once (or at least, the RSRD/base set along with whatever you're currently working on *or* temporarily have the new pcc include the RSRD standard set, so you have everything defined during the conversion), OR just ignore the warnings for now, and later on (when you actually load the RSRD and the new set as a source in PCGen), then go through and fix anything that is still an issue.

A principle to follow - you may have several datasets, and numerous races/classes therein, but this is *your* homebrew, so the only bits you need to focus on are those that are actively used in your campaign.
Sure, run the whole lot through all the converters and get it to a stage where it loads, but then seriously consider commenting out anything that you don't actually use in your games.
Who cares if 90% of the Forgotten Realms races give errors on loading, if the 5 or 6 your characters need actually work fine.
Comment out the rest (add a '#' to the begining of the line in the .lst file) and then ignore it until you specifically need that race/class/equipment, and then fix just the one thing you need). Leave yourself more time for gaming :-)

For instance, (at least initially) you may not need any epic classes, any wondrous items, and perhaps not even any prestige classes. If you're only creating 'standard' PC's, then you may not even need the monster races either. If you're methodical about the process, you can get things that you need working quickly, and build up to the other bits later.

If you want things to appear in the GUI lists, so you have a reminder of it existing, but don't feel inclined to fix it immediately, then consider creating a copy of the lst entry (temporarily comment out the original entry), and remove any coding bits from the copy that are causing errors, and replace them with a SAB and/or DESC to indicate the gist of what you've removed, so you can still use it, and have some text available to indicate that it does roughly (working adding a 'TODO' note to the SAB/DESC as a reminder to fix it later).

I'll reiterate that point - as you cannot share any closed content homebrew (outside your own gaming group anyway), you only need to cater for a few people, so concentrate on making the bits your group actually *use* work, and only worry about the rest as and when you need it.

Errors for SA:.CLEAR can be fixed (manually) by noting that its often granting an SA(B) at one level, and then replacing it with a better SA(B) at another, so remove the .CLEAR entry completely, and suffix the initial SA(B) with |PRELEVEL:MAX=xx where xx is one less than the level that had the CLEAR (and gives the new replacement)
Perhaps use PRECLASSLEVEL and specify the current class...
And if needs be, add |PRELEVEL:MIN=zz if there are multiple variants of the SAB.
(In future, you can consider migrating these SAB's to ABILITIES, but that's a whole separate piece of work)

EQMODs - check out \data\d20ogl\srd35\basics\rsrd_equipmods_base.lst and rsrd_equipmods_enhancing.lst to verify what the current set is. Generally work on the basis that things like 'WEAP_PLUS_1' get changed to 'PLUS1W' (possibly 'PLUS1M' [for Martial?] now)

After all this conversion, when loading homebrew datasets, I highly recommend starting PCGen from a batch file, modified from the 'low mem' sample provided with any installation, with higher memory allocation (as much as you can spare) - not just for the extra memory but primarily to ensure you see any warnings/errors as sources are included when PCGen starts up(before you even load them).
I.e if there are PCC errors, you will see them in the batch files shell window, but by the time the GUI is up and you can see sources, those errors may be hidden.

More 'technical' detail on search/replace can be found here: [[Further Notes on CMP to RSRD Migration, part2]]

Conversion 514 516

2012-03-01T18:27:16Z

FerretDave:

Info from Drew (stolen directly from his post on the lst help forum [http://games.groups.yahoo.com/group/pcgen/message/107662|here]

Updating the CMP sets*shouldn't* be all that hard, *if* done in a methodical
manner and using thetools available.

If the sets you have are working fantastic in 5.14, then you should be able to use the converter program available in 5.16 to bring those sets forward with minimal fuss - that was the purpose of the converter - to assist homebrews and older sets to stay current.

From my own experience in keeping sets up to date the issues the converter isn't able to handle is improper syntax that 5.14 was silently dropping. With 5.16 we have greater error catching than before. The error catching improves even more as we progress into 6.0.

Here is what I recommend - You run the PCGen Converter. It will have a LOG of issues it couldn't handle - look at those and fix them.

Load up 5.16, Open you preferences - Find the Input - there should be a check box to select 'Show Detailed Error Report' or something along those lines. There is also the option to turn of deprecated warnings - I'd recommend unselecting that so you can fix the true errors first, then we'll worry about updating the syntax.

Next - Load only your core set (PHB) (I prefer to use the bat file to load pcgen which has a dos console box open, but you can simply open the console in pcgen under tools IIRC).

Note the Error Messages - If in the dox box select all the text and then hit 'ENTER' - that will save all those errors (I usually open my text editor and place those in their own file - errors.lst.

Deprecated/Deprecation Messages should be safe to ignore for now - In fact if you followed the
above, you shouldn't be seeing them.

Unconstructed References - These are Abilities, Feats, Templates which are being asked for that the program cannot find. It will tell you what Category 'Feat' 'Special Ability' etc, and the name of the offending file. It should also give you the originating file for the call. Though that may be later in 5.17 we got that ability. In most cases you either have a typo (Misspelled name, or someone isn't using the KEY name if it's set). Fix those by either correcting the typo, or in the case it's actually missing, create one.

Error Messages are the big issues - You've got syntax usage in a wrong file, or improper usage of syntax. It will usually tell you the file, and the offending syntax, in some cases you'll have one issue generate 2 to 3 warnings, since once one part of the syntax is bad, the rest is also bad.
These need to be fixed for a smooth operation.

NPEs - NullPointerErrors - Those are the SERIOUS that severely broke something - DO NOT CONTINUE TO USE PCGEN if you see one of these errors - any issue you find is NULL & VOID as the program is already broken and unstable. These need to be addressed immediately. Fix it, restart PCGen and try again.
Common causes of these guys - Spaces where spaces do not belong; stray symbols in odd places, or really bad syntax. In all cases, you should seek help on the lst help forum as any of the code monkeys and experienced Data Monkeys can usually discern what the cause is and direct you how to fix it.

Other weird error messages - You either have a Code Issue, or your syntax is funky. Report it here.
Unlike those nasty NPEs, these guys mean you broke something, but the rest of the program should be okay to use (i.e. your broken issue is isolated from the rest of the program).

Like I said before, most of your error messages won't be the fault of the converter, it was bad syntax that was never discovered till the program was taught to announce it. It may seem like a mountain, but be methodical - Trust me, most of your errors can be caught at load up without opening any character. I'd say give yourself a couple of hours and most if not all your issues can be fixed.

Conversion 514 516

2012-03-01T18:26:37Z

FerretDave:

Info from Drew (stolen directly from his post on the lst help forum [http://games.groups.yahoo.com/group/pcgen/message/107662]|here)

Updating the CMP sets*shouldn't* be all that hard, *if* done in a methodical
manner and using thetools available.

If the sets you have are working fantastic in 5.14, then you should be able to use the converter program available in 5.16 to bring those sets forward with minimal fuss - that was the purpose of the converter - to assist homebrews and older sets to stay current.

From my own experience in keeping sets up to date the issues the converter isn't able to handle is improper syntax that 5.14 was silently dropping. With 5.16 we have greater error catching than before. The error catching improves even more as we progress into 6.0.

Here is what I recommend - You run the PCGen Converter. It will have a LOG of issues it couldn't handle - look at those and fix them.

Load up 5.16, Open you preferences - Find the Input - there should be a check box to select 'Show Detailed Error Report' or something along those lines. There is also the option to turn of deprecated warnings - I'd recommend unselecting that so you can fix the true errors first, then we'll worry about updating the syntax.

Next - Load only your core set (PHB) (I prefer to use the bat file to load pcgen which has a dos console box open, but you can simply open the console in pcgen under tools IIRC).

Note the Error Messages - If in the dox box select all the text and then hit 'ENTER' - that will save all those errors (I usually open my text editor and place those in their own file - errors.lst.

Deprecated/Deprecation Messages should be safe to ignore for now - In fact if you followed the
above, you shouldn't be seeing them.

Unconstructed References - These are Abilities, Feats, Templates which are being asked for that the program cannot find. It will tell you what Category 'Feat' 'Special Ability' etc, and the name of the offending file. It should also give you the originating file for the call. Though that may be later in 5.17 we got that ability. In most cases you either have a typo (Misspelled name, or someone isn't using the KEY name if it's set). Fix those by either correcting the typo, or in the case it's actually missing, create one.

Error Messages are the big issues - You've got syntax usage in a wrong file, or improper usage of syntax. It will usually tell you the file, and the offending syntax, in some cases you'll have one issue generate 2 to 3 warnings, since once one part of the syntax is bad, the rest is also bad.
These need to be fixed for a smooth operation.

NPEs - NullPointerErrors - Those are the SERIOUS that severely broke something - DO NOT CONTINUE TO USE PCGEN if you see one of these errors - any issue you find is NULL & VOID as the program is already broken and unstable. These need to be addressed immediately. Fix it, restart PCGen and try again.
Common causes of these guys - Spaces where spaces do not belong; stray symbols in odd places, or really bad syntax. In all cases, you should seek help on the lst help forum as any of the code monkeys and experienced Data Monkeys can usually discern what the cause is and direct you how to fix it.

Other weird error messages - You either have a Code Issue, or your syntax is funky. Report it here.
Unlike those nasty NPEs, these guys mean you broke something, but the rest of the program should be okay to use (i.e. your broken issue is isolated from the rest of the program).

Like I said before, most of your error messages won't be the fault of the converter, it was bad syntax that was never discovered till the program was taught to announce it. It may seem like a mountain, but be methodical - Trust me, most of your errors can be caught at load up without opening any character. I'd say give yourself a couple of hours and most if not all your issues can be fixed.

Conversion 514 516

2012-03-01T18:19:58Z

FerretDave: Drews LST conversion suggestions

Info from Drew (stolen directly from his post)

Updating the CMP sets*shouldn't* be all that hard, *if* done in a methodical
manner and using thetools available.

If the sets you have are working fantastic in 5.14, then you should be able to use the converter program available in 5.16 to bring those sets forward with minimal fuss - that was the purpose of the converter - to assist homebrews and older sets to stay current.

From my own experience in keeping sets up to date the issues the converter isn't able to handle is improper syntax that 5.14 was silently dropping. With 5.16 we have greater error catching than before. The error catching improves even more as we progress into 6.0.

Here is what I recommend - You run the PCGen Converter. It will have a LOG of issues it couldn't handle - look at those and fix them.

Load up 5.16, Open you preferences - Find the Input - there should be a check box to select 'Show Detailed Error Report' or something along those lines. There is also the option to turn of deprecated warnings - I'd recommend unselecting that so you can fix the true errors first, then we'll worry about updating the syntax.

Next - Load only your core set (PHB) (I prefer to use the bat file to load pcgen which has a dos console box open, but you can simply open the console in pcgen under tools IIRC).

Note the Error Messages - If in the dox box select all the text and then hit 'ENTER' - that will save all those errors (I usually open my text editor and place those in their own file - errors.lst.

Deprecated/Deprecation Messages should be safe to ignore for now - In fact if you followed the
above, you shouldn't be seeing them.

Unconstructed References - These are Abilities, Feats, Templates which are being asked for that the program cannot find. It will tell you what Category 'Feat' 'Special Ability' etc, and the name of the offending file. It should also give you the originating file for the call. Though that may be later in 5.17 we got that ability. In most cases you either have a typo (Misspelled name, or someone isn't using the KEY name if it's set). Fix those by either correcting the typo, or in the case it's actually missing, create one.

Error Messages are the big issues - You've got syntax usage in a wrong file, or improper usage of syntax. It will usually tell you the file, and the offending syntax, in some cases you'll have one issue generate 2 to 3 warnings, since once one part of the syntax is bad, the rest is also bad.
These need to be fixed for a smooth operation.

NPEs - NullPointerErrors - Those are the SERIOUS that severely broke something - DO NOT CONTINUE TO USE PCGEN if you see one of these errors - any issue you find is NULL & VOID as the program is already broken and unstable. These need to be addressed immediately. Fix it, restart PCGen and try again.
Common causes of these guys - Spaces where spaces do not belong; stray symbols in odd places, or really bad syntax. In all cases, you should seek help on the lst help forum as any of the code monkeys and experienced Data Monkeys can usually discern what the cause is and direct you how to fix it.

Other weird error messages - You either have a Code Issue, or your syntax is funky. Report it here.
Unlike those nasty NPEs, these guys mean you broke something, but the rest of the program should be okay to use (i.e. your broken issue is isolated from the rest of the program).

Like I said before, most of your error messages won't be the fault of the converter, it was bad syntax that was never discovered till the program was taught to announce it. It may seem like a mountain, but be methodical - Trust me, most of your errors can be caught at load up without opening any character. I'd say give yourself a couple of hours and most if not all your issues can be fixed.

Updating Homebrew Sets

2012-03-01T18:13:55Z

FerretDave: /* 5.14.x-->5.16.x */

{| align="right"
| __TOC__
|}

=Introduction=
This section is for updating older homebrew LST files to use the current standards. This is a work in progress. Any questions ask on the PCGen Yahoo Group.

==PrettyLST==

* First off we'll need [http://sourceforge.net/projects/pcgen/files/PrettyLst/v%201.39%20build%208180/prettylst_1-39_build-8180.zip/download PrettyLST] for earlier versions of PCGen

* Next, to run PrettyLST you'll need [https://www.activestate.com/activeperl/downloads/ ActivePerl].

* You will want to run PrettyLST with the Conversion Flag turned on to bring your sets up to 5.12 standards. Note this is not a perfect conversion, you will need to check your materials against any errors PrettyLST outputs.

It's a good idea to be methodical over this, and convert a single set at a time, otherwise the number of errors and warnings you'll have to get through may well become overwhelming.
Keep track of what you have converted.

you'll want to run PrettyLst with a command line such as:

perl prettylst.pl -i=d:\pcgen_convert\input -o=d:\pcgen_convert\intermediate -gamemode=35e -systempath D:\utils\PCGen\PCGen5120\system -e=error.txt -convert pcgen512 -nojep

That '-convert pcgen512' is the flag to actually perform the conversion (otherwise its just reformatting the field order and indentation).

-i specifies the directory your old data set is in currently (note that here I've setup specific directories completely outside of my 'normal' dataset directory, so I don't risk messing up any 'live' sets.

-o indicates the output directory (I use an 'intermediate' directory, which will be used as the input for the next script (Baraks) below).

-gamemode=35e specifies the gamemode we're converting, you can leave this off, and prettylst will determine what you need, though I find migrating CMP datasets to 35e means I can make use of many other PCGen enhancements and get a better experience.

-systempath is a path to the installed PCGen 5.12.0, I'm not totally sure this is needed actually, but it cant hurt :-)

-e defines where the error output is going to be written.

-nojep prevents (what appears to be erroneous) warnings about some functions.

I suggest you put the above into a batch file (RunConvert1.bat) to make it easier to run under windows.

Run the batch file, read the error messages, make any updates to the sources in the *input* directory, and re-run the batch file, repeat until either A) you have no more errors, or B) (more likely) you get fed up trying to fix them :-)
There are numerous warnings you can (probably) ignore (further options to prettylst reduce warning levels), and many that are just plain difficult to resolve at this stage - further steps below may fix them, or it may be cross references into other sources that you havent converted yet...

NOTE - if you do migrate CMP to RSRD (I personally recommend this, opinions may differ) many things (races, classes, spells, equipment...) are easier if they .MOD an appropriate (standard PCGen) 3.5 (or 3e!) dataset.

[[Further notes on CMP to RSRD]]

==5.12.x-->5.14.x==

For 5.12 to 5.14 you'll want to use [http://tech.groups.yahoo.com/group/PCGenListFileHelp/files/Misc/5.12%20to%205.14%20Conversion_v085.zip Barak's Script]

Again you'll need perl, see above. You may also need to jon the PCGenLiSTFileHelp group to access the file. I put the script with PrettyLST.

Following the methodology above to get datasets up to 5.12.0, with a dataset in d:\pcgen_convert\intermediate, run Baraks script as:

perl convert_514.pl -I=d:\pcgen_convert\intermediate -O=d:\pcgen_convert\output

Check the 'convert_514_log.txt' file for errors, edit the files in the 'intermediate'* directory to fix, and re-run Baraks script again.

*(or edit in the original 'input' directory, and run both the PrettyLst conversion and then Baraks script again - this ensures that you only edit one set of files and don't risk overwriting your edited intermediate files)

==5.14.x-->5.16.x==

5.16.x and beyond has a Converter included with PCGen. That Version of PCGen will update any files from the previous version. So the 5.16.x converter will bring 5.14.x files forward to 5.16.x standards.

Use the 5.16 Converter to bring 5.14 sets forward.

NOTE: The Converter will bring the previous cycle forward, do not use 6.0 to bring 5.14 forward, use 5.16 to do that.

When you finally load the sources into PCGen - Note that the error reporting improves with each version, so while you may see more errors with the newer version, chances are that those errors were there all along, just not being made obvious.
Initially, you most likely want to turn off preference options for 'deprecation' and 'show detailed error report' and fix anything else you see at load time (particularly any NPE errors - they are serious and you need to restart PCGen!)

Once those (serious) errors are fixed, then at your leisure turn those options back on and fix the remaining (less serious) issues manually.

See [[Conversion 514_516|here]] for more information.

==5.16.x-->6.0.x==
Use the 6.0 PCGen Converter

==Massive Changes that WILL affect Homebrew Users==
=Starting 5.16.4 and 5.17.4=
All the Armor BONUS TYPES got a bit of a Change. This WILL affect any homebrew sets that use any PCGen released core sets.

The Following needs to be done to follow the standards:

* Races that grant Natural Armor need to use this format:
BONUS:COMBAT|AC|x|TYPE=NaturalArmor
this replaces the old format of BONUS:COMBAT|AC|x|TYPE=NaturalArmor.REPLACE

* Anything that improves Natural Armor not by enhancement needs to use this format:
BONUS:COMBAT|AC|x|TYPE=NaturalArmor.STACK
this replaces the old format of BONUS:COMBAT|AC|x|TYPE=NaturalArmor.REPLACE
BONUS:COMBAT|AC|x|TYPE=NaturalArmorEnhancement
should be used for any Natural Armor Enhancement

The same applies for Armor.REPLACE and Shield.REPLACE; these both become Armor and Shield respectively. If there is an enhancement you wish to and, just append 'Enhancement' to the Bonus type 'ArmorEnhancement', 'ShieldEnhancement'.

* For Armor and Shield:
BONUS:COMBAT|AC|x|TYPE=ArmorEnhancement
This replaces '''BONUS:COMBAT|AC|x|TYPE=Armor.REPLACE'''

BONUS:COMBAT|AC|x|TYPE:ShieldEnhancement
This replaces '''BONUS:COMBAT|AC|x|TYPE=Shield.REPLACE'''

* 3rd Edition has a slight variation. We don't use 'Shield' or 'ShieldEnhancement' instead we use:
ArmorShield
For Armor Bonus derived from the Shield
ArmorShieldEnhancement
For the Armor Bonus granted from the Shield Enhancement

This was done to make the stacking rules work more uniformly, and avoid overlap stacking where it shouldn't occur.

Updating Homebrew Sets

2012-02-29T13:47:26Z

FerretDave: Updating homebrew sets

{| align="right"
| __TOC__
|}

=Introduction=
This section is for updating older homebrew LST files to use the current standards. This is a work in progress. Any questions ask on the PCGen Yahoo Group.

==PrettyLST==

* First off we'll need [http://sourceforge.net/projects/pcgen/files/PrettyLst/v%201.39%20build%208180/prettylst_1-39_build-8180.zip/download PrettyLST] for earlier versions of PCGen

* Next, to run PrettyLST you'll need [https://www.activestate.com/activeperl/downloads/ ActivePerl].

* You will want to run PrettyLST with the Conversion Flag turned on to bring your sets up to 5.12 standards. Note this is not a perfect conversion, you will need to check your materials against any errors PrettyLST outputs.

It's a good idea to be methodical over this, and convert a single set at a time, otherwise the number of errors and warnings you'll have to get through may well become overwhelming.
Keep track of what you have converted.

you'll want to run PrettyLst with a command line such as:

perl prettylst.pl -i=d:\pcgen_convert\input -o=d:\pcgen_convert\intermediate -gamemode=35e -systempath D:\utils\PCGen\PCGen5120\system -e=error.txt -convert pcgen512 -nojep

That '-convert pcgen512' is the flag to actually perform the conversion (otherwise its just reformatting the field order and indentation).

-i specifies the directory your old data set is in currently (note that here I've setup specific directories completely outside of my 'normal' dataset directory, so I don't risk messing up any 'live' sets.

-o indicates the output directory (I use an 'intermediate' directory, which will be used as the input for the next script (Baraks) below).

-gamemode=35e specifies the gamemode we're converting, you can leave this off, and prettylst will determine what you need, though I find migrating CMP datasets to 35e means I can make use of many other PCGen enhancements and get a better experience.

-systempath is a path to the installed PCGen 5.12.0, I'm not totally sure this is needed actually, but it cant hurt :-)

-e defines where the error output is going to be written.

-nojep prevents (what appears to be erroneous) warnings about some functions.

I suggest you put the above into a batch file (RunConvert1.bat) to make it easier to run under windows.

Run the batch file, read the error messages, make any updates to the sources in the *input* directory, and re-run the batch file, repeat until either A) you have no more errors, or B) (more likely) you get fed up trying to fix them :-)
There are numerous warnings you can (probably) ignore (further options to prettylst reduce warning levels), and many that are just plain difficult to resolve at this stage - further steps below may fix them, or it may be cross references into other sources that you havent converted yet...

NOTE - if you do migrate CMP to RSRD (I personally recommend this, opinions may differ) many things (races, classes, spells, equipment...) are easier if they .MOD an appropriate (standard PCGen) 3.5 (or 3e!) dataset.

[[Further notes on CMP to RSRD]]

==5.12.x-->5.14.x==

For 5.12 to 5.14 you'll want to use [http://tech.groups.yahoo.com/group/PCGenListFileHelp/files/Misc/5.12%20to%205.14%20Conversion_v085.zip Barak's Script]

Again you'll need perl, see above. You may also need to jon the PCGenLiSTFileHelp group to access the file. I put the script with PrettyLST.

Following the methodology above to get datasets up to 5.12.0, with a dataset in d:\pcgen_convert\intermediate, run Baraks script as:

perl convert_514.pl -I=d:\pcgen_convert\intermediate -O=d:\pcgen_convert\output

Check the 'convert_514_log.txt' file for errors, edit the files in the 'intermediate'* directory to fix, and re-run Baraks script again.

*(or edit in the original 'input' directory, and run both the PrettyLst conversion and then Baraks script again - this ensures that you only edit one set of files and don't risk overwriting your edited intermediate files)

==5.14.x-->5.16.x==

5.16.x and beyond has a Converter included with PCGen. That Version of PCGen will update any files from the previous version. So the 5.16.x converter will bring 5.14.x files forward to 5.16.x standards.

Use the 5.16 Converter to bring 5.14 sets forward.

NOTE: The Converter will bring the previous cycle forward, do not use 6.0 to bring 5.14 forward, use 5.16 to do that.

==5.16.x-->6.0.x==
Use the 6.0 PCGen Converter

==Massive Changes that WILL affect Homebrew Users==
=Starting 5.16.4 and 5.17.4=
All the Armor BONUS TYPES got a bit of a Change. This WILL affect any homebrew sets that use any PCGen released core sets.

The Following needs to be done to follow the standards:

* Races that grant Natural Armor need to use this format:
BONUS:COMBAT|AC|x|TYPE=NaturalArmor
this replaces the old format of BONUS:COMBAT|AC|x|TYPE=NaturalArmor.REPLACE

* Anything that improves Natural Armor not by enhancement needs to use this format:
BONUS:COMBAT|AC|x|TYPE=NaturalArmor.STACK
this replaces the old format of BONUS:COMBAT|AC|x|TYPE=NaturalArmor.REPLACE
BONUS:COMBAT|AC|x|TYPE=NaturalArmorEnhancement
should be used for any Natural Armor Enhancement

The same applies for Armor.REPLACE and Shield.REPLACE; these both become Armor and Shield respectively. If there is an enhancement you wish to and, just append 'Enhancement' to the Bonus type 'ArmorEnhancement', 'ShieldEnhancement'.

* For Armor and Shield:
BONUS:COMBAT|AC|x|TYPE=ArmorEnhancement
This replaces '''BONUS:COMBAT|AC|x|TYPE=Armor.REPLACE'''

BONUS:COMBAT|AC|x|TYPE:ShieldEnhancement
This replaces '''BONUS:COMBAT|AC|x|TYPE=Shield.REPLACE'''

* 3rd Edition has a slight variation. We don't use 'Shield' or 'ShieldEnhancement' instead we use:
ArmorShield
For Armor Bonus derived from the Shield
ArmorShieldEnhancement
For the Armor Bonus granted from the Shield Enhancement

This was done to make the stacking rules work more uniformly, and avoid overlap stacking where it shouldn't occur.

Further Notes on CMP to RSRD Migration, part2

2012-02-28T00:41:33Z

FerretDave:

Apologies for the formatting, this probably needs tidying up...This really is just a cut and paste from a scratch file I used whilst converting data
Some of this (most?) is possibly done by PrettyLst (I wasnt using the right options initially!)
Much of it was just notes I'd made as I manually updated some files, and possibly prettylst now does a healthy chunk of the below.

Several of these commands are search and replace regex expressions for VIM (my editor of choice), the concept should be clear though as to the intent (on every line, search for 'foo' and replace with 'bar'), and updating to your editor of choice.
I copy the line from the scratch file, and in vim, press ':' to enter command mode, and then just paste and hit return.

------------------------------------------
replace % with %% in descriptions

Willpower - replace with 'Will'

ADD: can't be used more than once per class line, so split it into two lines. I.e

<nowiki>1<tab>ADD:feat1<tab>ADD:feat2
becomes
1<tab>ADD:feat1
1<tab>ADD:feat2</nowiki>

Cannot have commas in names, just remove them/replace with a space.

------------------------------------------

**Above are confirmed as necessary following proper prettylst conversion, below still need to be validated.**

=====================================
spells file
changed all to .mod other than specific few (20 odd non-srd spells)
note - we only really want the descriptions, not the mechanics..
=====================================
feats file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
ExtraTurning - CHOOSE: nochoice Typo???!!! Type=ExtraTurnig.STACK ??? - updated to match pcgen srd original
CHOOSE:Exotic :- CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Exotic
CHOOSE:Blah|1 := CHOOSE:Blah
PRELEVEL:x := PRELEVEL:MIN=x
PREVARLT:CL=Shaaryan Hunter,6 := PRECLASSLEVELMAX:1,Shaaryan Hunter=5
PREVARGTEQ:CL=Shaaryan Hunter,6 := PRECLASS:1,Shaaryan Hunter=6

AUTO.SHIELDPROF|TYPE := AUTO.SHIELDPROF|SHIELDTYPE
CHOOSE:Martial := CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Martial
CHOOSE:SKILLSNAMED|blah|1 :- CHOOSE:SKILLSNAMED|blah

---------------------------------------------
feats_hidden file
ADD:FEAT(blah)|x :- ADD:FEAT|x|blah
SPELL:Blah|x|Innate := SPELLS:Innate|TIMES=x|Blah
SPELLS:Innate|CASTERLEVEL=max(classlevel("Mage"),1)|Blah
CHOOSE:NUMCHOICES=x| := CHOOSE:x|
**********************************************************************************
TODO Favoured Enemy / Favoured Bonus - all disabled, seems style is quite different
**********************************************************************************
Rogue Bonus -
CHOOSE:SKILLS|3+INT := SELECT:3+INT CHOOSE:SKILLS
=====================================

skills file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
PREMOVE:Blah := PREMOVE:1,Blah
CHOOSE:Language(Spoken) :- CHOOSE:LANGUAGE|Spoken

SA: := SAB:
AUTO.ARMORPROF|TYPE := AUTO.ARMORPROF|ARMORTYPE

=====================================
updates to dieties file
Tag Name: PREALIGN:x,x
Variables Used (x):LG,LN,LE,NG,TN,NE,CG,CN,CE,Deity (Alignment abbreviation).
Variables Used (x):0,1,2,3,4,5,6,7,8,10 (Alignment array number).
LG,LN,LE,NG,TN,NE,CG,CN,CE, Deity
0, 1, 2, 3, 4, 5, 6, 7, 8, 10

%s/ [ ]*FOLLOWERALIGN:147/|PREALIGN:LN,TN,CN /
%s/ [ ]*FOLLOWERALIGN:13457/|PREALIGN:LN,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:258/|PREALIGN:LE,NE,CE /
%s/ [ ]*FOLLOWERALIGN:012/|PREALIGN:LG,LN,LE /
%s/ [ ]*FOLLOWERALIGN:125/|PREALIGN:LN,LE,NE /
%s/ [ ]*FOLLOWERALIGN:036/|PREALIGN:LG,NG,CG /
%s/ [ ]*FOLLOWERALIGN:013/|PREALIGN:LG,LN,NG /
%s/ [ ]*FOLLOWERALIGN:578 /|PREALIGN:NE,CN,CE /
%s/ [ ]*FOLLOWERALIGN:678 /|PREALIGN:CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:367 /|PREALIGN:NG,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345678 /|PREALIGN:LG,LN,LE,NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:013467 /|PREALIGN:LG,LN,NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345 /|PREALIGN:LG,LN,LE,NG,TN,NE /
%s/ [ ]*FOLLOWERALIGN:3467 /|PREALIGN:NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:345678 /|PREALIGN:NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:0123457 /|PREALIGN:LG,LN,LE,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:01236 /|PREALIGN:LG,LN,LE,NG,CG /
%s/ [ ]*FOLLOWERALIGN:2458 /|PREALIGN:LE,TN,NE,CE /
%s/ [ ]*FOLLOWERALIGN:0346 /|PREALIGN:LG,NG,TN,CG /
%s/ [ ]*FOLLOWERALIGN:4678 /|PREALIGN:TN,CG,CN,CE /

PREVARxx| becomes PREVARxx:Var,Value
--------------
%s/|PREDEFAULTMONSTER:Y//g
%s/MFEAT/FEAT/g

# note - need BOTH of the following, first one splits, second one cleans
%s/HITDICE:[0-9]*,/HD:,&HITDICE:\tHITDIE:/
%s/,HITDICE://g
or just remove it completely... %s/HITDICE:[0-9]*,[0-9]*//g
>>>No Longer using HITDICE, please remove and just use MONSTERCLASS
=====================================
SPELL: becomes SPELLS:Innate|TIMES=x|CASTERLEVEL=x|SpellName1,DC|SpellName2,DC

=====================================
Typically replace 'Heavy blah' with 'blah (Heavy)' etc.
=====================================
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_enhancing.lst
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_base.lst

%s/Willpower/Will/g
%s/ARMR_MWORK/MWORKA/g
%s/ARMR_PLUS_2/PLUS2A/g
%s/ARMR_STEEL/STEEL/g
%s/ARMR_PLUS_3/PLUS3W/g
%s/ARMR_PLUS_1/PLUS1W/g
%s/SHLD_MWORK/MWORKS/g
%s/SHLD_STEEL/STEEL/g
%s/SHLD_WOOD/WOOD/g
%s/SHLD_PLUS_1/PLUS1S/g
%s/SHLD_PLUS_2/PLUS2S/g
%s/WEAP_PLUS_1/PLUS1W/g
%s/WEAP_PLUS_2/PLUS2W/g
%s/WEAP_PLUS_3/PLUS3W/g
%s/WEAP_PLUS_4/PLUS4W/g
%s/WEAP_PLUS_5/PLUS5W/g
%s/WEAP_STEEL/STEEL/g

%s/WEAP_MWORK/MWORKW/g
=====================================

Shields get changed from Small/Large to Light/Heavy and Wooden/Steel to Wood/Metal

=====================================
FRCS/ue_feats.lst - Ice Troll Berserker should modify the rage special ability for natural armor...

=====================================
if you use linux, or have 'cygwin' installed under windows, you can run a bash script to do some extra conversions - note that some of this may be unnecessary as PrettyLst may fix it)

<<--start of file

<nowiki>#</nowiki>!/bin/bash 
<nowiki>#</nowiki> SLong and SShort are what we *want* to have finally. 
<nowiki>#</nowiki> ALong, AShort and BShort are variations of this (common typos!) that appear initially 
<nowiki>#</nowiki> that we want to replace 

<nowiki>#</nowiki> 
<nowiki>#</nowiki> save to above commented out as version history once done 
SLong="Players Guide to Faerun" 
SShort="pgtfae" 
ALong="Players Guide to Faerun" 
ALong="players guide to faerun" 
AShort="pgtfae" 
BShort="PGTFAE" 

Files=$( ls *.lst) 

echo This script indicates the file name, and the first SOURCE entry noted therein as stdout, to allow verification of correct Sed replacement values 

for File in ${Files} 
do 

echo ${File} 
grep SOURCE ${File} |head -3 |uniq 
printf "SOURCELONG:${SLong}\nSOURCESHORT:${SShort}\n" >a 
printf "#Converted by SedScript $(date +%d/%m/%y)\n\n" >>a 

<nowiki>#</nowiki> want to replace characters 93 & 94 (special quotes) 
<nowiki>#</nowiki> but cant get sed to recognise them... 
<nowiki>#</nowiki> these appear as black squares in vim.. 
<nowiki>#</nowiki> have to do manually in vim.. 
<nowiki>#</nowiki> 

egrep -v "^SOURCE|^# CVS|#Converted by" $File |\ 
sed -e 's/Willpower/Will/g' \ 
-e 's/ARMR_MWORK/MWORKA/g' \ 
-e 's/AMMO_MWORK/MWORKA/g' \ 
-e 's/ARMRMW/MWORKA/g' \ 
-e 's/ARMR_PLUS_1/PLUS1A/g' \ 
-e 's/ARMR_PLUS_2/PLUS2A/g' \ 
-e 's/ARMR_PLUS_3/PLUS3A/g' \ 
-e 's/ARMR_PLUS_4/PLUS4A/g' \ 
-e 's/ARMR_PLUS_5/PLUS5A/g' \ 
-e 's/SHLD_MWORK/MWORKA/g' \ 
-e 's/SHLD_STEEL/STEEL/g' \ 
-e 's/SHLD_DARKWOOD/DARK/g' \ 
-e 's/ARMOR_SPIKE_BASH/SPOKE_SB/g' \ 
-e 's/ARMOR_SPIKE/SPIKE_S/g' \ 
-e 's/ARMR_STEEL/STEEL/g' \ 
-e 's/SHLD_WOOD/WOOD/g' \ 
-e 's/SHLD_PLUS_1/PLUS1S/g' \ 
-e 's/SHLD_PLUS_2/PLUS2S/g' \ 
-e 's/SHLD_PLUS_3/PLUS3S/g' \ 
-e 's/SHLD_PLUS_4/PLUS4S/g' \ 
-e 's/SHLD_PLUS_5/PLUS5S/g' \ 
-e 's/WEAP_PLUS_1/PLUS1W/g' \ 
-e 's/WEAP_PLUS_2/PLUS2W/g' \ 
-e 's/WEAP_PLUS_3/PLUS3W/g' \ 
-e 's/WEAP_PLUS_4/PLUS4W/g' \ 
-e 's/WEAP_PLUS_5/PLUS5W/g' \ 
-e 's/AMMO_PLUS_1/PLUS1W/g' \ 
-e 's/AMMO_PLUS_2/PLUS2W/g' \ 
-e 's/AMMO_PLUS_3/PLUS3W/g' \ 
-e 's/AMMO_PLUS_4/PLUS4W/g' \ 
-e 's/AMMO_PLUS_5/PLUS5W/g' \ 
-e 's/WEAP_BANE/BANE_M/g' \ 
-e 's/WEAP_STEEL/STEEL/g' \ 
-e 's/WEAP_VORPAL/VORPAL/g' \ 
-e 's/WEAP_ALCH_SILVR/ALCHM/g' \ 
-e 's/WEAP_ALCH_SLVR/ALCHM/g' \ 
-e 's/WEAP_AXIOMATIC/LAW_M/g' \ 
-e 's/WEAP_HOLY/HOLY_M/g' \ 
-e 's/ARMR_DRAGONHIDE/DRACO/g' \ 
-e 's/AMMO_ALCH_SLVR/ALCHM/g' \ 
-e 's/AMMO_COLD_IRON/C_IRON/g' \ 
-e 's/.WEAP_WOOD//g' \ 
-e 's/AMMO_ALCH_SILVR/ALCHM/g' \ 
-e 's/MWWEAPON/MWORKW/g' \ 
-e 's/WEAPMW/MWORKW/g' \ 
-e 's/WEAP_MWORK/MWORKW/g' \ 
-e 's/|PREDEFAULTMONSTER:Y//g' \ 
-e 's/MFEAT/FEAT/g' \ 
-e 's/HITDICE:[0-9]*,[0-9]*//g' \ 
-e"s/[|]SOURCELONG:${SLong}//" \ 
-e"s/[|]SOURCESHORT:${SShort}//" \ 
-e"s/[|]SOURCESHORT:${AShort}//" \ 
-e"s/[|]SOURCESHORT:${BShort}//" \ 
-e's/|SOURCEPAGE/SOURCEPAGE/' \ 
-e's/[|]SOURCELONG:${ALong}//' \ 
-e's/SOURCEPAGE/ SOURCEPAGE/' \ 
-e's/|SOURCE/\tSOURCE/' >>a 
<nowiki>#</nowiki> that's a 'tab' two lines up, check when copying 
mv a ${File} 
done 
<<--end of file-->>

Copy that to a file (remove the <<-- -->> lines) and then execute it

=====================================
other manual changes:

WEAPONPROF:blah to :
BONUS:WEAPONPROF:blah
AUTO:WEAPONPROF|Longsword|Rapier|

BONUS:ToHIT|blah to BONUS:COMBAT:TOHIT|blah

ADD:FEAT|(blah) ADD:FEAT|(blah) to ADD:FEAT|2|blah,blah

Note that LANGBONUS (and potentially others?) take pipe (|) separators in one file but comma separators in others.

Further note that there are various typo's, particularly in 'DEFINE' variables.

Further Notes on CMP to RSRD Migration, part2

2012-02-28T00:12:18Z

FerretDave: /* = */

Apologies for the formatting, this probably needs tidying up...This really is just a cut and paste from a scratch file I used whilst converting data
Some of this (most?) is possibly done by PrettyLst (I wasnt using the right options initially!)
Much of it was just notes I'd made as I manually updated some files, and possibly prettylst now does a healthy chunk of the below.

Several of these commands are search and replace regex expressions for VIM (my editor of choice), the concept should be clear though as to the intent (on every line, search for 'foo' and replace with 'bar'), and updating to your editor of choice.
I copy the line from the scratch file, and in vim, press ':' to enter command mode, and then just paste and hit return.

------------------------------------------
replace % with %% in descriptions

Willpower - replace with 'Will'

ADD: can't be used more than once per class line, so split it into two lines. I.e

<nowiki>1<tab>ADD:feat1<tab>ADD:feat2
becomes
1<tab>ADD:feat1
1<tab>ADD:feat2</nowiki>

Cannot have commas in names, just remove them/replace with a space.

------------------------------------------

**Above are confirmed as necessary following proper prettylst conversion, below still need to be validated.**

=====================================
spells file
changed all to .mod other than specific few (20 odd non-srd spells)
note - we only really want the descriptions, not the mechanics..
=====================================
feats file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
ExtraTurning - CHOOSE: nochoice Typo???!!! Type=ExtraTurnig.STACK ??? - updated to match pcgen srd original
CHOOSE:Exotic :- CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Exotic
CHOOSE:Blah|1 := CHOOSE:Blah
PRELEVEL:x := PRELEVEL:MIN=x
PREVARLT:CL=Shaaryan Hunter,6 := PRECLASSLEVELMAX:1,Shaaryan Hunter=5
PREVARGTEQ:CL=Shaaryan Hunter,6 := PRECLASS:1,Shaaryan Hunter=6

AUTO.SHIELDPROF|TYPE := AUTO.SHIELDPROF|SHIELDTYPE
CHOOSE:Martial := CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Martial
CHOOSE:SKILLSNAMED|blah|1 :- CHOOSE:SKILLSNAMED|blah

---------------------------------------------
feats_hidden file
ADD:FEAT(blah)|x :- ADD:FEAT|x|blah
SPELL:Blah|x|Innate := SPELLS:Innate|TIMES=x|Blah
SPELLS:Innate|CASTERLEVEL=max(classlevel("Mage"),1)|Blah
CHOOSE:NUMCHOICES=x| := CHOOSE:x|
**********************************************************************************
TODO Favoured Enemy / Favoured Bonus - all disabled, seems style is quite different
**********************************************************************************
Rogue Bonus -
CHOOSE:SKILLS|3+INT := SELECT:3+INT CHOOSE:SKILLS
=====================================

skills file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
PREMOVE:Blah := PREMOVE:1,Blah
CHOOSE:Language(Spoken) :- CHOOSE:LANGUAGE|Spoken

SA: := SAB:
AUTO.ARMORPROF|TYPE := AUTO.ARMORPROF|ARMORTYPE

=====================================
updates to dieties file
Tag Name: PREALIGN:x,x
Variables Used (x):LG,LN,LE,NG,TN,NE,CG,CN,CE,Deity (Alignment abbreviation).
Variables Used (x):0,1,2,3,4,5,6,7,8,10 (Alignment array number).
LG,LN,LE,NG,TN,NE,CG,CN,CE, Deity
0, 1, 2, 3, 4, 5, 6, 7, 8, 10

%s/ [ ]*FOLLOWERALIGN:147/|PREALIGN:LN,TN,CN /
%s/ [ ]*FOLLOWERALIGN:13457/|PREALIGN:LN,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:258/|PREALIGN:LE,NE,CE /
%s/ [ ]*FOLLOWERALIGN:012/|PREALIGN:LG,LN,LE /
%s/ [ ]*FOLLOWERALIGN:125/|PREALIGN:LN,LE,NE /
%s/ [ ]*FOLLOWERALIGN:036/|PREALIGN:LG,NG,CG /
%s/ [ ]*FOLLOWERALIGN:013/|PREALIGN:LG,LN,NG /
%s/ [ ]*FOLLOWERALIGN:578 /|PREALIGN:NE,CN,CE /
%s/ [ ]*FOLLOWERALIGN:678 /|PREALIGN:CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:367 /|PREALIGN:NG,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345678 /|PREALIGN:LG,LN,LE,NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:013467 /|PREALIGN:LG,LN,NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345 /|PREALIGN:LG,LN,LE,NG,TN,NE /
%s/ [ ]*FOLLOWERALIGN:3467 /|PREALIGN:NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:345678 /|PREALIGN:NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:0123457 /|PREALIGN:LG,LN,LE,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:01236 /|PREALIGN:LG,LN,LE,NG,CG /
%s/ [ ]*FOLLOWERALIGN:2458 /|PREALIGN:LE,TN,NE,CE /
%s/ [ ]*FOLLOWERALIGN:0346 /|PREALIGN:LG,NG,TN,CG /
%s/ [ ]*FOLLOWERALIGN:4678 /|PREALIGN:TN,CG,CN,CE /

PREVARxx| becomes PREVARxx:Var,Value
--------------
%s/|PREDEFAULTMONSTER:Y//g
%s/MFEAT/FEAT/g

# note - need BOTH of the following, first one splits, second one cleans
%s/HITDICE:[0-9]*,/HD:,&HITDICE:\tHITDIE:/
%s/,HITDICE://g
or just remove it completely... %s/HITDICE:[0-9]*,[0-9]*//g
>>>No Longer using HITDICE, please remove and just use MONSTERCLASS
=====================================
SPELL: becomes SPELLS:Innate|TIMES=x|CASTERLEVEL=x|SpellName1,DC|SpellName2,DC

=====================================
Typically replace 'Heavy blah' with 'blah (Heavy)' etc.
=====================================
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_enhancing.lst
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_base.lst

%s/Willpower/Will/g
%s/ARMR_MWORK/MWORKA/g
%s/ARMR_PLUS_2/PLUS2A/g
%s/ARMR_STEEL/STEEL/g
%s/ARMR_PLUS_3/PLUS3W/g
%s/ARMR_PLUS_1/PLUS1W/g
%s/SHLD_MWORK/MWORKS/g
%s/SHLD_STEEL/STEEL/g
%s/SHLD_WOOD/WOOD/g
%s/SHLD_PLUS_1/PLUS1S/g
%s/SHLD_PLUS_2/PLUS2S/g
%s/WEAP_PLUS_1/PLUS1W/g
%s/WEAP_PLUS_2/PLUS2W/g
%s/WEAP_PLUS_3/PLUS3W/g
%s/WEAP_PLUS_4/PLUS4W/g
%s/WEAP_PLUS_5/PLUS5W/g
%s/WEAP_STEEL/STEEL/g

%s/WEAP_MWORK/MWORKW/g
=====================================

Shields get changed from Small/Large to Light/Heavy and Wooden/Steel to Wood/Metal

=====================================
FRCS/ue_feats.lst - Ice Troll Berserker should modify the rage special ability for natural armor...

=====================================
if you use linux, or have 'cygwin' installed under windows, you can run a bash script to do some extra conversions - note that some of this may be unnecessary as PrettyLst may fix it)

<<--start of file
<nowiki>#!/bin/bash
# SLong and SShort are what we *want* to have finally.
# ALong, AShort and BShort are variations of this (common typos!) that appear initially
# that we want to replace

#################
# save to above commented out as version history once done
SLong="Players Guide to Faerun"
SShort="pgtfae"

ALong="Players Guide to Faerun"
ALong="players guide to faerun"
AShort="pgtfae"
BShort="PGTFAE"

Files=$( ls *.lst)
echo This script indicates the file name, and the first SOURCE entry noted therein as stdout, to allow verification of correct Sed replacement values

for File in ${Files}
do
echo ${File}
grep SOURCE ${File} |head -3 |uniq
printf "SOURCELONG:${SLong}\nSOURCESHORT:${SShort}\n" >a
printf "#Converted by DG $(date +%d/%m/%y)\n\n" >>a

# want to replace characters 93 & 94 (special quotes)
# but cant get sed to recognise them...
# these appear as black squares in vim..
# have to do manually in vim..
#
egrep -v "^SOURCE|^# CVS|#Converted by" $File |\
sed -e 's/Willpower/Will/g' \
-e 's/ARMR_MWORK/MWORKA/g' \
-e 's/AMMO_MWORK/MWORKA/g' \
-e 's/ARMRMW/MWORKA/g' \
-e 's/ARMR_PLUS_1/PLUS1A/g' \
-e 's/ARMR_PLUS_2/PLUS2A/g' \
-e 's/ARMR_PLUS_3/PLUS3A/g' \
-e 's/ARMR_PLUS_4/PLUS4A/g' \
-e 's/ARMR_PLUS_5/PLUS5A/g' \
-e 's/SHLD_MWORK/MWORKA/g' \
-e 's/SHLD_STEEL/STEEL/g' \
-e 's/SHLD_DARKWOOD/DARK/g' \
-e 's/ARMOR_SPIKE_BASH/SPOKE_SB/g' \
-e 's/ARMOR_SPIKE/SPIKE_S/g' \
-e 's/ARMR_STEEL/STEEL/g' \
-e 's/SHLD_WOOD/WOOD/g' \
-e 's/SHLD_PLUS_1/PLUS1S/g' \
-e 's/SHLD_PLUS_2/PLUS2S/g' \
-e 's/SHLD_PLUS_3/PLUS3S/g' \
-e 's/SHLD_PLUS_4/PLUS4S/g' \
-e 's/SHLD_PLUS_5/PLUS5S/g' \
-e 's/WEAP_PLUS_1/PLUS1W/g' \
-e 's/WEAP_PLUS_2/PLUS2W/g' \
-e 's/WEAP_PLUS_3/PLUS3W/g' \
-e 's/WEAP_PLUS_4/PLUS4W/g' \
-e 's/WEAP_PLUS_5/PLUS5W/g' \
-e 's/AMMO_PLUS_1/PLUS1W/g' \
-e 's/AMMO_PLUS_2/PLUS2W/g' \
-e 's/AMMO_PLUS_3/PLUS3W/g' \
-e 's/AMMO_PLUS_4/PLUS4W/g' \
-e 's/AMMO_PLUS_5/PLUS5W/g' \
-e 's/WEAP_BANE/BANE_M/g' \
-e 's/WEAP_STEEL/STEEL/g' \
-e 's/WEAP_VORPAL/VORPAL/g' \
-e 's/WEAP_ALCH_SILVR/ALCHM/g' \
-e 's/WEAP_ALCH_SLVR/ALCHM/g' \
-e 's/WEAP_AXIOMATIC/LAW_M/g' \
-e 's/WEAP_HOLY/HOLY_M/g' \
-e 's/ARMR_DRAGONHIDE/DRACO/g' \
-e 's/AMMO_ALCH_SLVR/ALCHM/g' \
-e 's/AMMO_COLD_IRON/C_IRON/g' \
-e 's/.WEAP_WOOD//g' \
-e 's/AMMO_ALCH_SILVR/ALCHM/g' \
-e 's/MWWEAPON/MWORKW/g' \
-e 's/WEAPMW/MWORKW/g' \
-e 's/WEAP_MWORK/MWORKW/g' \
-e 's/|PREDEFAULTMONSTER:Y//g' \
-e 's/MFEAT/FEAT/g' \
-e 's/HITDICE:[0-9]*,[0-9]*//g' \
-e"s/[|]SOURCELONG:${SLong}//" \
-e"s/[|]SOURCESHORT:${SShort}//" \
-e"s/[|]SOURCESHORT:${AShort}//" \
-e"s/[|]SOURCESHORT:${BShort}//" \
-e's/|SOURCEPAGE/SOURCEPAGE/' \
-e's/[|]SOURCELONG:${ALong}//' \
-e's/SOURCEPAGE/ SOURCEPAGE/' \
-e's/|SOURCE/\tSOURCE/' >>a
# that's a 'tab' two lines up, check when copying
mv a ${File}
done
</nowiki>
<<--end of file-->>

Copy that to a file (remove the <<-- -->> lines) and then execute it

=====================================
other manual changes:

WEAPONPROF:blah to :
BONUS:WEAPONPROF:blah
AUTO:WEAPONPROF|Longsword|Rapier|

BONUS:ToHIT|blah to BONUS:COMBAT:TOHIT|blah

ADD:FEAT|(blah) ADD:FEAT|(blah) to ADD:FEAT|2|blah,blah

Note that LANGBONUS (and potentially others?) take pipe (|) separators in one file but comma separators in others.

Further note that there are various typo's, particularly in 'DEFINE' variables.

Further Notes on CMP to RSRD Migration, part2

2012-02-28T00:09:45Z

FerretDave:

Apologies for the formatting, this probably needs tidying up...This really is just a cut and paste from a scratch file I used whilst converting data
Some of this (most?) is possibly done by PrettyLst (I wasnt using the right options initially!)
Much of it was just notes I'd made as I manually updated some files, and possibly prettylst now does a healthy chunk of the below.

Several of these commands are search and replace regex expressions for VIM (my editor of choice), the concept should be clear though as to the intent (on every line, search for 'foo' and replace with 'bar'), and updating to your editor of choice.
I copy the line from the scratch file, and in vim, press ':' to enter command mode, and then just paste and hit return.

------------------------------------------
replace % with %% in descriptions

Willpower - replace with 'Will'

ADD: can't be used more than once per class line, so split it into two lines. I.e

<nowiki>1<tab>ADD:feat1<tab>ADD:feat2
becomes
1<tab>ADD:feat1
1<tab>ADD:feat2</nowiki>

Cannot have commas in names, just remove them/replace with a space.

------------------------------------------

**Above are confirmed as necessary following proper prettylst conversion, below still need to be validated.**

=====================================
spells file
changed all to .mod other than specific few (20 odd non-srd spells)
note - we only really want the descriptions, not the mechanics..
=====================================
feats file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
ExtraTurning - CHOOSE: nochoice Typo???!!! Type=ExtraTurnig.STACK ??? - updated to match pcgen srd original
CHOOSE:Exotic :- CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Exotic
CHOOSE:Blah|1 := CHOOSE:Blah
PRELEVEL:x := PRELEVEL:MIN=x
PREVARLT:CL=Shaaryan Hunter,6 := PRECLASSLEVELMAX:1,Shaaryan Hunter=5
PREVARGTEQ:CL=Shaaryan Hunter,6 := PRECLASS:1,Shaaryan Hunter=6

AUTO.SHIELDPROF|TYPE := AUTO.SHIELDPROF|SHIELDTYPE
CHOOSE:Martial := CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Martial
CHOOSE:SKILLSNAMED|blah|1 :- CHOOSE:SKILLSNAMED|blah

---------------------------------------------
feats_hidden file
ADD:FEAT(blah)|x :- ADD:FEAT|x|blah
SPELL:Blah|x|Innate := SPELLS:Innate|TIMES=x|Blah
SPELLS:Innate|CASTERLEVEL=max(classlevel("Mage"),1)|Blah
CHOOSE:NUMCHOICES=x| := CHOOSE:x|
**********************************************************************************
TODO Favoured Enemy / Favoured Bonus - all disabled, seems style is quite different
**********************************************************************************
Rogue Bonus -
CHOOSE:SKILLS|3+INT := SELECT:3+INT CHOOSE:SKILLS
=====================================

skills file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
PREMOVE:Blah := PREMOVE:1,Blah
CHOOSE:Language(Spoken) :- CHOOSE:LANGUAGE|Spoken

SA: := SAB:
AUTO.ARMORPROF|TYPE := AUTO.ARMORPROF|ARMORTYPE

=====================================
updates to dieties file
Tag Name: PREALIGN:x,x
Variables Used (x):LG,LN,LE,NG,TN,NE,CG,CN,CE,Deity (Alignment abbreviation).
Variables Used (x):0,1,2,3,4,5,6,7,8,10 (Alignment array number).
LG,LN,LE,NG,TN,NE,CG,CN,CE, Deity
0, 1, 2, 3, 4, 5, 6, 7, 8, 10

%s/ [ ]*FOLLOWERALIGN:147/|PREALIGN:LN,TN,CN /
%s/ [ ]*FOLLOWERALIGN:13457/|PREALIGN:LN,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:258/|PREALIGN:LE,NE,CE /
%s/ [ ]*FOLLOWERALIGN:012/|PREALIGN:LG,LN,LE /
%s/ [ ]*FOLLOWERALIGN:125/|PREALIGN:LN,LE,NE /
%s/ [ ]*FOLLOWERALIGN:036/|PREALIGN:LG,NG,CG /
%s/ [ ]*FOLLOWERALIGN:013/|PREALIGN:LG,LN,NG /
%s/ [ ]*FOLLOWERALIGN:578 /|PREALIGN:NE,CN,CE /
%s/ [ ]*FOLLOWERALIGN:678 /|PREALIGN:CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:367 /|PREALIGN:NG,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345678 /|PREALIGN:LG,LN,LE,NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:013467 /|PREALIGN:LG,LN,NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345 /|PREALIGN:LG,LN,LE,NG,TN,NE /
%s/ [ ]*FOLLOWERALIGN:3467 /|PREALIGN:NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:345678 /|PREALIGN:NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:0123457 /|PREALIGN:LG,LN,LE,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:01236 /|PREALIGN:LG,LN,LE,NG,CG /
%s/ [ ]*FOLLOWERALIGN:2458 /|PREALIGN:LE,TN,NE,CE /
%s/ [ ]*FOLLOWERALIGN:0346 /|PREALIGN:LG,NG,TN,CG /
%s/ [ ]*FOLLOWERALIGN:4678 /|PREALIGN:TN,CG,CN,CE /

PREVARxx| becomes PREVARxx:Var,Value
--------------
%s/|PREDEFAULTMONSTER:Y//g
%s/MFEAT/FEAT/g

# note - need BOTH of the following, first one splits, second one cleans
%s/HITDICE:[0-9]*,/HD:,&HITDICE:\tHITDIE:/
%s/,HITDICE://g
or just remove it completely... %s/HITDICE:[0-9]*,[0-9]*//g
>>>No Longer using HITDICE, please remove and just use MONSTERCLASS
=====================================
SPELL: becomes SPELLS:Innate|TIMES=x|CASTERLEVEL=x|SpellName1,DC|SpellName2,DC

=====================================
Typically replace 'Heavy blah' with 'blah (Heavy)' etc.
=====================================
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_enhancing.lst
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_base.lst

%s/Willpower/Will/g
%s/ARMR_MWORK/MWORKA/g
%s/ARMR_PLUS_2/PLUS2A/g
%s/ARMR_STEEL/STEEL/g
%s/ARMR_PLUS_3/PLUS3W/g
%s/ARMR_PLUS_1/PLUS1W/g
%s/SHLD_MWORK/MWORKS/g
%s/SHLD_STEEL/STEEL/g
%s/SHLD_WOOD/WOOD/g
%s/SHLD_PLUS_1/PLUS1S/g
%s/SHLD_PLUS_2/PLUS2S/g
%s/WEAP_PLUS_1/PLUS1W/g
%s/WEAP_PLUS_2/PLUS2W/g
%s/WEAP_PLUS_3/PLUS3W/g
%s/WEAP_PLUS_4/PLUS4W/g
%s/WEAP_PLUS_5/PLUS5W/g
%s/WEAP_STEEL/STEEL/g

%s/WEAP_MWORK/MWORKW/g
=====================================

Shields get changed from Small/Large to Light/Heavy and Wooden/Steel to Wood/Metal

=====================================
FRCS/ue_feats.lst - Ice Troll Berserker should modify the rage special ability for natural armor...

=====================================
if you use linux, or have 'cygwin' installed under windows, you can run a bash script to do some extra conversions - note that some of this may be unnecessary as PrettyLst may fix it)

<<--start of file
# SLong and SShort are what we *want* to have finally.
# ALong, AShort and BShort are variations of this (common typos!) that appear initially
# that we want to replace

#################
# save to above commented out as version history once done
SLong="Players Guide to Faerun"
SShort="pgtfae"

ALong="Players Guide to Faerun"
ALong="players guide to faerun"
AShort="pgtfae"
BShort="PGTFAE"

Files=$( ls *.lst)
echo This script indicates the file name, and the first SOURCE entry noted therein as stdout, to allow verification of correct Sed replacement values

for File in ${Files}
do
echo ${File}
grep SOURCE ${File} |head -3 |uniq
printf "SOURCELONG:${SLong}\nSOURCESHORT:${SShort}\n" >a
printf "#Converted by DG $(date +%d/%m/%y)\n\n" >>a

# want to replace characters 93 & 94 (special quotes)
# but cant get sed to recognise them...
# these appear as black squares in vim..
# have to do manually in vim..
#
egrep -v "^SOURCE|^# CVS|#Converted by" $File |\
sed -e 's/Willpower/Will/g' \
-e 's/ARMR_MWORK/MWORKA/g' \
-e 's/AMMO_MWORK/MWORKA/g' \
-e 's/ARMRMW/MWORKA/g' \
-e 's/ARMR_PLUS_1/PLUS1A/g' \
-e 's/ARMR_PLUS_2/PLUS2A/g' \
-e 's/ARMR_PLUS_3/PLUS3A/g' \
-e 's/ARMR_PLUS_4/PLUS4A/g' \
-e 's/ARMR_PLUS_5/PLUS5A/g' \
-e 's/SHLD_MWORK/MWORKA/g' \
-e 's/SHLD_STEEL/STEEL/g' \
-e 's/SHLD_DARKWOOD/DARK/g' \
-e 's/ARMOR_SPIKE_BASH/SPOKE_SB/g' \
-e 's/ARMOR_SPIKE/SPIKE_S/g' \
-e 's/ARMR_STEEL/STEEL/g' \
-e 's/SHLD_WOOD/WOOD/g' \
-e 's/SHLD_PLUS_1/PLUS1S/g' \
-e 's/SHLD_PLUS_2/PLUS2S/g' \
-e 's/SHLD_PLUS_3/PLUS3S/g' \
-e 's/SHLD_PLUS_4/PLUS4S/g' \
-e 's/SHLD_PLUS_5/PLUS5S/g' \
-e 's/WEAP_PLUS_1/PLUS1W/g' \
-e 's/WEAP_PLUS_2/PLUS2W/g' \
-e 's/WEAP_PLUS_3/PLUS3W/g' \
-e 's/WEAP_PLUS_4/PLUS4W/g' \
-e 's/WEAP_PLUS_5/PLUS5W/g' \
-e 's/AMMO_PLUS_1/PLUS1W/g' \
-e 's/AMMO_PLUS_2/PLUS2W/g' \
-e 's/AMMO_PLUS_3/PLUS3W/g' \
-e 's/AMMO_PLUS_4/PLUS4W/g' \
-e 's/AMMO_PLUS_5/PLUS5W/g' \
-e 's/WEAP_BANE/BANE_M/g' \
-e 's/WEAP_STEEL/STEEL/g' \
-e 's/WEAP_VORPAL/VORPAL/g' \
-e 's/WEAP_ALCH_SILVR/ALCHM/g' \
-e 's/WEAP_ALCH_SLVR/ALCHM/g' \
-e 's/WEAP_AXIOMATIC/LAW_M/g' \
-e 's/WEAP_HOLY/HOLY_M/g' \
-e 's/ARMR_DRAGONHIDE/DRACO/g' \
-e 's/AMMO_ALCH_SLVR/ALCHM/g' \
-e 's/AMMO_COLD_IRON/C_IRON/g' \
-e 's/.WEAP_WOOD//g' \
-e 's/AMMO_ALCH_SILVR/ALCHM/g' \
-e 's/MWWEAPON/MWORKW/g' \
-e 's/WEAPMW/MWORKW/g' \
-e 's/WEAP_MWORK/MWORKW/g' \
-e 's/|PREDEFAULTMONSTER:Y//g' \
-e 's/MFEAT/FEAT/g' \
-e 's/HITDICE:[0-9]*,[0-9]*//g' \
-e"s/[|]SOURCELONG:${SLong}//" \
-e"s/[|]SOURCESHORT:${SShort}//" \
-e"s/[|]SOURCESHORT:${AShort}//" \
-e"s/[|]SOURCESHORT:${BShort}//" \
-e's/|SOURCEPAGE/SOURCEPAGE/' \
-e's/[|]SOURCELONG:${ALong}//' \
-e's/SOURCEPAGE/ SOURCEPAGE/' \
-e's/|SOURCE/\tSOURCE/' >>a
# that's a 'tab' two lines up, check when copying
mv a ${File}
done

<<--end of file-->>

Copy that to a file (remove the <<-- -->> lines) and then execute it, with something like:
cat SedCommands.txt |bash

=====================================
other manual changes:

WEAPONPROF:blah to :
BONUS:WEAPONPROF:blah
AUTO:WEAPONPROF|Longsword|Rapier|

BONUS:ToHIT|blah to BONUS:COMBAT:TOHIT|blah

ADD:FEAT|(blah) ADD:FEAT|(blah) to ADD:FEAT|2|blah,blah

Note that LANGBONUS (and potentially others?) take pipe (|) separators in one file but comma separators in others.

Further note that there are various typo's, particularly in 'DEFINE' variables.

Further Notes on CMP to RSRD Migration, part2

2012-02-27T19:43:27Z

FerretDave:

Apologies for the formatting, this probably needs tidying up...This really is just a cut and paste from a scratch file I used whilst converting data
Some of this (most?) is possibly done by PrettyLst (I wasnt using the right options initially!)
Much of it was just notes I'd made as I manually updated some files, and possibly prettylst now does a healthy chunk of the below.

Several of these commands are search and replace regex expressions for VIM (my editor of choice), the concept should be clear though as to the intent (on every line, search for 'foo' and replace with 'bar'), and updating to your editor of choice.
I copy the line from the scratch file, and in vim, press ':' to enter command mode, and then just paste and hit return.

------------------------------------------
replace % with %% in descriptions
Willpower - replace with 'Will'
ADD: can't be used more than once per class line, so split it into two lines. I.e
<nowiki>1<tab>ADD:feat1<tab>ADD:feat2
becomes
1<tab>ADD:feat1
1<tab>ADD:feat2</nowiki>
Cannot have commas in names, just remove them/replace with a space.

------------------------------------------

**Above are confirmed as necessary following proper prettylst conversion, below still need to be validated.**

=====================================
spells file
changed all to .mod other than specific few (20 odd non-srd spells)
note - we only really want the descriptions, not the mechanics..
=====================================
feats file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
ExtraTurning - CHOOSE: nochoice Typo???!!! Type=ExtraTurnig.STACK ??? - updated to match pcgen srd original
CHOOSE:Exotic :- CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Exotic
CHOOSE:Blah|1 := CHOOSE:Blah
PRELEVEL:x := PRELEVEL:MIN=x
PREVARLT:CL=Shaaryan Hunter,6 := PRECLASSLEVELMAX:1,Shaaryan Hunter=5
PREVARGTEQ:CL=Shaaryan Hunter,6 := PRECLASS:1,Shaaryan Hunter=6

AUTO.SHIELDPROF|TYPE := AUTO.SHIELDPROF|SHIELDTYPE
CHOOSE:Martial := CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Martial
CHOOSE:SKILLSNAMED|blah|1 :- CHOOSE:SKILLSNAMED|blah

---------------------------------------------
feats_hidden file
ADD:FEAT(blah)|x :- ADD:FEAT|x|blah
SPELL:Blah|x|Innate := SPELLS:Innate|TIMES=x|Blah
SPELLS:Innate|CASTERLEVEL=max(classlevel("Mage"),1)|Blah
CHOOSE:NUMCHOICES=x| := CHOOSE:x|
**********************************************************************************
TODO Favoured Enemy / Favoured Bonus - all disabled, seems style is quite different
**********************************************************************************
Rogue Bonus -
CHOOSE:SKILLS|3+INT := SELECT:3+INT CHOOSE:SKILLS
=====================================

skills file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
PREMOVE:Blah := PREMOVE:1,Blah
CHOOSE:Language(Spoken) :- CHOOSE:LANGUAGE|Spoken

SA: := SAB:
AUTO.ARMORPROF|TYPE := AUTO.ARMORPROF|ARMORTYPE

=====================================
updates to dieties file
Tag Name: PREALIGN:x,x
Variables Used (x):LG,LN,LE,NG,TN,NE,CG,CN,CE,Deity (Alignment abbreviation).
Variables Used (x):0,1,2,3,4,5,6,7,8,10 (Alignment array number).
LG,LN,LE,NG,TN,NE,CG,CN,CE, Deity
0, 1, 2, 3, 4, 5, 6, 7, 8, 10

%s/ [ ]*FOLLOWERALIGN:147/|PREALIGN:LN,TN,CN /
%s/ [ ]*FOLLOWERALIGN:13457/|PREALIGN:LN,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:258/|PREALIGN:LE,NE,CE /
%s/ [ ]*FOLLOWERALIGN:012/|PREALIGN:LG,LN,LE /
%s/ [ ]*FOLLOWERALIGN:125/|PREALIGN:LN,LE,NE /
%s/ [ ]*FOLLOWERALIGN:036/|PREALIGN:LG,NG,CG /
%s/ [ ]*FOLLOWERALIGN:013/|PREALIGN:LG,LN,NG /
%s/ [ ]*FOLLOWERALIGN:578 /|PREALIGN:NE,CN,CE /
%s/ [ ]*FOLLOWERALIGN:678 /|PREALIGN:CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:367 /|PREALIGN:NG,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345678 /|PREALIGN:LG,LN,LE,NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:013467 /|PREALIGN:LG,LN,NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345 /|PREALIGN:LG,LN,LE,NG,TN,NE /
%s/ [ ]*FOLLOWERALIGN:3467 /|PREALIGN:NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:345678 /|PREALIGN:NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:0123457 /|PREALIGN:LG,LN,LE,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:01236 /|PREALIGN:LG,LN,LE,NG,CG /
%s/ [ ]*FOLLOWERALIGN:2458 /|PREALIGN:LE,TN,NE,CE /
%s/ [ ]*FOLLOWERALIGN:0346 /|PREALIGN:LG,NG,TN,CG /
%s/ [ ]*FOLLOWERALIGN:4678 /|PREALIGN:TN,CG,CN,CE /

PREVARxx| becomes PREVARxx:Var,Value
--------------
%s/|PREDEFAULTMONSTER:Y//g
%s/MFEAT/FEAT/g

# note - need BOTH of the following, first one splits, second one cleans
%s/HITDICE:[0-9]*,/HD:,&HITDICE:\tHITDIE:/
%s/,HITDICE://g
or just remove it completely... %s/HITDICE:[0-9]*,[0-9]*//g
>>>No Longer using HITDICE, please remove and just use MONSTERCLASS
=====================================
SPELL: becomes SPELLS:Innate|TIMES=x|CASTERLEVEL=x|SpellName1,DC|SpellName2,DC

=====================================
Typically replace 'Heavy blah' with 'blah (Heavy)' etc.
=====================================
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_enhancing.lst
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_base.lst

%s/Willpower/Will/g
%s/ARMR_MWORK/MWORKA/g
%s/ARMR_PLUS_2/PLUS2A/g
%s/ARMR_STEEL/STEEL/g
%s/ARMR_PLUS_3/PLUS3W/g
%s/ARMR_PLUS_1/PLUS1W/g
%s/SHLD_MWORK/MWORKS/g
%s/SHLD_STEEL/STEEL/g
%s/SHLD_WOOD/WOOD/g
%s/SHLD_PLUS_1/PLUS1S/g
%s/SHLD_PLUS_2/PLUS2S/g
%s/WEAP_PLUS_1/PLUS1W/g
%s/WEAP_PLUS_2/PLUS2W/g
%s/WEAP_PLUS_3/PLUS3W/g
%s/WEAP_PLUS_4/PLUS4W/g
%s/WEAP_PLUS_5/PLUS5W/g
%s/WEAP_STEEL/STEEL/g

%s/WEAP_MWORK/MWORKW/g
=====================================

Shields get changed from Small/Large to Light/Heavy and Wooden/Steel to Wood/Metal

=====================================
FRCS/ue_feats.lst - Ice Troll Berserker should modify the rage special ability for natural armor...

=====================================
if you use linux, or have 'cygwin' installed under windows, you can run a bash script to do some extra conversions - note that some of this may be unnecessary as PrettyLst may fix it)

<<--start of file
# SLong and SShort are what we *want* to have finally.
# ALong, AShort and BShort are variations of this (common typos!) that appear initially
# that we want to replace

#################
# save to above commented out as version history once done
SLong="Players Guide to Faerun"
SShort="pgtfae"

ALong="Players Guide to Faerun"
ALong="players guide to faerun"
AShort="pgtfae"
BShort="PGTFAE"

Files=$( ls *.lst)
echo This script indicates the file name, and the first SOURCE entry noted therein as stdout, to allow verification of correct Sed replacement values

for File in ${Files}
do
echo ${File}
grep SOURCE ${File} |head -3 |uniq
printf "SOURCELONG:${SLong}\nSOURCESHORT:${SShort}\n" >a
printf "#Converted by DG $(date +%d/%m/%y)\n\n" >>a

# want to replace characters 93 & 94 (special quotes)
# but cant get sed to recognise them...
# these appear as black squares in vim..
# have to do manually in vim..
#
egrep -v "^SOURCE|^# CVS|#Converted by" $File |\
sed -e 's/Willpower/Will/g' \
-e 's/ARMR_MWORK/MWORKA/g' \
-e 's/AMMO_MWORK/MWORKA/g' \
-e 's/ARMRMW/MWORKA/g' \
-e 's/ARMR_PLUS_1/PLUS1A/g' \
-e 's/ARMR_PLUS_2/PLUS2A/g' \
-e 's/ARMR_PLUS_3/PLUS3A/g' \
-e 's/ARMR_PLUS_4/PLUS4A/g' \
-e 's/ARMR_PLUS_5/PLUS5A/g' \
-e 's/SHLD_MWORK/MWORKA/g' \
-e 's/SHLD_STEEL/STEEL/g' \
-e 's/SHLD_DARKWOOD/DARK/g' \
-e 's/ARMOR_SPIKE_BASH/SPOKE_SB/g' \
-e 's/ARMOR_SPIKE/SPIKE_S/g' \
-e 's/ARMR_STEEL/STEEL/g' \
-e 's/SHLD_WOOD/WOOD/g' \
-e 's/SHLD_PLUS_1/PLUS1S/g' \
-e 's/SHLD_PLUS_2/PLUS2S/g' \
-e 's/SHLD_PLUS_3/PLUS3S/g' \
-e 's/SHLD_PLUS_4/PLUS4S/g' \
-e 's/SHLD_PLUS_5/PLUS5S/g' \
-e 's/WEAP_PLUS_1/PLUS1W/g' \
-e 's/WEAP_PLUS_2/PLUS2W/g' \
-e 's/WEAP_PLUS_3/PLUS3W/g' \
-e 's/WEAP_PLUS_4/PLUS4W/g' \
-e 's/WEAP_PLUS_5/PLUS5W/g' \
-e 's/AMMO_PLUS_1/PLUS1W/g' \
-e 's/AMMO_PLUS_2/PLUS2W/g' \
-e 's/AMMO_PLUS_3/PLUS3W/g' \
-e 's/AMMO_PLUS_4/PLUS4W/g' \
-e 's/AMMO_PLUS_5/PLUS5W/g' \
-e 's/WEAP_BANE/BANE_M/g' \
-e 's/WEAP_STEEL/STEEL/g' \
-e 's/WEAP_VORPAL/VORPAL/g' \
-e 's/WEAP_ALCH_SILVR/ALCHM/g' \
-e 's/WEAP_ALCH_SLVR/ALCHM/g' \
-e 's/WEAP_AXIOMATIC/LAW_M/g' \
-e 's/WEAP_HOLY/HOLY_M/g' \
-e 's/ARMR_DRAGONHIDE/DRACO/g' \
-e 's/AMMO_ALCH_SLVR/ALCHM/g' \
-e 's/AMMO_COLD_IRON/C_IRON/g' \
-e 's/.WEAP_WOOD//g' \
-e 's/AMMO_ALCH_SILVR/ALCHM/g' \
-e 's/MWWEAPON/MWORKW/g' \
-e 's/WEAPMW/MWORKW/g' \
-e 's/WEAP_MWORK/MWORKW/g' \
-e 's/|PREDEFAULTMONSTER:Y//g' \
-e 's/MFEAT/FEAT/g' \
-e 's/HITDICE:[0-9]*,[0-9]*//g' \
-e"s/[|]SOURCELONG:${SLong}//" \
-e"s/[|]SOURCESHORT:${SShort}//" \
-e"s/[|]SOURCESHORT:${AShort}//" \
-e"s/[|]SOURCESHORT:${BShort}//" \
-e's/|SOURCEPAGE/SOURCEPAGE/' \
-e's/[|]SOURCELONG:${ALong}//' \
-e's/SOURCEPAGE/ SOURCEPAGE/' \
-e's/|SOURCE/\tSOURCE/' >>a
# that's a 'tab' two lines up, check when copying
mv a ${File}
done

<<--end of file-->>

Copy that to a file (remove the <<-- -->> lines) and then execute it, with something like:
cat SedCommands.txt |bash

=====================================
other manual changes:

WEAPONPROF:blah to :
BONUS:WEAPONPROF:blah
AUTO:WEAPONPROF|Longsword|Rapier|

BONUS:ToHIT|blah to BONUS:COMBAT:TOHIT|blah

ADD:FEAT|(blah) ADD:FEAT|(blah) to ADD:FEAT|2|blah,blah

Note that LANGBONUS (and potentially others?) take pipe (|) separators in one file but comma separators in others.

Further note that there are various typo's, particularly in 'DEFINE' variables.

Further notes on CMP to RSRD

2012-02-27T19:31:11Z

FerretDave:

Further notes on CMP to RSRD

2012-02-27T19:15:19Z

FerretDave: Hints on migrating CMP to RSRD

Further notes on CMP to RSRD

2012-02-27T10:57:45Z

FerretDave: batch file startup suggestion added

Updating Homebrew Sets

2012-02-24T23:38:25Z

FerretDave: /* 5.12.x-->5.14.x */

{| align="right"
| __TOC__
|}

=Introduction=
This section is for updating older homebrew LST files to use the current standards. This is a work in progress. Any questions ask on the PCGen Yahoo Group.

==PrettyLST==

* First off we'll need [http://sourceforge.net/projects/pcgen/files/PrettyLst/v%201.39%20build%208180/prettylst_1-39_build-8180.zip/download PrettyLST] for earlier versions of PCGen

* Next, to run PrettyLST you'll need [https://www.activestate.com/activeperl/downloads/ ActivePerl].

* You will want to run PrettyLST with the Conversion Flag turned on to bring your sets up to 5.12 standards. Note this is not a perfect conversion, you will need to check your materials against any errors PrettyLST outputs.

It's a good idea to be methodical over this, and convert a single set at a time, otherwise the number of errors and warnings you'll have to get through may well become overwhelming.
Keep track of what you have converted.

you'll want to run PrettyLst with a command line such as:

perl prettylst.pl -i=d:\pcgen_convert\input -o=d:\pcgen_convert\intermediate -gamemode=35e -systempath D:\utils\PCGen\PCGen5120\system -e=error.txt -convert pcgen512

That '-convert pcgen512' is the flag to actually perform the conversion (otherwise its just reformatting the field order and indentation).

-i specifies the directory your old data set is in currently (note that here I've setup specific directories completely outside of my 'normal' dataset directory, so I don't risk messing up any 'live' sets.

-o indicates the output directory (I use an 'intermediate' directory, which will be used as the input for the next script (Baraks) below).

-gamemode=35e specifies the gamemode we're converting, you can leave this off, and prettylst will determine what you need, though I find migrating CMP datasets to 35e means I can make use of many other PCGen enhancements and get a better experience.

-systempath is a path to the installed PCGen 5.12.0, I'm not totally sure this is needed actually, but it cant hurt :-)

-e defines where the error output is going to be written.

I suggest you put the above into a batch file (RunConvert1.bat) to make it easier to run under windows.

Run the batch file, read the error messages, make any updates to the sources in the *input* directory, and re-run the batch file, repeat until either A) you have no more errors, or B) (more likely) you get fed up trying to fix them :-)
There are numerous warnings you can (probably) ignore (further options to prettylst reduce warning levels), and many that are just plain difficult to resolve at this stage - further steps below may fix them, or it may be cross references into other sources that you havent converted yet...

NOTE - if you do migrate CMP to RSRD (I personally recommend this, opinions may differ) many things (races, classes, spells, equipment...) are easier if they .MOD an appropriate (standard PCGen) 3.5 (or 3e!) dataset.

[[Further notes on CMP to RSRD]]

==5.12.x-->5.14.x==

For 5.12 to 5.14 you'll want to use [http://tech.groups.yahoo.com/group/PCGenListFileHelp/files/Misc/5.12%20to%205.14%20Conversion_v085.zip Barak's Script]

Again you'll need perl, see above. You may also need to jon the PCGenLiSTFileHelp group to access the file. I put the script with PrettyLST.

Following the methodology above to get datasets up to 5.12.0, with a dataset in d:\pcgen_convert\intermediate, run Baraks script as:

perl convert_514.pl -I=d:\pcgen_convert\intermediate -O=d:\pcgen_convert\output

Check the 'convert_514_log.txt' file for errors, edit the files in the 'intermediate'* directory to fix, and re-run Baraks script again.

*(or edit in the original 'input' directory, and run both the PrettyLst conversion and then Baraks script again - this ensures that you only edit one set of files and don't risk overwriting your edited intermediate files)

==5.14.x-->5.16.x==

5.16.x and beyond has a Converter included with PCGen. That Version of PCGen will update any files from the previous version. So the 5.16.x converter will bring 5.14.x files forward to 5.16.x standards.

Use the 5.16 Converter to bring 5.14 sets forward.

NOTE: The Converter will bring the previous cycle forward, do not use 6.0 to bring 5.14 forward, use 5.16 to do that.

==5.16.x-->6.0.x==
Use the 6.0 PCGen Converter

==Massive Changes that WILL affect Homebrew Users==
=Starting 5.16.4 and 5.17.4=
All the Armor BONUS TYPES got a bit of a Change. This WILL affect any homebrew sets that use any PCGen released core sets.

The Following needs to be done to follow the standards:

* Races that grant Natural Armor need to use this format:
BONUS:COMBAT|AC|x|TYPE=NaturalArmor
this replaces the old format of BONUS:COMBAT|AC|x|TYPE=NaturalArmor.REPLACE

* Anything that improves Natural Armor not by enhancement needs to use this format:
BONUS:COMBAT|AC|x|TYPE=NaturalArmor.STACK
this replaces the old format of BONUS:COMBAT|AC|x|TYPE=NaturalArmor.REPLACE
BONUS:COMBAT|AC|x|TYPE=NaturalArmorEnhancement
should be used for any Natural Armor Enhancement

The same applies for Armor.REPLACE and Shield.REPLACE; these both become Armor and Shield respectively. If there is an enhancement you wish to and, just append 'Enhancement' to the Bonus type 'ArmorEnhancement', 'ShieldEnhancement'.

* For Armor and Shield:
BONUS:COMBAT|AC|x|TYPE=ArmorEnhancement
This replaces '''BONUS:COMBAT|AC|x|TYPE=Armor.REPLACE'''

BONUS:COMBAT|AC|x|TYPE:ShieldEnhancement
This replaces '''BONUS:COMBAT|AC|x|TYPE=Shield.REPLACE'''

* 3rd Edition has a slight variation. We don't use 'Shield' or 'ShieldEnhancement' instead we use:
ArmorShield
For Armor Bonus derived from the Shield
ArmorShieldEnhancement
For the Armor Bonus granted from the Shield Enhancement

This was done to make the stacking rules work more uniformly, and avoid overlap stacking where it shouldn't occur.

Further Notes on CMP to RSRD Migration, part2

2012-02-24T23:32:27Z

FerretDave: /* = */

This really is just a cut and paste from a scratch file I used whilst converting data
Some of this (most?) is possibly done by PrettyLst (I wasnt using the right options initially!)

Several of these commands are search and replace regex expressions for VIM (my editor of choice), the concept should be clear though as to the intent, and updating to your editor of choice.
I copy the line from the scratch file, and in vim, press ':' to enter command mode, and then just paste and hit return.

replace % with %% in descriptions
=====================================
spells file
changed all to .mod other than specific few (20 odd non-srd spells)
note - we only really want the descriptions, not the mechanics..
=====================================
feats file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
ExtraTurning - CHOOSE: nochoice Typo???!!! Type=ExtraTurnig.STACK ??? - updated to match pcgen srd original
CHOOSE:Exotic :- CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Exotic
CHOOSE:Blah|1 := CHOOSE:Blah
PRELEVEL:x := PRELEVEL:MIN=x
PREVARLT:CL=Shaaryan Hunter,6 := PRECLASSLEVELMAX:1,Shaaryan Hunter=5
PREVARGTEQ:CL=Shaaryan Hunter,6 := PRECLASS:1,Shaaryan Hunter=6

AUTO.SHIELDPROF|TYPE := AUTO.SHIELDPROF|SHIELDTYPE
CHOOSE:Martial := CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Martial
CHOOSE:SKILLSNAMED|blah|1 :- CHOOSE:SKILLSNAMED|blah

---------------------------------------------
feats_hidden file
ADD:FEAT(blah)|x :- ADD:FEAT|x|blah
SPELL:Blah|x|Innate := SPELLS:Innate|TIMES=x|Blah
SPELLS:Innate|CASTERLEVEL=max(classlevel("Mage"),1)|Blah
CHOOSE:NUMCHOICES=x| := CHOOSE:x|
**********************************************************************************
TODO Favoured Enemy / Favoured Bonus - all disabled, seems style is quite different
**********************************************************************************
Rogue Bonus -
CHOOSE:SKILLS|3+INT := SELECT:3+INT CHOOSE:SKILLS
=====================================

skills file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
PREMOVE:Blah := PREMOVE:1,Blah
CHOOSE:Language(Spoken) :- CHOOSE:LANGUAGE|Spoken

SA: := SAB:
AUTO.ARMORPROF|TYPE := AUTO.ARMORPROF|ARMORTYPE

=====================================
updates to dieties file
Tag Name: PREALIGN:x,x
Variables Used (x):LG,LN,LE,NG,TN,NE,CG,CN,CE,Deity (Alignment abbreviation).
Variables Used (x):0,1,2,3,4,5,6,7,8,10 (Alignment array number).
LG,LN,LE,NG,TN,NE,CG,CN,CE, Deity
0, 1, 2, 3, 4, 5, 6, 7, 8, 10

%s/ [ ]*FOLLOWERALIGN:147/|PREALIGN:LN,TN,CN /
%s/ [ ]*FOLLOWERALIGN:13457/|PREALIGN:LN,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:258/|PREALIGN:LE,NE,CE /
%s/ [ ]*FOLLOWERALIGN:012/|PREALIGN:LG,LN,LE /
%s/ [ ]*FOLLOWERALIGN:125/|PREALIGN:LN,LE,NE /
%s/ [ ]*FOLLOWERALIGN:036/|PREALIGN:LG,NG,CG /
%s/ [ ]*FOLLOWERALIGN:013/|PREALIGN:LG,LN,NG /
%s/ [ ]*FOLLOWERALIGN:578 /|PREALIGN:NE,CN,CE /
%s/ [ ]*FOLLOWERALIGN:678 /|PREALIGN:CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:367 /|PREALIGN:NG,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345678 /|PREALIGN:LG,LN,LE,NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:013467 /|PREALIGN:LG,LN,NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345 /|PREALIGN:LG,LN,LE,NG,TN,NE /
%s/ [ ]*FOLLOWERALIGN:3467 /|PREALIGN:NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:345678 /|PREALIGN:NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:0123457 /|PREALIGN:LG,LN,LE,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:01236 /|PREALIGN:LG,LN,LE,NG,CG /
%s/ [ ]*FOLLOWERALIGN:2458 /|PREALIGN:LE,TN,NE,CE /
%s/ [ ]*FOLLOWERALIGN:0346 /|PREALIGN:LG,NG,TN,CG /
%s/ [ ]*FOLLOWERALIGN:4678 /|PREALIGN:TN,CG,CN,CE /

PREVARxx| becomes PREVARxx:Var,Value
--------------
%s/|PREDEFAULTMONSTER:Y//g
%s/MFEAT/FEAT/g

# note - need BOTH of the following, first one splits, second one cleans
%s/HITDICE:[0-9]*,/HD:,&HITDICE:\tHITDIE:/
%s/,HITDICE://g
or just remove it completely... %s/HITDICE:[0-9]*,[0-9]*//g
>>>No Longer using HITDICE, please remove and just use MONSTERCLASS
=====================================
SPELL: becomes SPELLS:Innate|TIMES=x|CASTERLEVEL=x|SpellName1,DC|SpellName2,DC

=====================================
Typically replace 'Heavy blah' with 'blah (Heavy)' etc.
=====================================
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_enhancing.lst
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_base.lst

%s/Willpower/Will/g
%s/ARMR_MWORK/MWORKA/g
%s/ARMR_PLUS_2/PLUS2A/g
%s/ARMR_STEEL/STEEL/g
%s/ARMR_PLUS_3/PLUS3W/g
%s/ARMR_PLUS_1/PLUS1W/g
%s/SHLD_MWORK/MWORKS/g
%s/SHLD_STEEL/STEEL/g
%s/SHLD_WOOD/WOOD/g
%s/SHLD_PLUS_1/PLUS1S/g
%s/SHLD_PLUS_2/PLUS2S/g
%s/WEAP_PLUS_1/PLUS1W/g
%s/WEAP_PLUS_2/PLUS2W/g
%s/WEAP_PLUS_3/PLUS3W/g
%s/WEAP_PLUS_4/PLUS4W/g
%s/WEAP_PLUS_5/PLUS5W/g
%s/WEAP_STEEL/STEEL/g

%s/WEAP_MWORK/MWORKW/g
=====================================

Shields get changed from Small/Large to Light/Heavy and Wooden/Steel to Wood/Metal

=====================================
FRCS/ue_feats.lst - Ice Troll Berserker should modify the rage special ability for natural armor...

=====================================
if you use linux, or have 'cygwin' installed under windows, you can run a bash script to do some extra conversions - note that some of this may be unnecessary as PrettyLst may fix it)

<<--start of file
# SLong and SShort are what we *want* to have finally.
# ALong, AShort and BShort are variations of this (common typos!) that appear initially
# that we want to replace

#################
# save to above commented out as version history once done
SLong="Players Guide to Faerun"
SShort="pgtfae"

ALong="Players Guide to Faerun"
ALong="players guide to faerun"
AShort="pgtfae"
BShort="PGTFAE"

Files=$( ls *.lst)
echo This script indicates the file name, and the first SOURCE entry noted therein as stdout, to allow verification of correct Sed replacement values

for File in ${Files}
do
echo ${File}
grep SOURCE ${File} |head -3 |uniq
printf "SOURCELONG:${SLong}\nSOURCESHORT:${SShort}\n" >a
printf "#Converted by DG $(date +%d/%m/%y)\n\n" >>a

# want to replace characters 93 & 94 (special quotes)
# but cant get sed to recognise them...
# these appear as black squares in vim..
# have to do manually in vim..
#
egrep -v "^SOURCE|^# CVS|#Converted by" $File |\
sed -e 's/Willpower/Will/g' \
-e 's/ARMR_MWORK/MWORKA/g' \
-e 's/AMMO_MWORK/MWORKA/g' \
-e 's/ARMRMW/MWORKA/g' \
-e 's/ARMR_PLUS_1/PLUS1A/g' \
-e 's/ARMR_PLUS_2/PLUS2A/g' \
-e 's/ARMR_PLUS_3/PLUS3A/g' \
-e 's/ARMR_PLUS_4/PLUS4A/g' \
-e 's/ARMR_PLUS_5/PLUS5A/g' \
-e 's/SHLD_MWORK/MWORKA/g' \
-e 's/SHLD_STEEL/STEEL/g' \
-e 's/SHLD_DARKWOOD/DARK/g' \
-e 's/ARMOR_SPIKE_BASH/SPOKE_SB/g' \
-e 's/ARMOR_SPIKE/SPIKE_S/g' \
-e 's/ARMR_STEEL/STEEL/g' \
-e 's/SHLD_WOOD/WOOD/g' \
-e 's/SHLD_PLUS_1/PLUS1S/g' \
-e 's/SHLD_PLUS_2/PLUS2S/g' \
-e 's/SHLD_PLUS_3/PLUS3S/g' \
-e 's/SHLD_PLUS_4/PLUS4S/g' \
-e 's/SHLD_PLUS_5/PLUS5S/g' \
-e 's/WEAP_PLUS_1/PLUS1W/g' \
-e 's/WEAP_PLUS_2/PLUS2W/g' \
-e 's/WEAP_PLUS_3/PLUS3W/g' \
-e 's/WEAP_PLUS_4/PLUS4W/g' \
-e 's/WEAP_PLUS_5/PLUS5W/g' \
-e 's/AMMO_PLUS_1/PLUS1W/g' \
-e 's/AMMO_PLUS_2/PLUS2W/g' \
-e 's/AMMO_PLUS_3/PLUS3W/g' \
-e 's/AMMO_PLUS_4/PLUS4W/g' \
-e 's/AMMO_PLUS_5/PLUS5W/g' \
-e 's/WEAP_BANE/BANE_M/g' \
-e 's/WEAP_STEEL/STEEL/g' \
-e 's/WEAP_VORPAL/VORPAL/g' \
-e 's/WEAP_ALCH_SILVR/ALCHM/g' \
-e 's/WEAP_ALCH_SLVR/ALCHM/g' \
-e 's/WEAP_AXIOMATIC/LAW_M/g' \
-e 's/WEAP_HOLY/HOLY_M/g' \
-e 's/ARMR_DRAGONHIDE/DRACO/g' \
-e 's/AMMO_ALCH_SLVR/ALCHM/g' \
-e 's/AMMO_COLD_IRON/C_IRON/g' \
-e 's/.WEAP_WOOD//g' \
-e 's/AMMO_ALCH_SILVR/ALCHM/g' \
-e 's/MWWEAPON/MWORKW/g' \
-e 's/WEAPMW/MWORKW/g' \
-e 's/WEAP_MWORK/MWORKW/g' \
-e 's/|PREDEFAULTMONSTER:Y//g' \
-e 's/MFEAT/FEAT/g' \
-e 's/HITDICE:[0-9]*,[0-9]*//g' \
-e"s/[|]SOURCELONG:${SLong}//" \
-e"s/[|]SOURCESHORT:${SShort}//" \
-e"s/[|]SOURCESHORT:${AShort}//" \
-e"s/[|]SOURCESHORT:${BShort}//" \
-e's/|SOURCEPAGE/SOURCEPAGE/' \
-e's/[|]SOURCELONG:${ALong}//' \
-e's/SOURCEPAGE/ SOURCEPAGE/' \
-e's/|SOURCE/\tSOURCE/' >>a
# that's a 'tab' two lines up, check when copying
mv a ${File}
done

<<--end of file-->>

Copy that to a file (remove the <<-- -->> lines) and then execute it, with something like:
cat SedCommands.txt |bash

=====================================
other manual changes:

WEAPONPROF:blah to :
BONUS:WEAPONPROF:blah
AUTO:WEAPONPROF|Longsword|Rapier|

BONUS:ToHIT|blah to BONUS:COMBAT:TOHIT|blah

ADD:FEAT|(blah) ADD:FEAT|(blah) to ADD:FEAT|2|blah,blah

Note that LANGBONUS (and potentially others?) take pipe (|) separators in one file but comma separators in others.

Further note that there are various typo's, particularly in 'DEFINE' variables.

Further Notes on CMP to RSRD Migration, part2

2012-02-24T23:29:50Z

FerretDave: /* = */

This really is just a cut and paste from a scratch file I used whilst converting data
Some of this (most?) is possibly done by PrettyLst (I wasnt using the right options initially!)

Several of these commands are search and replace regex expressions for VIM (my editor of choice), the concept should be clear though as to the intent, and updating to your editor of choice.
I copy the line from the scratch file, and in vim, press ':' to enter command mode, and then just paste and hit return.

replace % with %% in descriptions
=====================================
spells file
changed all to .mod other than specific few (20 odd non-srd spells)
note - we only really want the descriptions, not the mechanics..
=====================================
feats file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
ExtraTurning - CHOOSE: nochoice Typo???!!! Type=ExtraTurnig.STACK ??? - updated to match pcgen srd original
CHOOSE:Exotic :- CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Exotic
CHOOSE:Blah|1 := CHOOSE:Blah
PRELEVEL:x := PRELEVEL:MIN=x
PREVARLT:CL=Shaaryan Hunter,6 := PRECLASSLEVELMAX:1,Shaaryan Hunter=5
PREVARGTEQ:CL=Shaaryan Hunter,6 := PRECLASS:1,Shaaryan Hunter=6

AUTO.SHIELDPROF|TYPE := AUTO.SHIELDPROF|SHIELDTYPE
CHOOSE:Martial := CHOOSE:PROFICIENCY|WEAPON|UNIQUE|TYPE=Martial
CHOOSE:SKILLSNAMED|blah|1 :- CHOOSE:SKILLSNAMED|blah

---------------------------------------------
feats_hidden file
ADD:FEAT(blah)|x :- ADD:FEAT|x|blah
SPELL:Blah|x|Innate := SPELLS:Innate|TIMES=x|Blah
SPELLS:Innate|CASTERLEVEL=max(classlevel("Mage"),1)|Blah
CHOOSE:NUMCHOICES=x| := CHOOSE:x|
**********************************************************************************
TODO Favoured Enemy / Favoured Bonus - all disabled, seems style is quite different
**********************************************************************************
Rogue Bonus -
CHOOSE:SKILLS|3+INT := SELECT:3+INT CHOOSE:SKILLS
=====================================

skills file
changed all to .mod
note - we only really want the descriptions, not the mechanics..
PREMOVE:Blah := PREMOVE:1,Blah
CHOOSE:Language(Spoken) :- CHOOSE:LANGUAGE|Spoken

SA: := SAB:
AUTO.ARMORPROF|TYPE := AUTO.ARMORPROF|ARMORTYPE

=====================================
updates to dieties file
Tag Name: PREALIGN:x,x
Variables Used (x):LG,LN,LE,NG,TN,NE,CG,CN,CE,Deity (Alignment abbreviation).
Variables Used (x):0,1,2,3,4,5,6,7,8,10 (Alignment array number).
LG,LN,LE,NG,TN,NE,CG,CN,CE, Deity
0, 1, 2, 3, 4, 5, 6, 7, 8, 10

%s/ [ ]*FOLLOWERALIGN:147/|PREALIGN:LN,TN,CN /
%s/ [ ]*FOLLOWERALIGN:13457/|PREALIGN:LN,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:258/|PREALIGN:LE,NE,CE /
%s/ [ ]*FOLLOWERALIGN:012/|PREALIGN:LG,LN,LE /
%s/ [ ]*FOLLOWERALIGN:125/|PREALIGN:LN,LE,NE /
%s/ [ ]*FOLLOWERALIGN:036/|PREALIGN:LG,NG,CG /
%s/ [ ]*FOLLOWERALIGN:013/|PREALIGN:LG,LN,NG /
%s/ [ ]*FOLLOWERALIGN:578 /|PREALIGN:NE,CN,CE /
%s/ [ ]*FOLLOWERALIGN:678 /|PREALIGN:CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:367 /|PREALIGN:NG,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345678 /|PREALIGN:LG,LN,LE,NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:013467 /|PREALIGN:LG,LN,NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:012345 /|PREALIGN:LG,LN,LE,NG,TN,NE /
%s/ [ ]*FOLLOWERALIGN:3467 /|PREALIGN:NG,TN,CG,CN /
%s/ [ ]*FOLLOWERALIGN:345678 /|PREALIGN:NG,TN,NE,CG,CN,CE /
%s/ [ ]*FOLLOWERALIGN:0123457 /|PREALIGN:LG,LN,LE,NG,TN,NE,CN /
%s/ [ ]*FOLLOWERALIGN:01236 /|PREALIGN:LG,LN,LE,NG,CG /
%s/ [ ]*FOLLOWERALIGN:2458 /|PREALIGN:LE,TN,NE,CE /
%s/ [ ]*FOLLOWERALIGN:0346 /|PREALIGN:LG,NG,TN,CG /
%s/ [ ]*FOLLOWERALIGN:4678 /|PREALIGN:TN,CG,CN,CE /

PREVARxx| becomes PREVARxx:Var,Value
--------------
%s/|PREDEFAULTMONSTER:Y//g
%s/MFEAT/FEAT/g

# note - need BOTH of the following, first one splits, second one cleans
%s/HITDICE:[0-9]*,/HD:,&HITDICE:\tHITDIE:/
%s/,HITDICE://g
or just remove it completely... %s/HITDICE:[0-9]*,[0-9]*//g
>>>No Longer using HITDICE, please remove and just use MONSTERCLASS
=====================================
SPELL: becomes SPELLS:Innate|TIMES=x|CASTERLEVEL=x|SpellName1,DC|SpellName2,DC

=====================================
Typically replace 'Heavy blah' with 'blah (Heavy)' etc.
=====================================
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_enhancing.lst
NOTE D:\utils\PCGen\PCGen5164\data\d20ogl\srd35\basics\rsrd_equipmods_base.lst

%s/Willpower/Will/g
%s/ARMR_MWORK/MWORKA/g
%s/ARMR_PLUS_2/PLUS2A/g
%s/ARMR_STEEL/STEEL/g
%s/ARMR_PLUS_3/PLUS3W/g
%s/ARMR_PLUS_1/PLUS1W/g
%s/SHLD_MWORK/MWORKS/g
%s/SHLD_STEEL/STEEL/g
%s/SHLD_WOOD/WOOD/g
%s/SHLD_PLUS_1/PLUS1S/g
%s/SHLD_PLUS_2/PLUS2S/g
%s/WEAP_PLUS_1/PLUS1W/g
%s/WEAP_PLUS_2/PLUS2W/g
%s/WEAP_PLUS_3/PLUS3W/g
%s/WEAP_PLUS_4/PLUS4W/g
%s/WEAP_PLUS_5/PLUS5W/g
%s/WEAP_STEEL/STEEL/g

%s/WEAP_MWORK/MWORKW/g
=====================================
FRCS/ue_feats.lst - Ice Troll Berserker should modify the rage special ability for natural armor...

=====================================
if you use linux, or have 'cygwin' installed under windows, you can run a bash script to do some extra conversions - note that some of this may be unnecessary as PrettyLst may fix it)

<<--start of file
# SLong and SShort are what we *want* to have finally.
# ALong, AShort and BShort are variations of this (common typos!) that appear initially
# that we want to replace

#################
# save to above commented out as version history once done
SLong="Players Guide to Faerun"
SShort="pgtfae"

ALong="Players Guide to Faerun"
ALong="players guide to faerun"
AShort="pgtfae"
BShort="PGTFAE"

Files=$( ls *.lst)
echo This script indicates the file name, and the first SOURCE entry noted therein as stdout, to allow verification of correct Sed replacement values

for File in ${Files}
do
echo ${File}
grep SOURCE ${File} |head -3 |uniq
printf "SOURCELONG:${SLong}\nSOURCESHORT:${SShort}\n" >a
printf "#Converted by DG $(date +%d/%m/%y)\n\n" >>a

# want to replace characters 93 & 94 (special quotes)
# but cant get sed to recognise them...
# these appear as black squares in vim..
# have to do manually in vim..
#
egrep -v "^SOURCE|^# CVS|#Converted by" $File |\
sed -e 's/Willpower/Will/g' \
-e 's/ARMR_MWORK/MWORKA/g' \
-e 's/AMMO_MWORK/MWORKA/g' \
-e 's/ARMRMW/MWORKA/g' \
-e 's/ARMR_PLUS_1/PLUS1A/g' \
-e 's/ARMR_PLUS_2/PLUS2A/g' \
-e 's/ARMR_PLUS_3/PLUS3A/g' \
-e 's/ARMR_PLUS_4/PLUS4A/g' \
-e 's/ARMR_PLUS_5/PLUS5A/g' \
-e 's/SHLD_MWORK/MWORKA/g' \
-e 's/SHLD_STEEL/STEEL/g' \
-e 's/SHLD_DARKWOOD/DARK/g' \
-e 's/ARMOR_SPIKE_BASH/SPOKE_SB/g' \
-e 's/ARMOR_SPIKE/SPIKE_S/g' \
-e 's/ARMR_STEEL/STEEL/g' \
-e 's/SHLD_WOOD/WOOD/g' \
-e 's/SHLD_PLUS_1/PLUS1S/g' \
-e 's/SHLD_PLUS_2/PLUS2S/g' \
-e 's/SHLD_PLUS_3/PLUS3S/g' \
-e 's/SHLD_PLUS_4/PLUS4S/g' \
-e 's/SHLD_PLUS_5/PLUS5S/g' \
-e 's/WEAP_PLUS_1/PLUS1W/g' \
-e 's/WEAP_PLUS_2/PLUS2W/g' \
-e 's/WEAP_PLUS_3/PLUS3W/g' \
-e 's/WEAP_PLUS_4/PLUS4W/g' \
-e 's/WEAP_PLUS_5/PLUS5W/g' \
-e 's/AMMO_PLUS_1/PLUS1W/g' \
-e 's/AMMO_PLUS_2/PLUS2W/g' \
-e 's/AMMO_PLUS_3/PLUS3W/g' \
-e 's/AMMO_PLUS_4/PLUS4W/g' \
-e 's/AMMO_PLUS_5/PLUS5W/g' \
-e 's/WEAP_BANE/BANE_M/g' \
-e 's/WEAP_STEEL/STEEL/g' \
-e 's/WEAP_VORPAL/VORPAL/g' \
-e 's/WEAP_ALCH_SILVR/ALCHM/g' \
-e 's/WEAP_ALCH_SLVR/ALCHM/g' \
-e 's/WEAP_AXIOMATIC/LAW_M/g' \
-e 's/WEAP_HOLY/HOLY_M/g' \
-e 's/ARMR_DRAGONHIDE/DRACO/g' \
-e 's/AMMO_ALCH_SLVR/ALCHM/g' \
-e 's/AMMO_COLD_IRON/C_IRON/g' \
-e 's/.WEAP_WOOD//g' \
-e 's/AMMO_ALCH_SILVR/ALCHM/g' \
-e 's/MWWEAPON/MWORKW/g' \
-e 's/WEAPMW/MWORKW/g' \
-e 's/WEAP_MWORK/MWORKW/g' \
-e 's/|PREDEFAULTMONSTER:Y//g' \
-e 's/MFEAT/FEAT/g' \
-e 's/HITDICE:[0-9]*,[0-9]*//g' \
-e"s/[|]SOURCELONG:${SLong}//" \
-e"s/[|]SOURCESHORT:${SShort}//" \
-e"s/[|]SOURCESHORT:${AShort}//" \
-e"s/[|]SOURCESHORT:${BShort}//" \
-e's/|SOURCEPAGE/SOURCEPAGE/' \
-e's/[|]SOURCELONG:${ALong}//' \
-e's/SOURCEPAGE/ SOURCEPAGE/' \
-e's/|SOURCE/\tSOURCE/' >>a
# that's a 'tab' two lines up, check when copying
mv a ${File}
done

<<--end of file-->>

Copy that to a file (remove the <<-- -->> lines) and then execute it, with something like:
cat SedCommands.txt |bash

=====================================
other manual changes:

WEAPONPROF:blah to :
BONUS:WEAPONPROF:blah
AUTO:WEAPONPROF|Longsword|Rapier|

BONUS:ToHIT|blah to BONUS:COMBAT:TOHIT|blah

ADD:FEAT|(blah) ADD:FEAT|(blah) to ADD:FEAT|2|blah,blah

Note that LANGBONUS (and potentially others?) take pipe (|) separators in one file but comma separators in others.

Further note that there are various typo's, particularly in 'DEFINE' variables.

Further notes on CMP to RSRD

2012-02-24T23:21:46Z

FerretDave:

Further Notes on CMP to RSRD Migration, part2

2012-02-24T23:16:48Z

FerretDave: Further CMP to RSRD conversion suggestions

Further notes on CMP to RSRD

2012-02-24T23:09:33Z

FerretDave:

Further notes on CMP to RSRD

2012-02-24T23:08:25Z

FerretDave: Random suggestions for CMP to RSRD conversion

Updating Homebrew Sets

2012-02-24T22:39:24Z

FerretDave: Updated PrettyLst command line params and methodology

{| align="right"
| __TOC__
|}

=Introduction=
This section is for updating older homebrew LST files to use the current standards. This is a work in progress. Any questions ask on the PCGen Yahoo Group.

==PrettyLST==

* First off we'll need [http://sourceforge.net/projects/pcgen/files/PrettyLst/v%201.39%20build%208180/prettylst_1-39_build-8180.zip/download PrettyLST] for earlier versions of PCGen

* Next, to run PrettyLST you'll need [https://www.activestate.com/activeperl/downloads/ ActivePerl].

* You will want to run PrettyLST with the Conversion Flag turned on to bring your sets up to 5.12 standards. Note this is not a perfect conversion, you will need to check your materials against any errors PrettyLST outputs.

It's a good idea to be methodical over this, and convert a single set at a time, otherwise the number of errors and warnings you'll have to get through may well become overwhelming.
Keep track of what you have converted.

you'll want to run PrettyLst with a command line such as:

perl prettylst.pl -i=d:\pcgen_convert\input -o=d:\pcgen_convert\intermediate -gamemode=35e -systempath D:\utils\PCGen\PCGen5120\system -e=error.txt -convert pcgen512

That '-convert pcgen512' is the flag to actually perform the conversion (otherwise its just reformatting the field order and indentation).

-i specifies the directory your old data set is in currently (note that here I've setup specific directories completely outside of my 'normal' dataset directory, so I don't risk messing up any 'live' sets.

-o indicates the output directory (I use an 'intermediate' directory, which will be used as the input for the next script (Baraks) below).

-gamemode=35e specifies the gamemode we're converting, you can leave this off, and prettylst will determine what you need, though I find migrating CMP datasets to 35e means I can make use of many other PCGen enhancements and get a better experience.

-systempath is a path to the installed PCGen 5.12.0, I'm not totally sure this is needed actually, but it cant hurt :-)

-e defines where the error output is going to be written.

I suggest you put the above into a batch file (RunConvert1.bat) to make it easier to run under windows.

Run the batch file, read the error messages, make any updates to the sources in the *input* directory, and re-run the batch file, repeat until either A) you have no more errors, or B) (more likely) you get fed up trying to fix them :-)
There are numerous warnings you can (probably) ignore (further options to prettylst reduce warning levels), and many that are just plain difficult to resolve at this stage - further steps below may fix them, or it may be cross references into other sources that you havent converted yet...

NOTE - if you do migrate CMP to RSRD (I personally recommend this, opinions may differ) many things (races, classes, spells, equipment...) are easier if they .MOD an appropriate (standard PCGen) 3.5 (or 3e!) dataset.

[[Further notes on CMP to RSRD]]

==5.12.x-->5.14.x==

For 5.12 to 5.14 you'll want to use [http://tech.groups.yahoo.com/group/PCGenListFileHelp/files/Misc/5.12%20to%205.14%20Conversion_v085.zip Barak's Script]

Again you'll need perl, see above. You may also need to jon the PCGenLiSTFileHelp group to access the file. I put the script with PrettyLST.

==5.14.x-->5.16.x==

5.16.x and beyond has a Converter included with PCGen. That Version of PCGen will update any files from the previous version. So the 5.16.x converter will bring 5.14.x files forward to 5.16.x standards.

Use the 5.16 Converter to bring 5.14 sets forward.

NOTE: The Converter will bring the previous cycle forward, do not use 6.0 to bring 5.14 forward, use 5.16 to do that.

==5.16.x-->6.0.x==
Use the 6.0 PCGen Converter

==Massive Changes that WILL affect Homebrew Users==
=Starting 5.16.4 and 5.17.4=
All the Armor BONUS TYPES got a bit of a Change. This WILL affect any homebrew sets that use any PCGen released core sets.

The Following needs to be done to follow the standards:

* Races that grant Natural Armor need to use this format:
BONUS:COMBAT|AC|x|TYPE=NaturalArmor
this replaces the old format of BONUS:COMBAT|AC|x|TYPE=NaturalArmor.REPLACE

* Anything that improves Natural Armor not by enhancement needs to use this format:
BONUS:COMBAT|AC|x|TYPE=NaturalArmor.STACK
this replaces the old format of BONUS:COMBAT|AC|x|TYPE=NaturalArmor.REPLACE
BONUS:COMBAT|AC|x|TYPE=NaturalArmorEnhancement
should be used for any Natural Armor Enhancement

The same applies for Armor.REPLACE and Shield.REPLACE; these both become Armor and Shield respectively. If there is an enhancement you wish to and, just append 'Enhancement' to the Bonus type 'ArmorEnhancement', 'ShieldEnhancement'.

* For Armor and Shield:
BONUS:COMBAT|AC|x|TYPE=ArmorEnhancement
This replaces '''BONUS:COMBAT|AC|x|TYPE=Armor.REPLACE'''

BONUS:COMBAT|AC|x|TYPE:ShieldEnhancement
This replaces '''BONUS:COMBAT|AC|x|TYPE=Shield.REPLACE'''

* 3rd Edition has a slight variation. We don't use 'Shield' or 'ShieldEnhancement' instead we use:
ArmorShield
For Armor Bonus derived from the Shield
ArmorShieldEnhancement
For the Armor Bonus granted from the Shield Enhancement

This was done to make the stacking rules work more uniformly, and avoid overlap stacking where it shouldn't occur.

Spell List Suggested Improvements

2012-02-13T00:27:15Z

FerretDave: added comment on BENEFIT (JIRA'd)

===Spell List Introduction===
Overall Aim is to reduce the page count for spell lists, whilst still keeping all the relevant information clearly visible.

For low level characters, its not a massive headache, for high level (especially clerics), it can get excessive. 28 pages of spells is the current record (no prizes for beating this though).

[I would need to actually count, but I think it was 28 it could have been more ;) [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

For users of the [R]SRD, the spell descriptions are pretty short - a single line usually, whereas for homebrew and Pathfinder, there is often several lines of text.

NOTE - while FEATS use a short DESC and have an option (only via homebrew I think) to use a far longer BENEFIT field, I don't believe that spells have this functionality.
To gain from this, we'd need a code update to output either the DESC or BENEFIT for Spells (as a seperate option than for feats), and to actually get anything of value, LST editors would have to code up seperate BENEFIT for each spell with a lengthier description. Is that of value?

* Homebrewers might think so, but I doubt it would find much use in the official release sets, so be a low priority feature request to be honest. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
JIRA raised to allow BENEFIT to be used on SPELLS as well as Feats, gives homebrewers the option to implement themselves.

==Variants==

Consider variants:
A low level bard with just a handful of spells - could afford to have a full text copy of the book source
A medium level wizard with a few dozen spells - would want a 2 or 3 line description for most spells
A high level cleric with far too many spells to mention - may just want a one line description for each spell.
Is there value in the CODE working with possibly three different levels of description (DESC-SHORT, DESC-MEDIUM and DESC-LONG/BENEFIT)? It would be down to homebrew and lst editors to actually take advantage of this however.

This may be easier solved by merely providing an alternative 'condensed' spell list for those with too many spells, that restricts the output of the DESC to a single line, allowing many spells to be output on one page.

----------------------------
===Comparison of Layouts===
Current default for 5.17.10 and earlier versions till 5.17.1 for comparison
(Could do with a screen shot here)

LEVEL 0
Name Save Information Time Duration Range Comp. Source
oooooAcid Splash 1 standard action Instantaneous Close (30 ft.) V, S PHB35e: P.196
School: Conjuration (Creation) [Acid] SR: No Target: One missile of acid Caster Level: 3
Effect: Orb deals 1d3 acid damage.

Before than, Effect was on the Second Line and a lengthy description would be boxed to waste a lot of space. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

This is 3+ rows - 2 headers and then the description

Drews current 5.17.10 new version:
LEVEL 0
Name School Time Duration Range Caster Level Source
oooooAcid Splash Conjuration (Creation) [Acid] Standard Action Instantaneous Close (50 ft.) Caster Level: 10 PHB: p.196
Target: One missile of acid; EFFECT: [SR: No] You fire a small orb of acid at the target. You must succeed on a ranged touch attack to hit your target. The orb deals 1d3 points of acid damage. [V,S]

This is 2+ lines, one header and an extended description, with some fields moved from the header onto the desc line.

=== Requested Updates ===
Updates to the 'standard' spell sheet:

For each LEVEL heading 'LEVEL x', add:
* Default casterlevel
* Concentration check
* Spells (of this level) castable per day

For each SPELL entry
* position the [V,S,M] components field (in bold) as a prefix to the description, to aid in searching for specific types (non-somatic spells when silenced for example)
** Done [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Spell Resistance - as Suffix or to desc? But not *between* 'effect:' and the actual desc.
DC - put as suffix to desc? or as prefix? Retain on header line?
Target - suffix or prefix to desc? retain on header line? bold or italic for string'target:'

Placing the Target Text in the Comps/Source area doesn't work out: [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Screen shot==

[[File:Target not good.JPG|400px|thumb|center|Target not Good]]

[[File:Long Spell Name.JPG|400px|thumb|center|Long Spell Name]]

[[File:Spell Level Header.JPG|400px|thumb|center|NEW SPELL LEVEL HEADER]]

[[File:Caster Level.JPG|400px|thumb|center|Caster Level shown after spell NAME if different from base]]

[[File:Domain Spell Display.JPG|400px|thumb|center|Domain Spell Display, Fixed PCGen Version, CR added to Footer]]

==More Tweaks==
* Source - put as (right justified) suffix on last line of desc, retain on header line, or - if feasible - rotate the text 90 degrees and have it expand down the very far right hand side as a 'narrow' column across both header and desc lines? I.e
Source display suggestion:

header blah blah P 1 
effect blah blah H 9 
blah blah blah b B 6 

(with the 'PHB 196' characters actually rotated 90', to be read on by tilting your head to one side
** Neither option is feasible within the row, I can't do it as inline text, it needs it's own block to do alignment styles. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** I can't think of any easy method to 1) implement it; and 2) think it would expand beyond the confines defeating the condensed space request. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Caster level - add as bracketed value after the spell name (in the name field) but only if it differs from the default (which is shown on the LEVEL header row). Or move into Desc line (prefix or suffix?) Remove string 'Class level' from spell line at least.
** Might be tricky, I have to wrap my head around how to accomplish that, LST code it'd be easy, if value neq to base, then display. In xslt it's probably '<if:test ??? &neq; "casterlevel"> or some such, will need to consult for that [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** DONE -- [[User:LegacyKing|LegacyKing]] 18:23, 11 February 2012 (EST)

* Remove the text 'Effect:' either completely(?) or replace with 'Desc:' ?
** I suppose that is an option. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Prevent spells from wrapping from one page to the next, if it wont fit, force it to start on a new page
** Need to consult for assistance in how to enforce that. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Grey highlight - rather than alternate grey/white background for each spell, just use the highlight on each header row, making the desc clearer to read?
** Same as above, need to consult a guru. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Domain spells - indicate in italic rather than with an asterisk? Or increase size of asterisk?
** Increased Size of the Asterisk - no screen shot yet [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Latest Screen Shot of Current Work==
[[File:Rev1.JPG]]

Further comments for above screenshot:
Comps - is there benefit in including the actual word 'COMPS:' or just use the familiar bracketed [V,S,M] style ?
Caster level appears to have a very wide column alloted, it only needs to be 2 characters wide?
How about putting the 'school' into the same field as the spell name (not in bold), and make the name field (slightly) wider - free's up some space to add target back onto header line?

Thinking like: 
oooooAcid Splash (Conjuration (Creation) [Acid]) | 1 standard action | Instantaneous | Close (30 ft.) | Target: One missile of acid |CL:3 |PHB35e: P.196 
[V,S] | Effect: Orb deals 1d3 acid damage. | [SR:No] 

(adding pipe symbol to show field seperation for clarity only)
--[[User:FerretDave|FerretDave]] 21:03, 10 February 2012 (EST)

You're using a spell with a short target, I'm not pulling out the lengthy target examples. Target in the old rev I believe takes up three columns. You'd end up wasting space if we placed it back on the 1st line. I'm not crazy about combining the spell name with school, in that case there is a special block and I'd rather leave that be. I haven't seen any spell name in the usual sources that would require additional space. 22:32, 10 February 2012 (EST)

The extra width was to account for school being included in the same field, working on the basis that 'Name+School' in one field would not need as much space as 'Name'&'School' as two seperate fields.
We perhaps need to have an example of a spell that is long (in each field) and another example that is short, so we can see how different formats affect each one, from the screenshot there are only really 'short' target fields.
--[[User:FerretDave|FerretDave]] 00:32, 11 February 2012 (EST)

Size of columns - has this been determined statistically, or by guesswork? Does anyone have any stats of the min/average/max size of each spell field, across a sample of the most common lst files ?
--[[User:FerretDave|FerretDave]] 21:52, 10 February 2012 (EST)

That was determined by someone else, those can be edited. -- 22:32, 10 February 2012 (EST)~

* alter the number of checkboxes to match the 'usual' number/day for that spell level
See discussion: [http://tech.groups.yahoo.com/group/PCGenListFileHelp/post?act=reply&messageNum=22143]

Spell List Suggested Improvements

2012-02-12T23:24:36Z

FerretDave: added variable checkboxes request

===Spell List Introduction===
Overall Aim is to reduce the page count for spell lists, whilst still keeping all the relevant information clearly visible.

For low level characters, its not a massive headache, for high level (especially clerics), it can get excessive. 28 pages of spells is the current record (no prizes for beating this though).

[I would need to actually count, but I think it was 28 it could have been more ;) [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

For users of the [R]SRD, the spell descriptions are pretty short - a single line usually, whereas for homebrew and Pathfinder, there is often several lines of text.

NOTE - while FEATS use a short DESC and have an option (only via homebrew I think) to use a far longer BENEFIT field, I don't believe that spells have this functionality.
To gain from this, we'd need a code update to output either the DESC or BENEFIT for Spells (as a seperate option than for feats), and to actually get anything of value, LST editors would have to code up seperate BENEFIT for each spell with a lengthier description. Is that of value?

* Homebrewers might think so, but I doubt it would find much use in the official release sets, so be a low priority feature request to be honest. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Variants==

Consider variants:
A low level bard with just a handful of spells - could afford to have a full text copy of the book source
A medium level wizard with a few dozen spells - would want a 2 or 3 line description for most spells
A high level cleric with far too many spells to mention - may just want a one line description for each spell.
Is there value in the CODE working with possibly three different levels of description (DESC-SHORT, DESC-MEDIUM and DESC-LONG/BENEFIT)? It would be down to homebrew and lst editors to actually take advantage of this however.

This may be easier solved by merely providing an alternative 'condensed' spell list for those with too many spells, that restricts the output of the DESC to a single line, allowing many spells to be output on one page.

----------------------------
===Comparison of Layouts===
Current default for 5.17.10 and earlier versions till 5.17.1 for comparison
(Could do with a screen shot here)

LEVEL 0
Name Save Information Time Duration Range Comp. Source
oooooAcid Splash 1 standard action Instantaneous Close (30 ft.) V, S PHB35e: P.196
School: Conjuration (Creation) [Acid] SR: No Target: One missile of acid Caster Level: 3
Effect: Orb deals 1d3 acid damage.

Before than, Effect was on the Second Line and a lengthy description would be boxed to waste a lot of space. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

This is 3+ rows - 2 headers and then the description

Drews current 5.17.10 new version:
LEVEL 0
Name School Time Duration Range Caster Level Source
oooooAcid Splash Conjuration (Creation) [Acid] Standard Action Instantaneous Close (50 ft.) Caster Level: 10 PHB: p.196
Target: One missile of acid; EFFECT: [SR: No] You fire a small orb of acid at the target. You must succeed on a ranged touch attack to hit your target. The orb deals 1d3 points of acid damage. [V,S]

This is 2+ lines, one header and an extended description, with some fields moved from the header onto the desc line.

=== Requested Updates ===
Updates to the 'standard' spell sheet:

For each LEVEL heading 'LEVEL x', add:
* Default casterlevel
* Concentration check
* Spells (of this level) castable per day

For each SPELL entry
* position the [V,S,M] components field (in bold) as a prefix to the description, to aid in searching for specific types (non-somatic spells when silenced for example)
** Done [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Spell Resistance - as Suffix or to desc? But not *between* 'effect:' and the actual desc.
DC - put as suffix to desc? or as prefix? Retain on header line?
Target - suffix or prefix to desc? retain on header line? bold or italic for string'target:'

Placing the Target Text in the Comps/Source area doesn't work out: [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Screen shot==

[[File:Target not good.JPG|400px|thumb|center|Target not Good]]

[[File:Long Spell Name.JPG|400px|thumb|center|Long Spell Name]]

[[File:Spell Level Header.JPG|400px|thumb|center|NEW SPELL LEVEL HEADER]]

[[File:Caster Level.JPG|400px|thumb|center|Caster Level shown after spell NAME if different from base]]

[[File:Domain Spell Display.JPG|400px|thumb|center|Domain Spell Display, Fixed PCGen Version, CR added to Footer]]

==More Tweaks==
* Source - put as (right justified) suffix on last line of desc, retain on header line, or - if feasible - rotate the text 90 degrees and have it expand down the very far right hand side as a 'narrow' column across both header and desc lines? I.e
Source display suggestion:

header blah blah P 1 
effect blah blah H 9 
blah blah blah b B 6 

(with the 'PHB 196' characters actually rotated 90', to be read on by tilting your head to one side
** Neither option is feasible within the row, I can't do it as inline text, it needs it's own block to do alignment styles. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** I can't think of any easy method to 1) implement it; and 2) think it would expand beyond the confines defeating the condensed space request. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Caster level - add as bracketed value after the spell name (in the name field) but only if it differs from the default (which is shown on the LEVEL header row). Or move into Desc line (prefix or suffix?) Remove string 'Class level' from spell line at least.
** Might be tricky, I have to wrap my head around how to accomplish that, LST code it'd be easy, if value neq to base, then display. In xslt it's probably '<if:test ??? &neq; "casterlevel"> or some such, will need to consult for that [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** DONE -- [[User:LegacyKing|LegacyKing]] 18:23, 11 February 2012 (EST)

* Remove the text 'Effect:' either completely(?) or replace with 'Desc:' ?
** I suppose that is an option. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Prevent spells from wrapping from one page to the next, if it wont fit, force it to start on a new page
** Need to consult for assistance in how to enforce that. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Grey highlight - rather than alternate grey/white background for each spell, just use the highlight on each header row, making the desc clearer to read?
** Same as above, need to consult a guru. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Domain spells - indicate in italic rather than with an asterisk? Or increase size of asterisk?
** Increased Size of the Asterisk - no screen shot yet [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Latest Screen Shot of Current Work==
[[File:Rev1.JPG]]

Further comments for above screenshot:
Comps - is there benefit in including the actual word 'COMPS:' or just use the familiar bracketed [V,S,M] style ?
Caster level appears to have a very wide column alloted, it only needs to be 2 characters wide?
How about putting the 'school' into the same field as the spell name (not in bold), and make the name field (slightly) wider - free's up some space to add target back onto header line?

Thinking like: 
oooooAcid Splash (Conjuration (Creation) [Acid]) | 1 standard action | Instantaneous | Close (30 ft.) | Target: One missile of acid |CL:3 |PHB35e: P.196 
[V,S] | Effect: Orb deals 1d3 acid damage. | [SR:No] 

(adding pipe symbol to show field seperation for clarity only)
--[[User:FerretDave|FerretDave]] 21:03, 10 February 2012 (EST)

You're using a spell with a short target, I'm not pulling out the lengthy target examples. Target in the old rev I believe takes up three columns. You'd end up wasting space if we placed it back on the 1st line. I'm not crazy about combining the spell name with school, in that case there is a special block and I'd rather leave that be. I haven't seen any spell name in the usual sources that would require additional space. 22:32, 10 February 2012 (EST)

The extra width was to account for school being included in the same field, working on the basis that 'Name+School' in one field would not need as much space as 'Name'&'School' as two seperate fields.
We perhaps need to have an example of a spell that is long (in each field) and another example that is short, so we can see how different formats affect each one, from the screenshot there are only really 'short' target fields.
--[[User:FerretDave|FerretDave]] 00:32, 11 February 2012 (EST)

Size of columns - has this been determined statistically, or by guesswork? Does anyone have any stats of the min/average/max size of each spell field, across a sample of the most common lst files ?
--[[User:FerretDave|FerretDave]] 21:52, 10 February 2012 (EST)

That was determined by someone else, those can be edited. -- 22:32, 10 February 2012 (EST)~

* alter the number of checkboxes to match the 'usual' number/day for that spell level
See discussion: [http://tech.groups.yahoo.com/group/PCGenListFileHelp/post?act=reply&messageNum=22143]

Talk:Spell List Suggested Improvements

2012-02-11T18:38:20Z

FerretDave: Comments on latest screenshots

Several excellent points have been made, here is the state of things:
* Righ-Justified for Source | Cannot Accomplish
* Altering the Text to Downward Angle | Not going to attempt at this time
* Caster Level Display only if different from base | Requires Consult

Cheers,
[[User:LegacyKing|LegacyKing]] 20:21, 10 February 2012 (EST)

* Concentration Display only if different from base | as per caster level? Also requires consult

Screenshot comments:
http://wiki.pcgen.org/images/1/1e/Target_not_good.JPG
Those targets do wrap, but we have a lot of whitespace elsewhere, a resizing of other columns may fix this.
It would be beneficial to get some stats on average column size (any volunteers?)

http://wiki.pcgen.org/images/6/68/Long_Spell_Name.JPG
Again, column size stats may help, we're never going to eliminate every field from *ever* wrapping, but there's a compromise somewhere
(some calculation perhaps - over all spells for a high level cleric, what's the total line count for the display, does it increase or decrease if we change the column size for each field?)

If 90% of spell names (or target fields, etc) don't wrap, then the size is good, and by reducing column sizes to fit that 90%, then can we afford to move target back onto the header?

http://wiki.pcgen.org/images/7/71/Spell_Level_Header.JPG
Definitely like this, can remove the '10' (Casterlevel entry) from the header line.

http://wiki.pcgen.org/images/0/0d/Caster_Level.JPG
This display of CL if it differs from the default works for me, again, with CL suffixed on the spell name, we don't need the extra column in the header.

http://wiki.pcgen.org/File:Domain_Spell_Display.JPG
There are *two* asterisks?

User:FerretDave

2012-02-10T15:22:51Z

FerretDave: Created page with "Dave or Ferret, I answer to both :-) IT Consultant for a big communications company, have been running UNIX systems for 18 years. UNIX shell scripting, C Code, SQL (Oracle & MyS..."

Dave or Ferret, I answer to both :-)

IT Consultant for a big communications company, have been running UNIX systems for 18 years.
UNIX shell scripting, C Code, SQL (Oracle & MySQL) and at long last learning Java.

Mostly run DnD 3.5, but also Cthulhu, Cyberpunk, Traveller, Paranoia...

Spell List Suggested Improvements

2012-02-10T13:32:16Z

FerretDave:

===Spell List Introduction===
Overall Aim is to reduce the page count for spell lists, whilst still keeping all the relevant information clearly visible.

For low level characters, its not a massive headache, for high level (especially clerics), it can get excessive. 28 pages of spells is the current record (no prizes for beating this though).

[I would need to actually count, but I think it was 28 it could have been more ;) [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

For users of the [R]SRD, the spell descriptions are pretty short - a single line usually, whereas for homebrew and Pathfinder, there is often several lines of text.

NOTE - while FEATS use a short DESC and have an option (only via homebrew I think) to use a far longer BENEFIT field, I don't believe that spells have this functionality.
To gain from this, we'd need a code update to output either the DESC or BENEFIT for Spells (as a seperate option than for feats), and to actually get anything of value, LST editors would have to code up seperate BENEFIT for each spell with a lengthier description. Is that of value?

* Homebrewers might think so, but I doubt it would find much use in the official release sets, so be a low priority feature request to be honest. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Variants==

Consider variants:
A low level bard with just a handful of spells - could afford to have a full text copy of the book source
A medium level wizard with a few dozen spells - would want a 2 or 3 line description for most spells
A high level cleric with far too many spells to mention - may just want a one line description for each spell.
Is there value in the CODE working with possibly three different levels of description (DESC-SHORT, DESC-MEDIUM and DESC-LONG/BENEFIT)? It would be down to homebrew and lst editors to actually take advantage of this however.

This may be easier solved by merely providing an alternative 'condensed' spell list for those with too many spells, that restricts the output of the DESC to a single line, allowing many spells to be output on one page.

----------------------------
===Comparison of Layouts===
Current default for 5.17.10 and earlier versions till 5.17.1 for comparison
(Could do with a screen shot here)

LEVEL 0
Name Save Information Time Duration Range Comp. Source
oooooAcid Splash 1 standard action Instantaneous Close (30 ft.) V, S PHB35e: P.196
School: Conjuration (Creation) [Acid] SR: No Target: One missile of acid Caster Level: 3
Effect: Orb deals 1d3 acid damage.

Before than, Effect was on the Second Line and a lengthy description would be boxed to waste a lot of space. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

This is 3+ rows - 2 headers and then the description

Drews current 5.17.10 new version:
LEVEL 0
Name School Time Duration Range Caster Level Source
oooooAcid Splash Conjuration (Creation) [Acid] Standard Action Instantaneous Close (50 ft.) Caster Level: 10 PHB: p.196
Target: One missile of acid; EFFECT: [SR: No] You fire a small orb of acid at the target. You must succeed on a ranged touch attack to hit your target. The orb deals 1d3 points of acid damage. [V,S]

This is 2+ lines, one header and an extended description, with some fields moved from the header onto the desc line.

=== Requested Updates ===
Updates to the 'standard' spell sheet:

For each LEVEL heading 'LEVEL x', add:
* Default casterlevel
* Concentration check
* Spells (of this level) castable per day

For each SPELL entry
* position the [V,S,M] components field (in bold) as a prefix to the description, to aid in searching for specific types (non-somatic spells when silenced for example)
** Done [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Spell Resistance - as Suffix or to desc? But not *between* 'effect:' and the actual desc.
DC - put as suffix to desc? or as prefix? Retain on header line?
Target - suffix or prefix to desc? retain on header line? bold or italic for string'target:'

Placing the Target Text in the Comps/Source area doesn't work out: [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Screen shot==
[[File:Target not good.JPG]]

==More Tweaks==
Source - put as (right justified) suffix on last line of desc, retain on header line, or - if feasible - rotate the text 90 degrees and have it expand down the very far right hand side as a 'narrow' column across both header and desc lines? I.e
Source display suggestion:

header blah blah P 1 
effect blah blah H 9 
blah blah blah b B 6 

(with the 'PHB 196' characters actually rotated 90', to be read on by tilting your head to one side
** Neither option is feasible within the row, I can't do it as inline text, it needs it's own block to do alignment styles. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** I can't think of any easy method to 1) implement it; and 2) think it would expand beyond the confines defeating the condensed space request. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Caster level - add as bracketed value after the spell name (in the name field) but only if it differs from the default (which is shown on the LEVEL header row). Or move into Desc line (prefix or suffix?) Remove string 'Class level' from spell line at least.
** Might be tricky, I have to wrap my head around how to accomplish that, LST code it'd be easy, if value neq to base, then display. In xslt it's probably '<if:test ??? &neq; "casterlevel"> or some such, will need to consult for that [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Remove the text 'Effect:' either completely(?) or replace with 'Desc:' ?
** I suppose that is an option. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Prevent spells from wrapping from one page to the next, if it wont fit, force it to start on a new page
** Need to consult for assistance in how to enforce that. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Grey highlight - rather than alternate grey/white background for each spell, just use the highlight on each header row, making the desc clearer to read?
** Same as above, need to consult a guru. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Domain spells - indicate in italic rather than with an asterisk? Or increase size of asterisk?
** Increased Size of the Asterisk - no screen shot yet [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Latest Screen Shot of Current Work==
[[File:Rev1.JPG]]

Further comments for above screenshot:
Comps - is there benefit in including the actual word 'COMPS:' or just use the familiar bracketed [V,S,M] style ?
Caster level appears to have a very wide column alloted, it only needs to be 2 characters wide?
How about putting the 'school' into the same field as the spell name (not in bold), and make the name field (slightly) wider - free's up some space to add target back onto header line?

Thinking like: 
oooooAcid Splash (Conjuration (Creation) [Acid]) | 1 standard action | Instantaneous | Close (30 ft.) | Target: One missile of acid |CL:3 |PHB35e: P.196 
[V,S] | Effect: Orb deals 1d3 acid damage. | [SR:No] 

(adding pipe symbol to show field seperation for clarity only)
--[[User:FerretDave|FerretDave]] 21:03, 10 February 2012 (EST)

You're using a spell with a short target, I'm not pulling out the lengthy target examples. Target in the old rev I believe takes up three columns. You'd end up wasting space if we placed it back on the 1st line. I'm not crazy about combining the spell name with school, in that case there is a special block and I'd rather leave that be. I haven't seen any spell name in the usual sources that would require additional space. 22:32, 10 February 2012 (EST)

The extra width was to account for school being included in the same field, working on the basis that 'Name+School' in one field would not need as much space as 'Name'&'School' as two seperate fields.
We perhaps need to have an example of a spell that is long (in each field) and another example that is short, so we can see how different formats affect each one, from the screenshot there are only really 'short' target fields.
--[[User:FerretDave|FerretDave]] 00:32, 11 February 2012 (EST)

Size of columns - has this been determined statistically, or by guesswork? Does anyone have any stats of the min/average/max size of each spell field, across a sample of the most common lst files ?
--[[User:FerretDave|FerretDave]] 21:52, 10 February 2012 (EST)

That was determined by someone else, those can be edited. -- 22:32, 10 February 2012 (EST)~

Spell List Suggested Improvements

2012-02-10T10:52:05Z

FerretDave:

Overall Aim is to reduce the page count for spell lists, whilst still keeping all the relevant information clearly visible.

For low level characters, its not a massive headache, for high level (especially clerics), it can get excessive. 28 pages of spells is the current record (no prizes for beating this though).

[I would need to actually count, but I think it was 28 it could have been more ;) [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

For users of the [R]SRD, the spell descriptions are pretty short - a single line usually, whereas for homebrew and Pathfinder, there is often several lines of text.

NOTE - while FEATS use a short DESC and have an option (only via homebrew I think) to use a far longer BENEFIT field, I don't believe that spells have this functionality.
To gain from this, we'd need a code update to output either the DESC or BENEFIT for Spells (as a seperate option than for feats), and to actually get anything of value, LST editors would have to code up seperate BENEFIT for each spell with a lengthier description. Is that of value?

* Homebrewers might think so, but I doubt it would find much use in the official release sets, so be a low priority feature request to be honest. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

Consider variants:
A low level bard with just a handful of spells - could afford to have a full text copy of the book source
A medium level wizard with a few dozen spells - would want a 2 or 3 line description for most spells
A high level cleric with far too many spells to mention - may just want a one line description for each spell.
Is there value in the CODE working with possibly three different levels of description (DESC-SHORT, DESC-MEDIUM and DESC-LONG/BENEFIT)? It would be down to homebrew and lst editors to actually take advantage of this however.

This may be easier solved by merely providing an alternative 'condensed' spell list for those with too many spells, that restricts the output of the DESC to a single line, allowing many spells to be output on one page.

----------------------------

Current default for 5.17.10 and earlier versions till 5.17.1 for comparison
(Could do with a screen shot here)

LEVEL 0
Name Save Information Time Duration Range Comp. Source
oooooAcid Splash 1 standard action Instantaneous Close (30 ft.) V, S PHB35e: P.196
School: Conjuration (Creation) [Acid] SR: No Target: One missile of acid Caster Level: 3
Effect: Orb deals 1d3 acid damage.

Before than, Effect was on the Second Line and a lengthy description would be boxed to waste a lot of space. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

This is 3+ rows - 2 headers and then the description

Drews current 5.17.10 new version:
LEVEL 0
Name School Time Duration Range Caster Level Source
oooooAcid Splash Conjuration (Creation) [Acid] Standard Action Instantaneous Close (50 ft.) Caster Level: 10 PHB: p.196
Target: One missile of acid; EFFECT: [SR: No] You fire a small orb of acid at the target. You must succeed on a ranged touch attack to hit your target. The orb deals 1d3 points of acid damage. [V,S]

This is 2+ lines, one header and an extended description, with some fields moved from the header onto the desc line.

Updates to the 'standard' spell sheet:

For each LEVEL heading 'LEVEL x', add:
* Default casterlevel
* Concentration check
* Spells (of this level) castable per day

For each SPELL entry
* position the [V,S,M] components field (in bold) as a prefix to the description, to aid in searching for specific types (non-somatic spells when silenced for example)
** Done [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Spell Resistance - as Suffix or to desc? But not *between* 'effect:' and the actual desc.
DC - put as suffix to desc? or as prefix? Retain on header line?
Target - suffix or prefix to desc? retain on header line? bold or italic for string'target:'

Placing the Target Text in the Comps/Source area doesn't work out: [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

[[File:Target not good.JPG]]

Source - put as (right justified) suffix on last line of desc, retain on header line, or - if feasible - rotate the text 90 degrees and have it expand down the very far right hand side as a 'narrow' column across both header and desc lines? I.e
Source display suggestion:

header blah blah P 1 
effect blah blah H 9 
blah blah blah b B 6 

(with the 'PHB 196' characters actually rotated 90', to be read on by tilting your head to one side
** Neither option is feasible within the row, I can't do it as inline text, it needs it's own block to do alignment styles. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** I can't think of any easy method to 1) implement it; and 2) think it would expand beyond the confines defeating the condensed space request. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Caster level - add as bracketed value after the spell name (in the name field) but only if it differs from the default (which is shown on the LEVEL header row). Or move into Desc line (prefix or suffix?) Remove string 'Class level' from spell line at least.
** Might be tricky, I have to wrap my head around how to accomplish that, LST code it'd be easy, if value neq to base, then display. In xslt it's probably '<if:test ??? &neq; "casterlevel"> or some such, will need to consult for that [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Remove the text 'Effect:' either completely(?) or replace with 'Desc:' ?
** I suppose that is an option. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Prevent spells from wrapping from one page to the next, if it wont fit, force it to start on a new page
** Need to consult for assistance in how to enforce that. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Grey highlight - rather than alternate grey/white background for each spell, just use the highlight on each header row, making the desc clearer to read?
** Same as above, need to consult a guru. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Domain spells - indicate in italic rather than with an asterisk? Or increase size of asterisk?
** Increased Size of the Asterisk - no screen shot yet [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Latest Screen Shot of Current Work==
[[File:Rev1.JPG]]

Further comments for above screenshot:
Comps - is there benefit in including the actual word 'COMPS:' or just use the familiar bracketed [V,S,M] style ?
Caster level appears to have a very wide column alloted, it only needs to be 2 characters wide?
How about putting the 'school' into the same field as the spell name (not in bold), and make the name field (slightly) wider - free's up some space to add target back onto header line?

Thinking like: 
oooooAcid Splash (Conjuration (Creation) [Acid]) | 1 standard action | Instantaneous | Close (30 ft.) | Target: One missile of acid |CL:3 |PHB35e: P.196 
[V,S] | Effect: Orb deals 1d3 acid damage. | [SR:No] 

(adding pipe symbol to show field seperation for clarity only)

--[[User:FerretDave|FerretDave]] 21:03, 10 February 2012 (EST)

Size of columns - has this been determined statistically, or by guesswork? Does anyone have any stats of the min/average/max size of each spell field, across a sample of the most common lst files ?
--[[User:FerretDave|FerretDave]] 21:52, 10 February 2012 (EST)

Spell List Suggested Improvements

2012-02-10T10:24:26Z

FerretDave:

Overall Aim is to reduce the page count for spell lists, whilst still keeping all the relevant information clearly visible.

For low level characters, its not a massive headache, for high level (especially clerics), it can get excessive. 28 pages of spells is the current record (no prizes for beating this though).

[I would need to actually count, but I think it was 28 it could have been more ;) [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

For users of the [R]SRD, the spell descriptions are pretty short - a single line usually, whereas for homebrew and Pathfinder, there is often several lines of text.

NOTE - while FEATS use a short DESC and have an option (only via homebrew I think) to use a far longer BENEFIT field, I don't believe that spells have this functionality.
To gain from this, we'd need a code update to output either the DESC or BENEFIT for Spells (as a seperate option than for feats), and to actually get anything of value, LST editors would have to code up seperate BENEFIT for each spell with a lengthier description. Is that of value?

* Homebrewers might think so, but I doubt it would find much use in the official release sets, so be a low priority feature request to be honest. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

Consider variants:
A low level bard with just a handful of spells - could afford to have a full text copy of the book source
A medium level wizard with a few dozen spells - would want a 2 or 3 line description for most spells
A high level cleric with far too many spells to mention - may just want a one line description for each spell.
Is there value in the CODE working with possibly three different levels of description (DESC-SHORT, DESC-MEDIUM and DESC-LONG/BENEFIT)? It would be down to homebrew and lst editors to actually take advantage of this however.

This may be easier solved by merely providing an alternative 'condensed' spell list for those with too many spells, that restricts the output of the DESC to a single line, allowing many spells to be output on one page.

----------------------------

Current default for 5.17.10 and earlier versions till 5.17.1 for comparison
(Could do with a screen shot here)

LEVEL 0
Name Save Information Time Duration Range Comp. Source
oooooAcid Splash 1 standard action Instantaneous Close (30 ft.) V, S PHB35e: P.196
School: Conjuration (Creation) [Acid] SR: No Target: One missile of acid Caster Level: 3
Effect: Orb deals 1d3 acid damage.

Before than, Effect was on the Second Line and a lengthy description would be boxed to waste a lot of space. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

This is 3+ rows - 2 headers and then the description

Drews current 5.17.10 new version:
LEVEL 0
Name School Time Duration Range Caster Level Source
oooooAcid Splash Conjuration (Creation) [Acid] Standard Action Instantaneous Close (50 ft.) Caster Level: 10 PHB: p.196
Target: One missile of acid; EFFECT: [SR: No] You fire a small orb of acid at the target. You must succeed on a ranged touch attack to hit your target. The orb deals 1d3 points of acid damage. [V,S]

This is 2+ lines, one header and an extended description, with some fields moved from the header onto the desc line.

Updates to the 'standard' spell sheet:

For each LEVEL heading 'LEVEL x', add:
* Default casterlevel
* Concentration check
* Spells (of this level) castable per day

For each SPELL entry
* position the [V,S,M] components field (in bold) as a prefix to the description, to aid in searching for specific types (non-somatic spells when silenced for example)
** Done [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Spell Resistance - as Suffix or to desc? But not *between* 'effect:' and the actual desc.
DC - put as suffix to desc? or as prefix? Retain on header line?
Target - suffix or prefix to desc? retain on header line? bold or italic for string'target:'

Placing the Target Text in the Comps/Source area doesn't work out: [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

[[File:Target not good.JPG]]

Source - put as (right justified) suffix on last line of desc, retain on header line, or - if feasible - rotate the text 90 degrees and have it expand down the very far right hand side as a 'narrow' column across both header and desc lines? I.e
Source display suggestion:

header blah blah P 1 
effect blah blah H 9 
blah blah blah b B 6 

(with the 'PHB 196' characters actually rotated 90', to be read on by tilting your head to one side
** Neither option is feasible within the row, I can't do it as inline text, it needs it's own block to do alignment styles. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** I can't think of any easy method to 1) implement it; and 2) think it would expand beyond the confines defeating the condensed space request. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Caster level - add as bracketed value after the spell name (in the name field) but only if it differs from the default (which is shown on the LEVEL header row). Or move into Desc line (prefix or suffix?) Remove string 'Class level' from spell line at least.
** Might be tricky, I have to wrap my head around how to accomplish that, LST code it'd be easy, if value neq to base, then display. In xslt it's probably '<if:test ??? &neq; "casterlevel"> or some such, will need to consult for that [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Remove the text 'Effect:' either completely(?) or replace with 'Desc:' ?
** I suppose that is an option. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Prevent spells from wrapping from one page to the next, if it wont fit, force it to start on a new page
** Need to consult for assistance in how to enforce that. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Grey highlight - rather than alternate grey/white background for each spell, just use the highlight on each header row, making the desc clearer to read?
** Same as above, need to consult a guru. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Domain spells - indicate in italic rather than with an asterisk? Or increase size of asterisk?
** Increased Size of the Asterisk - no screen shot yet [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Latest Screen Shot of Current Work==
[[File:Rev1.JPG]]

Further comments for above screenshot:
Comps - is there benefit in including the actual word 'COMPS:' or just use the familiar bracketed [V,S,M] style ?
Caster level appears to have a very wide column alloted, it only needs to be 2 characters wide?
How about putting the 'school' into the same field as the spell name (not in bold), and make the name field (slightly) wider - free's up some space to add target back onto header line?

Thinking like:
oooooAcid Splash (Conjuration (Creation) [Acid]) | 1 standard action | Instantaneous | Close (30 ft.) | Target: One missile of acid |CL:3 |PHB35e: P.196
[V,S] | Effect: Orb deals 1d3 acid damage. | [SR:No]
(adding pipe symbol to show field seperation for clarity only)

--[[User:FerretDave|FerretDave]] 21:03, 10 February 2012 (EST)

Spell List Suggested Improvements

2012-02-10T10:11:36Z

FerretDave:

Overall Aim is to reduce the page count for spell lists, whilst still keeping all the relevant information clearly visible.

For low level characters, its not a massive headache, for high level (especially clerics), it can get excessive. 28 pages of spells is the current record (no prizes for beating this though).

[I would need to actually count, but I think it was 28 it could have been more ;) [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

For users of the [R]SRD, the spell descriptions are pretty short - a single line usually, whereas for homebrew and Pathfinder, there is often several lines of text.

NOTE - while FEATS use a short DESC and have an option (only via homebrew I think) to use a far longer BENEFIT field, I don't believe that spells have this functionality.
To gain from this, we'd need a code update to output either the DESC or BENEFIT for Spells (as a seperate option than for feats), and to actually get anything of value, LST editors would have to code up seperate BENEFIT for each spell with a lengthier description. Is that of value?

* Homebrewers might think so, but I doubt it would find much use in the official release sets, so be a low priority feature request to be honest. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

Consider variants:
A low level bard with just a handful of spells - could afford to have a full text copy of the book source
A medium level wizard with a few dozen spells - would want a 2 or 3 line description for most spells
A high level cleric with far too many spells to mention - may just want a one line description for each spell.
Is there value in the CODE working with possibly three different levels of description (DESC-SHORT, DESC-MEDIUM and DESC-LONG/BENEFIT)? It would be down to homebrew and lst editors to actually take advantage of this however.

This may be easier solved by merely providing an alternative 'condensed' spell list for those with too many spells, that restricts the output of the DESC to a single line, allowing many spells to be output on one page.

----------------------------

Current default for 5.17.10 and earlier versions till 5.17.1 for comparison
(Could do with a screen shot here)

LEVEL 0
Name Save Information Time Duration Range Comp. Source
oooooAcid Splash 1 standard action Instantaneous Close (30 ft.) V, S PHB35e: P.196
School: Conjuration (Creation) [Acid] SR: No Target: One missile of acid Caster Level: 3
Effect: Orb deals 1d3 acid damage.

Before than, Effect was on the Second Line and a lengthy description would be boxed to waste a lot of space. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

This is 3+ rows - 2 headers and then the description

Drews current 5.17.10 new version:
LEVEL 0
Name School Time Duration Range Caster Level Source
oooooAcid Splash Conjuration (Creation) [Acid] Standard Action Instantaneous Close (50 ft.) Caster Level: 10 PHB: p.196
Target: One missile of acid; EFFECT: [SR: No] You fire a small orb of acid at the target. You must succeed on a ranged touch attack to hit your target. The orb deals 1d3 points of acid damage. [V,S]

This is 2+ lines, one header and an extended description, with some fields moved from the header onto the desc line.

Updates to the 'standard' spell sheet:

For each LEVEL heading 'LEVEL x', add:
* Default casterlevel
* Concentration check
* Spells (of this level) castable per day

For each SPELL entry
* position the [V,S,M] components field (in bold) as a prefix to the description, to aid in searching for specific types (non-somatic spells when silenced for example)
** Done [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Spell Resistance - as Suffix or to desc? But not *between* 'effect:' and the actual desc.
DC - put as suffix to desc? or as prefix? Retain on header line?
Target - suffix or prefix to desc? retain on header line? bold or italic for string'target:'

Placing the Target Text in the Comps/Source area doesn't work out: [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

[[File:Target not good.JPG]]

Source - put as (right justified) suffix on last line of desc, retain on header line, or - if feasible - rotate the text 90 degrees and have it expand down the very far right hand side as a 'narrow' column across both header and desc lines? I.e
Source display suggestion:

header blah blah P 1 
effect blah blah H 9 
blah blah blah b B 6 

(with the 'PHB 196' characters actually rotated 90', to be read on by tilting your head to one side
** Neither option is feasible within the row, I can't do it as inline text, it needs it's own block to do alignment styles. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** I can't think of any easy method to 1) implement it; and 2) think it would expand beyond the confines defeating the condensed space request. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Caster level - add as bracketed value after the spell name (in the name field) but only if it differs from the default (which is shown on the LEVEL header row). Or move into Desc line (prefix or suffix?) Remove string 'Class level' from spell line at least.
** Might be tricky, I have to wrap my head around how to accomplish that, LST code it'd be easy, if value neq to base, then display. In xslt it's probably '<if:test ??? &neq; "casterlevel"> or some such, will need to consult for that [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Remove the text 'Effect:' either completely(?) or replace with 'Desc:' ?
** I suppose that is an option. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Prevent spells from wrapping from one page to the next, if it wont fit, force it to start on a new page
** Need to consult for assistance in how to enforce that. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Grey highlight - rather than alternate grey/white background for each spell, just use the highlight on each header row, making the desc clearer to read?
** Same as above, need to consult a guru. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Domain spells - indicate in italic rather than with an asterisk? Or increase size of asterisk?
** Increased Size of the Asterisk - no screen shot yet [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Latest Screen Shot of Current Work==
[[File:Rev1.JPG]]

Further comments for above screenshot:
Comps - is there benefit in including the actual word 'COMPS:' or just use the familiar bracketed [V,S,M] style ?
Caster level appears to have a very wide column alloted, it only needs to be 2 characters wide?
How about putting the 'school' into the same field as the spell name (not in bold), and make the name field (slightly) wider - free's up some space to add target back onto header line?
--[[User:FerretDave|FerretDave]] 21:03, 10 February 2012 (EST)

Spell List Suggested Improvements

2012-02-10T10:10:33Z

FerretDave:

Overall Aim is to reduce the page count for spell lists, whilst still keeping all the relevant information clearly visible.

For low level characters, its not a massive headache, for high level (especially clerics), it can get excessive. 28 pages of spells is the current record (no prizes for beating this though).

[I would need to actually count, but I think it was 28 it could have been more ;) [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

For users of the [R]SRD, the spell descriptions are pretty short - a single line usually, whereas for homebrew and Pathfinder, there is often several lines of text.

NOTE - while FEATS use a short DESC and have an option (only via homebrew I think) to use a far longer BENEFIT field, I don't believe that spells have this functionality.
To gain from this, we'd need a code update to output either the DESC or BENEFIT for Spells (as a seperate option than for feats), and to actually get anything of value, LST editors would have to code up seperate BENEFIT for each spell with a lengthier description. Is that of value?

* Homebrewers might think so, but I doubt it would find much use in the official release sets, so be a low priority feature request to be honest. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

Consider variants:
A low level bard with just a handful of spells - could afford to have a full text copy of the book source
A medium level wizard with a few dozen spells - would want a 2 or 3 line description for most spells
A high level cleric with far too many spells to mention - may just want a one line description for each spell.
Is there value in the CODE working with possibly three different levels of description (DESC-SHORT, DESC-MEDIUM and DESC-LONG/BENEFIT)? It would be down to homebrew and lst editors to actually take advantage of this however.

This may be easier solved by merely providing an alternative 'condensed' spell list for those with too many spells, that restricts the output of the DESC to a single line, allowing many spells to be output on one page.

----------------------------

Current default for 5.17.10 and earlier versions till 5.17.1 for comparison
(Could do with a screen shot here)

LEVEL 0
Name Save Information Time Duration Range Comp. Source
oooooAcid Splash 1 standard action Instantaneous Close (30 ft.) V, S PHB35e: P.196
School: Conjuration (Creation) [Acid] SR: No Target: One missile of acid Caster Level: 3
Effect: Orb deals 1d3 acid damage.

Before than, Effect was on the Second Line and a lengthy description would be boxed to waste a lot of space. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

This is 3+ rows - 2 headers and then the description

Drews current 5.17.10 new version:
LEVEL 0
Name School Time Duration Range Caster Level Source
oooooAcid Splash Conjuration (Creation) [Acid] Standard Action Instantaneous Close (50 ft.) Caster Level: 10 PHB: p.196
Target: One missile of acid; EFFECT: [SR: No] You fire a small orb of acid at the target. You must succeed on a ranged touch attack to hit your target. The orb deals 1d3 points of acid damage. [V,S]

This is 2+ lines, one header and an extended description, with some fields moved from the header onto the desc line.

Updates to the 'standard' spell sheet:

For each LEVEL heading 'LEVEL x', add:
* Default casterlevel
* Concentration check
* Spells (of this level) castable per day

For each SPELL entry
* position the [V,S,M] components field (in bold) as a prefix to the description, to aid in searching for specific types (non-somatic spells when silenced for example)
** Done [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Spell Resistance - as Suffix or to desc? But not *between* 'effect:' and the actual desc.
DC - put as suffix to desc? or as prefix? Retain on header line?
Target - suffix or prefix to desc? retain on header line? bold or italic for string'target:'

Placing the Target Text in the Comps/Source area doesn't work out: [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

[[File:Target not good.JPG]]

Source - put as (right justified) suffix on last line of desc, retain on header line, or - if feasible - rotate the text 90 degrees and have it expand down the very far right hand side as a 'narrow' column across both header and desc lines? I.e
Source display suggestion:

<nowiki>header blah blah P 1 
effect blah blah H 9 
blah blah blah b B 6 </nowiki>

(with the 'PHB 196' characters actually rotated 90', to be read on by tilting your head to one side
** Neither option is feasible within the row, I can't do it as inline text, it needs it's own block to do alignment styles. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** I can't think of any easy method to 1) implement it; and 2) think it would expand beyond the confines defeating the condensed space request. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Caster level - add as bracketed value after the spell name (in the name field) but only if it differs from the default (which is shown on the LEVEL header row). Or move into Desc line (prefix or suffix?) Remove string 'Class level' from spell line at least.
** Might be tricky, I have to wrap my head around how to accomplish that, LST code it'd be easy, if value neq to base, then display. In xslt it's probably '<if:test ??? &neq; "casterlevel"> or some such, will need to consult for that [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Remove the text 'Effect:' either completely(?) or replace with 'Desc:' ?
** I suppose that is an option. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Prevent spells from wrapping from one page to the next, if it wont fit, force it to start on a new page
** Need to consult for assistance in how to enforce that. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Grey highlight - rather than alternate grey/white background for each spell, just use the highlight on each header row, making the desc clearer to read?
** Same as above, need to consult a guru. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Domain spells - indicate in italic rather than with an asterisk? Or increase size of asterisk?
** Increased Size of the Asterisk - no screen shot yet [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Latest Screen Shot of Current Work==
[[File:Rev1.JPG]]

Further comments for above screenshot:
Comps - is there benefit in including the actual word 'COMPS:' or just use the familiar bracketed [V,S,M] style ?
Caster level appears to have a very wide column alloted, it only needs to be 2 characters wide?
How about putting the 'school' into the same field as the spell name (not in bold), and make the name field (slightly) wider - free's up some space to add target back onto header line?
--[[User:FerretDave|FerretDave]] 21:03, 10 February 2012 (EST)

Spell List Suggested Improvements

2012-02-10T10:03:10Z

FerretDave: further comments on latest screenshot, updated display of 'rotated text' option for clarity

Overall Aim is to reduce the page count for spell lists, whilst still keeping all the relevant information clearly visible.

For low level characters, its not a massive headache, for high level (especially clerics), it can get excessive. 28 pages of spells is the current record (no prizes for beating this though).

[I would need to actually count, but I think it was 28 it could have been more ;) [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

For users of the [R]SRD, the spell descriptions are pretty short - a single line usually, whereas for homebrew and Pathfinder, there is often several lines of text.

NOTE - while FEATS use a short DESC and have an option (only via homebrew I think) to use a far longer BENEFIT field, I don't believe that spells have this functionality.
To gain from this, we'd need a code update to output either the DESC or BENEFIT for Spells (as a seperate option than for feats), and to actually get anything of value, LST editors would have to code up seperate BENEFIT for each spell with a lengthier description. Is that of value?

* Homebrewers might think so, but I doubt it would find much use in the official release sets, so be a low priority feature request to be honest. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

Consider variants:
A low level bard with just a handful of spells - could afford to have a full text copy of the book source
A medium level wizard with a few dozen spells - would want a 2 or 3 line description for most spells
A high level cleric with far too many spells to mention - may just want a one line description for each spell.
Is there value in the CODE working with possibly three different levels of description (DESC-SHORT, DESC-MEDIUM and DESC-LONG/BENEFIT)? It would be down to homebrew and lst editors to actually take advantage of this however.

This may be easier solved by merely providing an alternative 'condensed' spell list for those with too many spells, that restricts the output of the DESC to a single line, allowing many spells to be output on one page.

----------------------------

Current default for 5.17.10 and earlier versions till 5.17.1 for comparison
(Could do with a screen shot here)

LEVEL 0
Name Save Information Time Duration Range Comp. Source
oooooAcid Splash 1 standard action Instantaneous Close (30 ft.) V, S PHB35e: P.196
School: Conjuration (Creation) [Acid] SR: No Target: One missile of acid Caster Level: 3
Effect: Orb deals 1d3 acid damage.

Before than, Effect was on the Second Line and a lengthy description would be boxed to waste a lot of space. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

This is 3+ rows - 2 headers and then the description

Drews current 5.17.10 new version:
LEVEL 0
Name School Time Duration Range Caster Level Source
oooooAcid Splash Conjuration (Creation) [Acid] Standard Action Instantaneous Close (50 ft.) Caster Level: 10 PHB: p.196
Target: One missile of acid; EFFECT: [SR: No] You fire a small orb of acid at the target. You must succeed on a ranged touch attack to hit your target. The orb deals 1d3 points of acid damage. [V,S]

This is 2+ lines, one header and an extended description, with some fields moved from the header onto the desc line.

Updates to the 'standard' spell sheet:

For each LEVEL heading 'LEVEL x', add:
* Default casterlevel
* Concentration check
* Spells (of this level) castable per day

For each SPELL entry
* position the [V,S,M] components field (in bold) as a prefix to the description, to aid in searching for specific types (non-somatic spells when silenced for example)
** Done [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Spell Resistance - as Suffix or to desc? But not *between* 'effect:' and the actual desc.
DC - put as suffix to desc? or as prefix? Retain on header line?
Target - suffix or prefix to desc? retain on header line? bold or italic for string'target:'

Placing the Target Text in the Comps/Source area doesn't work out: [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

[[File:Target not good.JPG]]

Source - put as (right justified) suffix on last line of desc, retain on header line, or - if feasible - rotate the text 90 degrees and have it expand down the very far right hand side as a 'narrow' column across both header and desc lines? I.e
Source display suggestion:

<nowiki>header blah blah P 1
effect blah blah H 9
blah blah blah b B 6</nowiki>

(with the 'PHB 196' characters actually rotated 90', to be read on by tilting your head to one side
** Neither option is feasible within the row, I can't do it as inline text, it needs it's own block to do alignment styles. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
** I can't think of any easy method to 1) implement it; and 2) think it would expand beyond the confines defeating the condensed space request. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Caster level - add as bracketed value after the spell name (in the name field) but only if it differs from the default (which is shown on the LEVEL header row). Or move into Desc line (prefix or suffix?) Remove string 'Class level' from spell line at least.
** Might be tricky, I have to wrap my head around how to accomplish that, LST code it'd be easy, if value neq to base, then display. In xslt it's probably '<if:test ??? &neq; "casterlevel"> or some such, will need to consult for that [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

* Remove the text 'Effect:' either completely(?) or replace with 'Desc:' ?
** I suppose that is an option. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Prevent spells from wrapping from one page to the next, if it wont fit, force it to start on a new page
** Need to consult for assistance in how to enforce that. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Grey highlight - rather than alternate grey/white background for each spell, just use the highlight on each header row, making the desc clearer to read?
** Same as above, need to consult a guru. [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)
* Domain spells - indicate in italic rather than with an asterisk? Or increase size of asterisk?
** Increased Size of the Asterisk - no screen shot yet [[User:LegacyKing|LegacyKing]] 20:16, 10 February 2012 (EST)

==Latest Screen Shot of Current Work==
[[File:Rev1.JPG]]

Further comments for above screenshot:
Comps - is there benefit in including the actual word 'COMPS:' or just use the familiar bracketed [V,S,M] style ?
Caster level appears to have a very wide column alloted, it only needs to be 2 characters wide?
How about putting the 'school' into the same field as the spell name (not in bold), and make the name field (slightly) wider - free's up some space to add target back onto header line?
--[[User:FerretDave|FerretDave]] 21:03, 10 February 2012 (EST)

Talk:Spell List Suggested Improvements

2012-02-10T10:00:28Z

FerretDave: added concentration option as per caster level

Spell List Suggested Improvements

2012-02-09T19:14:07Z

FerretDave: Output Sheet Layout Review / redo - Spells

OS Sheet Improvement Discussion

2012-02-09T18:25:09Z

FerretDave: Output Sheet Layout Review/ redo

Discussion from thread http://games.groups.yahoo.com/group/pcgen/message/107383 migrated here for ease of use

A list of suggested updates to the character output sheet.

'''General Aims:'''

Improve the format through reorganisation and alternative display styles to reduce the overall page count of an OS (primarily by improving spell lists).

Ensure that the majority of the regularly used information (specifically combat related) appears on the first page (or first 2 pages at least), this involves moving some less used information to subsequent pages.

Allow 'equipment' changes to be made, and only require a re-print of the first few (ideally 1 or 2) pages - this may already be satisfied.

'''Suggestions'''

Move fields off P1 onto Bio page.
(most of the 'descriptive' fields are not referenced very often, so aren't need on the first page)
Alignment (to help keep such information secret for those in disguise) JIRA
Region - can also be a giveaway for disguised characters.
Deity - move to keep secret, do clerics really need a reminder on P1? JIRA
Height, Weight - though can be useful as they come into play for traps. JIRA (covers descriptive fields in general, as an option)
Eyes, Hair - Any reason to duplicate these on P1 and Bio?
Age, Gender, Race - Not sure of benefit in moving these over leaving as is.
Points - Character generation points? Do they need outputting at all?
Reduce header line to just 2 rows.

Remove duplicated fields
BAB - listed by itself, and then for each variation of Melee, Ranged, Grapple and CMD

Add fields to P1
Effective Level & Challenge Rating
Templates applied (Rage is the biggie - Barbarians want two copies of P1 and need to differentiate) JIRA
Spell effects applied (potential for very large list, perhaps limited display)
Companions box - who's who in the party is often referred to (in my group) JIRA
Party Companions box - is there any benefit to having just of list of PC's separately to Companions?

Update fields
AC split out for all the possible types of enhancements
More weapons being displayed on P1
Skills broken out to show class, feat, equipment modifiers
Shift Miss Chance, ASF, ACP, Spell Resistance down a row (freeing up space for AC details)
Shift Speed, DR, Subdual down a row
Move HP 'box' to far right, reduce size of box and use Margin for continued damage notes JIRA
Move Subdual damage box to far right, as per HP
Encumbrance to persist (even 'light' should still show, and show limit before reaching next bracket)
Turning table - using that space for non-clerics, adding special attacks into that space (but what to do with multi-class that need both?)
Equipment - ensure that changes to carried equipment only affects first two pages (avoid reprinting entire sheet) JIRA
Prevent a large portrait from pushing the 'stats' section down.
Force portrait on P1 to be a small picture (limited to header size)?
Conditional Modifiers - move to one side, or bottom of page(?) to allow extended notes in margin?
Feats ('disadvantages' on Drews sample sheet) - limit source name to prevent long feats/disadvantages from wrapping rather than forcing 70%/30% split.
Footer - unbold the 'character:' and 'Player:' prefixes, leaving just the actual tokens bold.
Simple weapon display - put 'total attack bonus' and 'damage' as prefixes to the actual value rather than a separate row

Display style
Bio/header information has a line between the data and the title, alter this to make it more intuitive
(box the info together or put the title as a prefix to the token?)
Use initial caps rather than all caps on headers

Page order
With double sided printing, pages 2 & 3 become more valuable open side by side in a binder, thus page 1 becomes essentially just a cover sheet. However, single sided printing seems more favourable currently.

Filing Assistance
To aid in finding a specific character, NPC or monster from a ring binder:
Level/ECL/CR prominent on P1 -done
Character Name, Player Name & Level on footer of every page JIRA-done
Type & Subtype prominent on P1

Include files /templating
not a quick fix - simplify building new OS by providing building blocks for each individual section on the OS, to be arranged on the page by end users.

[[Spell List Suggested Improvements]]