Further notes on CMP to RSRD
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.
Apologies for the formatting, this probably needs tidying up... 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.
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 creatures 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 :-)
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...
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.
