Further notes on CMP to RSRD - Revision history

FerretDave at 18:44, 1 March 2012

2012-03-01T18:44:01Z

FerretDave: Notes on CMP to RSRD conversion

2012-03-01T18:37:59Z

Notes on CMP to RSRD conversion

FerretDave at 19:31, 27 February 2012

2012-02-27T19:31:11Z

FerretDave: Hints on migrating CMP to RSRD

2012-02-27T19:15:19Z

Hints on migrating CMP to RSRD

FerretDave: batch file startup suggestion added

2012-02-27T10:57:45Z

batch file startup suggestion added

FerretDave at 23:21, 24 February 2012

2012-02-24T23:21:46Z

FerretDave at 23:09, 24 February 2012

2012-02-24T23:09:33Z

FerretDave: Random suggestions for CMP to RSRD conversion

2012-02-24T23:08:25Z

Random suggestions for CMP to RSRD conversion

New page

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. 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.

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.

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)
[[
Further Notes on CMP to RSRD Migration]]

@@ Line 8: / Line 8: @@
 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.
@@ Line 24: / Line 30: @@
 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.

@@ Line 20: / Line 20: @@
 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 :-)
 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.

@@ Line 6: / Line 6: @@
 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.
@@ Line 23: / Line 21: @@
 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 :-)
-Willpower - replace with 'Will'
+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)
@@ Line 35: / Line 33: @@
 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.
-[[Further Notes on CMP to RSRD Migration, part2]]
+More 'technical' detail on search/replace can be found here: [[Further Notes on CMP to RSRD Migration, part2]]

@@ Line 20: / Line 20: @@
 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.
+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 :-)
 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)

← Older revision		Revision as of 23:21, 24 February 2012
Line 11:		Line 11:

	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.		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.
		+
		+	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)		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)

@@ Line 2: / Line 2: @@
 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. These comments are just to try and help you avoid some of the pitfalls others have discovered.
+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.
 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.
 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.
 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.
@@ Line 23: / Line 29: @@
 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)
 [[Further Notes on CMP to RSRD Migration, part2]]

@@ Line 16: / Line 16: @@
 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)
 [[
 Further Notes on CMP to RSRD Migration]]