On November 14, 2019 at 12:15 AM "Andrew Maitland via Groups.Io" <drew0500@...> wrote:
About to go to bed but let me address a few things:
1) PCGen uses git for version control. I would know because I've been a part of the migration effort from the previous version control "SVN" to Git. Also, we have two primary branches - Master which houses all the latest features (6.09.x) and then the production branch named for the production version (6.08).
2) Homebrew support is readily available. First I created a skeleton set for customization, next I pushed the code team to support an additional data folder preference location (Previous to this, you had data and vendordata), today you also have homebrewdata.
3) Most of our volunteers will tell folks to move homebrew content to an alternative location to avoid being overwritten. Unless you're creating new game systems or customizing your own character sheet exports, this feature is quite sufficient. However, symlinks is a great mechanism to allow for expansion for additional content requirements such as the aforementioned folders.
4) PCGen is a 20 year old open source project that has been altered over thousands of man hours, by hundreds of volunteers with various levels of experience and knowledge. If you don't like something, want something fixed, or want to make a change, then join the team and enact it. That's how most of us joined up. We wanted to see a change and made it happen. This is truly a community project.
Now, to the answer of documentation and support - F1 opens the program documentation. There is a List Tag index that explains all the lst and pcc file tags, there is an Outputsheet tag index in case you want to branch out into creating some character sheets. I also created several youtube videos to explain basics of pcgen, how to code things up, and made some examples.
My availability is limited, but I have a group of lurking volunteers over on discord that answer questions in real time (Might be delayed a few hours, cause time zones) but for the most part we average a 5-15 minutes turn around time during the Main North American time zones. (2am to 5am we don't have many up and about.)
For the Language add, you open the LANGUAGE file. Though why would "read lips" be a language you learn? Someone speaking another language would make that difficult. I recall a 3rd edition skill called read lips, and there is a reference to skills. However, at the end of the day, you do whatever you want. Want it as another language, then add it to the language file, want it as a skill, then add it as a skill, want it as a class feature, then make it a class feature. Adding a skill or language is a 5 minute task.
Read Lips <tab> TYPE:Observation
Read Lips <tab> TYPE:Language.NormalSkill
Read Lips <tab> TYPE:SpecialQuality <tab> CATEGORY:Special Ability <tab> DESC:You can read the lips and decipher most of a conversation you can observe.
Help us to help you. Tell us what the end state/goal is, and we can help you get there. (Within reason).
Hope that covered the questions that I saw posted.
PCGen Board of Directors - Content Silverback
> This is why the homebrew system exists to allow users to modify the core rules in order to meet their requirements.
Could someone point to the documentation of the homebrew system and syntext for the my_homebrew.pcg file?