Posting Guidelines

Introduction

This document was last updated on **19th June 2007**

To avoid some common hot-topics that have been beat to death, here are some basic ground rules for posting on our main yahoo board at [[1]] group at yahoo is an e-mail community dedicated to the (but always fun) discussion of PCGen product, there are some ground rules which everyone needs to follow. Please read the following document carefully, or you will be jumped on by the soft pawed ones! (that would be the Moderators).

Where should I post my question?

• If it's data syntax or building-your-own class/feat/race/equipment/etc related, then post it at [[2]]
• If it's related to official PCGen data or development of LST syntax, then post it at [[3]]
• If it's to do with internationalising PCGen, then post it at [[4]]
• If it's anything else related to PCGen, then post it at [[5]]

A note on Closed Content/PI

We respect the Publishers wishes with regards to PI and Closed Content and therefore strongly prefer that any discussion of the creation of those data sources are held in Generic terms.

However, we realise that a vast majority of you are asking questions on how to code data sets for your own personal use and so we're no longer going to growl or wave fingers at people who mention a PI/Closed Content reference when asking questions. We will however continue to state our responses to those questions in a generic manner and hope that you'll do the same.

We will still not tolerate any PI/Closed Content being uploaded to our file areas or any attempts at illegally sharing data sources.

Examples

1. A user asking how to code the Skirmish ability from the Complete Adventurer (WotC) will receive a helpful polite answer phrased in generic terms, e.g "To implement an Ability that gives 1d6 damage every 3 levels you'd want to look to the Rogue sneak attack progression in our SRD files". But no more finger waving or growling from the Moderators!
2. A user stating that they want someone to give them a privately coded data source for the Complete Adventurer set will be warned etc.
3. A user uploading the Complete Adventurer data source will be warned etc.

So, for all community members, there's no longer any need to call in the Moderator if a PI/Closed Content question is asked. We will step in if necessary if someone blatantly abuses this new policy.

For reference

Closed Content/PI is any data source that we don't have permission to publish ourselves or isn't OGL/OGC. Please see [Permissions] for a list of publisher permissions that we currently have.

Any special requirements if I'm reporting a bug, making a request or suggestion?

• Bugs: The title of the post must start with [BUG], and the body of the post must contain the version of PCGen, your operating system version and a step-by-step process to duplicate the bug. They get fixed much faster this way!
• Feature Requests: The title of the post must start with [FREQ] (abbreviation for feature request), and specific suggestions or requests are welcomed and appreciated!
• Documentation: The title of the post must start with [DOC] if you are requesting clarification of documentation or if you have any suggestions about improving the documentation.
• Output/Character Sheets: The title of the post must start with [OS] if you're commenting about the output sheets and want to make sure that the output sheet monkeys notice your post.

Our hope is that this list will stay as a community of people willing to share thoughts and ideas about various aspects of PCGen; Criticism and feedback on specific parts of PCGen and any general issues with PCGen is very appropriate for this list and actively encouraged - provided such feedback is well thought-out, rational, and promotes an open discussion of the issue in question. Although this list is essentially administered by those involved in the PCGen project, posters will not be removed from the list or blacklisted simply because they are critical of a part of PCGen or PCGen in general.

An exception to this occurs in relations to trolling, flaming and personal attacks. Simply put, trolling, flaming and personal attacks ARE NOT tolerated on the PCGen list. Posters who troll, flame or attack others will be placed on REVIEW or removed from the list if such activity continues. Wherever possible, the Soft Pawed Ones will intervene and try to nip flame wars in the bud before they spiral out of control.

A few definitions

• Trolling: posting messages designed to draw an angry response from those who read it
• Flame: a sarcastic, biting message, which often attacks the intelligence, education and/or perceptiveness of others and is usually designed to draw an angry response from them
• Personal attack: A negative comment in a discussion, which is directed at/or dealing with a person or persons instead of the issue at hand. This includes flaming publishers, whether PCGEN supports them or not. We are not a discussion board that allows slamming of publishers, they have their own boards for that.

Remember that everyone on the list comes from a different background. We have engineers, lawyers, college students, and high school-age members who post on a variety of topics. Please respect the fact that their opinions might be different from yours and move on. Many users also come from non English backgrounds or countries, bear this in mind when you wish to flame them for their spelling or grammar!

In addition, please adhere to the following rules of etiquette:

1. Please refrain from using profanity and other insulting language in your posts. This is to include starring out of letters or other forms of self-censorship.
2. When responding to a post, make sure to quote only what is required. In general, do not quote more than you actually contribute.
3. Do not make "me too" posts.
4. If a post begins to move off of its original topic, PLEASE GIVE IT A NEW SUBJECT (and include [OT] in the subject header). (This is an especially important rule as the PCGen staff who are on the list have a limited amount of time in which to read the messages sent to it.)
5. If an OT subject carries on too long a Moderator may step in and request that the contributers to the thread take it off-list.
6. Please keep your sig files reasonable in length. Five to six lines is considered reasonable.
7. Please do not post virus warnings without the prior approval of the list staff.
8. When quoting, please remove the two pages of ads that appear from various web-based email clients.

Thanks! The Moderators