PCGen 3.1.0 available

Status
Not open for further replies.

Leopold

NKL4LYFE
What an eventful 2 weeks since our last release!
This release is being sent to Wotc for their
evaluation to determine if the data is indeed
OGL compliant, and the application is D20 compliant.
We've been in constant contact with them and we
believe that we're there. We don't know how long
it will take Wotc to make their determination, but
we'll keep you posted with any developments. Once
we are certified as OGL/D20 compliant, we will
begin negotiations for permission on their non-SRD
material. We'll keep you all posted on how that
proceeds as well. :)

Why have we become OGL and D20 compliant? Those of
you who have been with us for a while know that we've
been investigating and working on becoming OGL
compliant for over a year now. We were actually
quite close to being done with that, but there were
a number of reasons why we didn't. Once Wotc told
us that if we became OGL and D20 compliant they
would consider giving us permission for all their
non-SRD material, it became a no-brainer. The
OGL compliance was quite simple - the changes required
for the D20 compliance were a bit stickier, and those
drove the main changes you will notice in this release.
D20 compliance means we can no longer randomly
generate stats or hit points, this is considered
'interactive'. To compensate for this we've made the
purchase mode much more flexible - you can specify
the cost of stats all the way down to 0 and as high
as you want. We'll make it easier for you to just
type your stats in as well. That way you can use
your favorite die roller (use actual dice or one of
the billions of die rollers on the internet) and copy
and paste the result it. You'll also notice the
OGL license comes up - section 15 at the bottom is
dynamically generated based upon the sources in
pcgen's data directory.

A lot of work has gone into this, and this couldn't
have happened so rapidly without a lot of people
putting in extra time on this. Being the Benevolent
Dictator, I expect myself to put lots of time into
it, but I'm always grateful for those who also help
move the mountain! Anthony Valterra from Wotc has
been a great resource and has spent a lot of time
explaining the nitty gritty of what OGL/D20 compliance
means for us specifically and what we need to change
to get there. Mynex has spent a lot of time on the
phone with Anthony and then helped translate to
the rest of us what needs to be done. Jonas Karlsson
and Greg Bingleman have helped do a lot of the coding,
and Andrew McDougall has done a lot of the data work.

This release represents a lot of very fundamental
changes, so it would be best to install this in a
new directory. The LstConverter in the Tools menu
has been updated so it can update your old data
files to use the new tags which have been created.
Make a backup copy of your data files before you
do this as it will overwrite them.

You can right-click on an item in the available table
in the Inventory tab to "Customise" it (make a
normal item a magical one or just change its size).
Anyone wanting to use the "print" button will need
the pdf library at
http://prdownloads.sourceforge.net/pcgen/pdf.zip and
unzip it into your PCGen's lib directory (those are
the 4 files PCGen will indicate are missing if you try
to print without having downloaded that libarary).


Here's the list of everything that has been
addressed in this release. If you reported one
of these, please verify that it is was addressed
properly. PCGen is available at
http://pcgen.sourceforge.net , and the main
discussion group is at
http://groups.yahoo.com/group/pcgen . Be sure to
download at least the first two parts of PCGen...
pcgen310_part1of3.zip and pcgen310_part2of3.zip.
Please download both of these files!
There's also pcgen310_part3of3.zip which is the
complete documentation - it's been split out due to
its increased size and the fact that it doesn't change
much from release to release. Since some documentation
is included in part1of3.zip, some files will also
be in part3of3.zip, so unzipping one over the other
will require overwriting of files (which is fine
since they're identical).

We've got some OS-specific installs of PCGen to help
those who have trouble installing the generic
version. At
http://groups.yahoo.com/group/pcgen/files/Alternate PCGen%
20Releases/

you will find a list of these releases which you can
use if you have trouble with the version you find
here. Please note that there alternate versions are
updated by users, so there may be some time lag
between when an official release comes out and
when the alternate OS-specific release is ready.


Bugs
599972 'All stats the same' doesn't work
590652 Sub Menu for Stat Rolling method wrong
587561 Monster Alignment
596926 NAMEISPI tag breaks GUI behavior
584434 A bad file CRC
588716 Spell List Appears in Language Block
595055 Summary tab level field always reads '1'
588157 Opening Character File Problem
595204 Main Source list not updated on PC load
591883 spell resistance not displayed right
595059 Beep when changing tabs in UI
586711 Dwarf barbarian speed error
594812 Template list has no default selection
591487 Item spell ability customization broken
592635 Armor Proficiency (1x)?
590857 Bracers of Armor do not add to AC
588224 Skill requirements not fullfilable
589324 DM Notes tab is not PC Notes
587839 Contemplate Restriction problem
589443 P-Class Skill Pre-Reqs Broken
588965 starting weapon prof missing
589137 Familiar hit dice/points not correct
588741 No meow for Animal Lord
587448 Skill type cannot be fulfilled for DivA
587825 Pre-req for Pyro
588676 Multiclassing prevents familiar-taking
588261 Wizards can't select basic familiars
588379 Familiar's ranged attack wrong
588382 Familiars/Mounts Natural Armor
588299 Prestige classes appear to be broken
588260 Class-granted special abils messed up
588059 corrected typos for Divine Agent
588177 Balagarn's Iron Horse?
587912 BONUS:SKILL broken
587867 missing container halts pcg load
585163 Halflings have a +1 to hit
586093 Adamantine overrides Masterwork
587443 correction for Divine Agent (MotP)

Features
599502 PRECHECK:#,name(=#),name=# (OGL)
586101 Need COUNT[FOLLOWERS] tag
596643 Extract BAB types to formulae
595202 Move campaign load code to PCG Parser
592630 PREEQUIP tag needed
592632 Armor Defense Bonus display
592634 DEFBONUS: tag for equipment
509751 Search function in Inventory
536445 Exotic Weapon Proficiencies&House Rules
523919 Customize the Customization
522014 Customizing Gems
504712 Customizing scrolls
502831 Custom Wands

Output Sheets
589115 Added token to ROG.fo templates
578931 Add filter option for PREPARE tag
569437 Pictures taken from wrong directory
527557 Charset encoding support in templates
517887 Psionic 0-level 'talents' per day

PCGen:DM: Bugs
589999 Arcane Archer with Bow
594455 DMG Assassin Class Misspellings
588259 Skills list not showing correctly
591203 Cannot Add PrC's
573390 Holy Avenger weilded by Paladin
588319 Spells with no home
583556 Initiate Special Ability Choice
568029 Wrong Prestiege Domain added

PCGEN:DM: List File Fixes/New List Files
600012 PHb classes converted to WotC request
596500 Mythic Races: a few BONUS systax errors
594692 Net Book of Feats PRESA tag fixes
594300 Holy Avenger fix for Paladin weilder
587761 additional base equip types
563636 Reallow Spell Comp Pouch to hold items
584274 Several classes named Shaman
587779 Goblins missing bonus to riding wolves
570248 Carry Vials like Potions
584099 Dragon Star Skill focus incorrect
589879 Monte Cooke Ranger Fix
584809 Quintessential Rogue

PCGEN:DM: Tag Modification Requests
564265 Spell Resistance in equipment to SR
599261 Race.lst: BAB > BONUS w/PREDEFAULTMONSTER:Y
599249 BAB: in classes.lst to BONUS:COMBAT|BAB|
599252 CHECK1, etc to BONUS:CHECKS|BASE.name|
596812 Changed checks (saves) to load from file
596982 TEMPLATE: deprecated STAT tags.
596644 BAB:G/M/B/O to BAB:>formula<
585200 SUBSA to SA:.CLEAR

The PCGen Development Team
 
Last edited:

log in or register to remove this ad


Why have we become OGL and D20 compliant?

Unfortunately, you have NOT become OGL and D20 STL compliant.

Reading the Open Game License version 1.0a that appears in your product, it appears (and I stress that word) that you don't understand the actual content of the document in question.

Section 6 of the Open Game License, version 1.0a, clearly states (cut and pasted from your own copy of the OGL in PCGen):

"6.Notice of License Copyright: You must update the COPYRIGHT NOTICE portion of this License to include the exact text of the COPYRIGHT NOTICE of any Open Game Content You are copying, modifying or distributing, and You must add the title, the copyright date, and the copyright holder's name to the COPYRIGHT NOTICE of any original Open Game Content you Distribute."

Notice the words, EXACT TEXT in there... not "approximate text" or "incorrect attribution".

Meanwhile, you incorrectly attribute the section 15 of almost EVERY product you mention. You even mention products that have NO SECTION 15.
 

HellHound said:
Why have we become OGL and D20 compliant?

Unfortunately, you have NOT become OGL and D20 STL compliant.

Reading the Open Game License version 1.0a that appears in your product, it appears (and I stress that word) that you don't understand the actual content of the document in question.

Section 6 of the Open Game License, version 1.0a, clearly states (cut and pasted from your own copy of the OGL in PCGen):

"6.Notice of License Copyright: You must update the COPYRIGHT NOTICE portion of this License to include the exact text of the COPYRIGHT NOTICE of any Open Game Content You are copying, modifying or distributing, and You must add the title, the copyright date, and the copyright holder's name to the COPYRIGHT NOTICE of any original Open Game Content you Distribute."

Notice the words, EXACT TEXT in there... not "approximate text" or "incorrect attribution".

Meanwhile, you incorrectly attribute the section 15 of almost EVERY product you mention. You even mention products that have NO SECTION 15.


We're not perfect, and we're already in the process of fixing this. :)

The Alpha/beta builds everyone has come to know and love should have this done correctly within the next 24 hours...
 
Last edited:

I didn't notice this yesterday when I looked at PCGen 3.1. But, it looks like you are not compliant with section 8 of the OGL.

8. Identification: If you distribute Open Game Content You must clearly indicate which portions of the work that you are distributing are Open Game Content.

This should be pretty easy for you to implement.

Also, section 2 of the OGL says:
2. The License: This License applies to any Open Game Content that contains a notice indicating that the Open Game Content may only be Used under and in terms of this License. You must affix such a notice to any Open Game Content that you Use. No terms may be added to or subtracted from this License except as described by the License itself. No other terms or conditions may be applied to any Open Game Content distributed using this License.

This means that you cannot use other licensing schemes in conjunction with OGC. So, GNU doesn't mix with the OGL and OGC content. I think I know how you are getting around this restriction. However, it is not clear from your web page nor from anything included with the download. I think it would be wise for you to explain somewhere how you are complying with point 2 of the OGL. This will eliminate someone from asking the question in a newsgroup and an uninformed person giving a wrong answer.
 
Last edited:

smetzger said:
This means that you cannot use other licensing schemes in conjunction with OGC. So, GNU doesn't mix with the OGL and OGC content.

Actually its (L)GPL not GNU. Splitting hairs here, but GNU is "GNU not Unix", only vaguely related. Though both under similar licenses.

I think I know how you are getting around this restriction.

They are not applying a new license to the data, only to the source code.


If you or anyone else see some sort of a problem with OGL or the license, PLEASE post it as a bug report for PCGen or send it to the newsgroup (even this may be slightly incorrect, at least list it in the bug report). The more people that test and hunt, the more flaws will be found. The more bugs that are found and REPORTED in a standard place, i.e. bug report, the more bugs get crushed. Thus the product improves and grows.

Things get lost on boards. People see them and then forget them if they are not written down somewhere. If they are all in the wonderful bug list, then they can be checked off when fixed.

Thanks,
Arnix (tm)
 

smetzger said:
8. Identification: If you distribute Open Game Content You must clearly indicate which portions of the work that you are distributing are Open Game Content.

This should be pretty easy for you to implement.

Hmm. I thought we had that in 3.1.0? Ah well, we know how we're going to handle it (PI is going to be tagged as PI, which will be visible in the interface) and I believe the code to support that is in, though it may be not all the lst files were gone through in time.

Also, section 2 of the OGL says:
This means that you cannot use other licensing schemes in conjunction with OGC. So, GNU doesn't mix with the OGL and OGC content. I think I know how you are getting around this restriction.[/B]

Yeah, program is LGPL, lst files are meant to be OGL/STL. You may well be right that we aren't clear on this in the documentation/webpage. Isn't it enough that I know? ;-)

/Jonas
 

jujutsunerd said:


Hmm. I thought we had that in 3.1.0? Ah well, we know how we're going to handle it (PI is going to be tagged as PI, which will be visible in the interface) and I believe the code to support that is in, though it may be not all the lst files were gone through in time.



You don't need to identify PI. You need to identify OGC.

Oops my bad on the GNU and GPL mixup.
 

smetzger said:
Oops my bad on the GNU and GPL mixup.

No prob, just trying to keep things straight. Someone not knowing might have come along and went looking for GNU laws and then started flaming about nont GNU compliance or something. :)


Arnix (tm)
 

smetzger said:
You don't need to identify PI. You need to identify OGC.
Ummm...you need to identify both. Section 8 says you need to ID the OGC, but Section 7 says
7. Use of Product Identity: You agree not to Use any Product Identity, including as an indication as to compatibility, except as expressly licensed in another, independent Agreement with the owner of each element of that Product Identity
which means that you'll need to ID any PI that you've been given permission to use.
 

Status
Not open for further replies.
Remove ads

Top