FAQ and Help - Revision history

Nylanfs: /* High Resolution Display */

2018-03-08T19:06:38Z

‎High Resolution Display

LegacyKing: /* What systems does PCGen support today? */

2018-02-26T00:12:23Z

‎What systems does PCGen support today?

LegacyKing at 00:10, 26 February 2018

2018-02-26T00:10:13Z

LegacyKing: /* Trouble Shooting Problems */

2018-02-17T21:00:38Z

‎Trouble Shooting Problems

LegacyKing: /* Mac Installation Issues */

2016-05-19T23:44:22Z

‎Mac Installation Issues

LegacyKing: /* Using Pathfinder in PCGen */

2016-03-01T18:48:26Z

‎Using Pathfinder in PCGen

LegacyKing: Add Unchained Class and decision making.

2016-03-01T18:44:39Z

Add Unchained Class and decision making.

LegacyKing: /* Trouble Shooting Problems */

2015-02-26T19:21:28Z

‎Trouble Shooting Problems

LegacyKing: /* Is there support for problems? */

2014-07-22T00:05:04Z

‎Is there support for problems?

LegacyKing: Add new sections, and expand upon what PCGen is and is capable of.

2014-07-21T23:33:45Z

Add new sections, and expand upon what PCGen is and is capable of.

@@ Line 80: / Line 80: @@
 ===High Resolution Display===
 I was able to workaround this issue by going into the compatibility properties of the PCGen shortcut and setting the "Override high DPI scaling behavior" to System. This was tested on Windows 10.
 === Java 7 for version 5.17.11 or lower ===

@@ Line 20: / Line 20: @@
 * Spycraft
 * Xcrawl
 Non-d20 Systems we're building support for:
-* Killshot by Broken Ruler Games (This is ready to play but needs a Character Sheet to display)
 * Cyberpunk
 * Shadowrun

← Older revision		Revision as of 00:10, 26 February 2018
Line 69:		Line 69:

	== Trouble Shooting Problems ==		== Trouble Shooting Problems ==
		+
		+	===Mouse Over Issues for some users===
		+	Solution: run Command Line, navigate to your PCGen installed files "cd c:\the\path\to\pcgen" and type in:
		+	java "-Dsun.java2d.d3d=false" -jar .\pcgen.jar

	===High Resolution Display===		===High Resolution Display===

← Older revision		Revision as of 21:00, 17 February 2018
Line 69:		Line 69:

	== Trouble Shooting Problems ==		== Trouble Shooting Problems ==
		+
		+	===High Resolution Display===
		+	I was able to workaround this issue by going into the compatibility properties of the PCGen shortcut and setting the "Override high DPI scaling behavior" to System. This was tested on Windows 10.

	=== Java 7 for version 5.17.11 or lower ===		=== Java 7 for version 5.17.11 or lower ===

← Older revision		Revision as of 23:44, 19 May 2016
Line 115:		Line 115:
	SOLUTION: Disable Gatekeeper, run PCGen, re-enable Gatekeeper. Once PCGen has run once successfully, it's ignored by Gatekeeper.		SOLUTION: Disable Gatekeeper, run PCGen, re-enable Gatekeeper. Once PCGen has run once successfully, it's ignored by Gatekeeper.

		+	UPDATE:
		+
		+	* Hold down "control" button
		+	* Click on the app that is triggering the message about the security preferences
		+	* Select "open" to override and install/open the application
		+
		+	This allows you to avoid changing the security setting to "anywhere."

	=== Homebrew OS Sheet for working 5.17.16 and forward ===		=== Homebrew OS Sheet for working 5.17.16 and forward ===

@@ Line 30: / Line 30: @@
 * Unchained Classes - Q&A:
 ** '''QUESTION''': How can I created an Unchained x class?
-** '''ANSWER''': Select the base class, Rogue for Unchained Rogue as an example. Once you add the first level, go to the Feats & Abilities tab, under Class Features, there should be a CLASS SELECTION group. Select the Unchained Version from there. Congratulations, you now have an Unchained version of the Class.
+** '''ANSWER''': First, you need to make sure you are loading the correct book(s). You will need to load ''Pathfinder Unchained'' to have access to the first four Unchained variant classes - Barbarian, Monk, Rogue, and Summoner. Select the base class, Rogue for Unchained Rogue as an example. Once you add the first level, go to the Feats & Abilities tab, under Class Features, there should be a CLASS SELECTION group. Select the Unchained Version from there. Congratulations, you now have an Unchained version of the Class.
 ** '''LIMITATIONS''': Warning - Due to how PCGen processes SPELL LISTS, an Unchained Summoner will require you to SAVE and RELOAD to have the correct spells populate your spell list.
-** QUESTION: I'm very curious (from both a user's viewpoint and that of a designer) as to why you made the Unchained classes as options within the class (when the source is selected) instead of a separate class in their own right. I actually found that very confusing when making an unchained class as I couldn't select it from the class list as one would usually do when making a character. It was only when I went back to the summary screen after selecting the class that I realised I could make the Unchained version. That's a design decision that needs to be deliberated upon and possibly altered because as it stands, it is highly confusing and may lead a lot of people to believe that you can't make an Unchained class at all in PCGen.
+** QUESTION: I'm very curious (from both a user's viewpoint and that of a designer) as to why you made the Unchained classes as options within the class (when the source is selected) instead of a separate class in their own right. I actually found that very confusing when making an unchained class as I couldn't select it from the class list as one would usually do when making a character. It was only when I went back to the summary screen after selecting the class that I realized I could make the Unchained version. That's a design decision that needs to be deliberated upon and possibly altered because as it stands, it is highly confusing and may lead a lot of people to believe that you can't make an Unchained class at all in PCGen.
-** ANSWER: Since that was my decision, I'll be happy to explain the reasoning and how I arrived to that conclusion.  If you do a comparison between the normal classes and the unchained versions, in most cases the only differences was the class features - Monk had a HD boost, Summoner has a Spell List change, Barbarian only changes features, and Rogue added some new features.  It seemed more economical to re-use the base framework which 90% of the classes were built upon. Reduce duplication in code (Each class loaded requires some memory, whereas the method I opted did not increase memory, merely which features to use). Unchained classes comes across as more a variant. Plus, you cannot have an unchained version and regular version of the class. Programming in "Cannot take this" does increase cpu cycles and additional code lines. Add in the fact they were treated just as the regular version in terms of meeting prerequisites for prestige classes, feats, and archetypes, etc.  Looking at it big picture, it made more sense to simply use the base class and treat the unchained variant as a super archetype - swap out abilities. They were more the base class then not. The chance of breaking support was higher if they were coded separately - anything using the code classlevel("Summoner") would fail for an "Unchained Summoner" as an example, SERVESAS only does prexxx support. Reviewing everything related to the class - favored classes, archetype support, feats and the data hacks was a bit more time consuming.  Plus, it gave me the excuse to test out a function of the program to try and support a prestige class that grants class features from other classes, which we could not support in the past.  To combat the confusion, I did include the Summary TO DO to prompt the user to choose which version they want to use; most users use the summary screen to add classes to the character, which would mean they see the prompt right off. Under the hood, it defaults to the base version in case they never make that selection. An important fact for the Summoner - so it still gains spells.  If it helps to know, I went back and forth several times, actually coding them up initially as classes. But the lack of time on my part limited what I was willing to undertake, so choosing the path that had the least chance to break any particular build was what I ended up doing. As I progressed, I learned a new tidbit that swung the pendulum toward the other method. I might have chosen differently knowing what I know today.  Right or wrong, it is a bit late to change the decision (6.06.00 is now released). With our focus for the 6.08 dev cycle to rip out the JEP reliance tags - anything that starts with BONUS:x, anything that is touched by BONUS, such as LEGS, FACE, REACH, WEAPONPROF, etc. Implementing new support for global and local variable numbers, Booleans, strings and orderedpairs. Rip out every text output tag and replace it with INFO/INFOVARS. Redesign the output sheets to (1) use the freemarker template code properly, and (2) switch to grabbing the new output via fact, info and value. The end goal is a more lean and efficient code base and data processing. Hope that helps clear up the decision making process that led to variant vs. class. If you have any other questions, comments or otherwise, feel free to reach out to me. --Andrew Maitland (Content Silverback - PCGen Board of Director's)
+** ANSWER: Since that was my decision, I'll be happy to explain the reasoning and how I arrived at that conclusion.  If you do a comparison between the normal classes and the unchained versions, you will see (in most cases) the only differences was the class features - Monk had a HD boost, Summoner has a Spell List change, Barbarian only changes features, and Rogue added some new features.  It seemed more economical to re-use the base framework which 90% of the classes were built upon. Reduce duplication in code (Each class loaded requires some memory, whereas the method I opted did not increase memory, merely which features to use). Unchained classes comes across as more a variant. Plus, you cannot have an unchained version and regular version of the class. Programming in "Cannot take this" does increase cpu cycles and additional code lines. Add in the fact they were treated just as the regular version in terms of meeting prerequisites for prestige classes, feats, and archetypes, etc.  Looking at it big picture, it made more sense to simply use the base class and treat the unchained variant as a super archetype - swap out abilities. They were more the base class then not. The chance of breaking support was higher if they were coded separately - anything using the code classlevel("Summoner") would fail for an "Unchained Summoner" as an example, SERVESAS only does prexxx support. Reviewing everything related to the class - favored classes, archetype support, feats and the data hacks was a bit more time consuming.  Plus, it gave me the excuse to test out a function of the program to try and support a prestige class that grants class features from other classes, which we could not support in the past.  To combat the confusion, I did include the Summary TO DO to prompt the user to choose which version they want to use; most users use the summary screen to add classes to the character, which would mean they see the prompt right off. Under the hood, it defaults to the base version in case they never make that selection. An important fact for the Summoner - so it still gains spells.  If it helps to know, I went back and forth several times, actually coding them up initially as classes. But the lack of time on my part limited what I was willing to undertake, so choosing the path that had the least chance to break any particular build was what I ended up doing. As I progressed, I learned a new tidbit that swung the pendulum toward the other method. I might have chosen differently knowing what I know today.  Right or wrong, it is a bit late to change the decision (6.06.00 is now released). With our focus for the 6.08 dev cycle to rip out the JEP reliance tags - anything that starts with BONUS:x, anything that is touched by BONUS, such as LEGS, FACE, REACH, WEAPONPROF, etc. Implementing new support for global and local variable numbers, Booleans, strings and orderedpairs. Rip out every text output tag and replace it with INFO/INFOVARS. Redesign the output sheets to (1) use the freemarker template code properly, and (2) switch to grabbing the new output via fact, info and value. The end goal is a more lean and efficient code base and data processing. Hope that helps clear up the decision making process that led to variant vs. class. If you have any other questions, comments or otherwise, feel free to reach out to me. --Andrew Maitland (Content Silverback - PCGen Board of Director's)
 ** Reply back: Thanks for the explanation. Now I understand the process behind the decision a lot more. Might be something to add to the FAQs because other people may also get confused and I admittedly found the Unchained version by accident.
 * Pathfinder vs Pathfinder Society:
 ** QUESTION: What is the difference between these and why should I care?
 ** ANSWER: Pathfinder Society is an actual real world international organization which publishes official rules of play for gamemasters and players alike. The games are run using official modules with completion items given out, special sheets to track rewards and of course a very different XP progression, which is capped well before 20th level. As mentioned before they publish rules each year to tell their members what is legal to use in their games. In essence Pathfinder Society (abbreviated PFS) is a structured event setting which determines what is legal in their games, allowing players from all over the world to have the same experiences and options. Many feats, spells, equipment and class options are restricted in the Pathfinder Society games. PCGen supports the various seasons of play as best we can. Many false bugs are raised due to people mistakenly thinking their favorite options are not working. Rule of thumb, unless you play in this actual society, do not use their rules.
 == How Customizable is PCGen? ==

@@ Line 8: / Line 8: @@
 Our list of supported d20 systems with pre-made books:
 * D&D 3.0 edition (Listed as SRD - System Resource Documents)
 * D&D 3.5 edition (Listed as RSRD - Revised System Resource Documents)
@@ Line 25: / Line 26: @@
 * Cyberpunk
 * Shadowrun
 == How Customizable is PCGen? ==

← Older revision		Revision as of 19:21, 26 February 2015
Line 90:		Line 90:
	** 2) Put the pcgen.cmd file in your C:\program files (x86)\pcgen\pcgen5161\ directory.		** 2) Put the pcgen.cmd file in your C:\program files (x86)\pcgen\pcgen5161\ directory.
	** 3) Change your shortcut link to the pcgen.cmd file.		** 3) Change your shortcut link to the pcgen.cmd file.
		+
		+
		+	=== Mac Installation Issues ===
		+	ISSUE: I have downloaded PCGen for the Mac and I cannot get it to run. If I try to open the application from within the disk image, I get this error message: " “PCGen 6.04.01” is damaged and can’t be opened. You should eject the disk image." If I move the application into the Applications folder on my hard drive, I get this error message: "You can’t open the application “PCGen 6.04.01” because it is not supported on this type of Mac."
		+
		+	SOLUTION: To prevent this error, go to System Preferences -> Security & Privacy. At the bottom of the window there is a section titled: "Allow apps downloaded from:" Then select "Anywhere". That will allow you to open PCGen.
		+
		+	ISSUE: Gatekeeper will not allow PCGen to run
		+
		+	SOLUTION: Disable Gatekeeper, run PCGen, re-enable Gatekeeper. Once PCGen has run once successfully, it's ignored by Gatekeeper.

@@ Line 31: / Line 31: @@
 PCGen has several methods to impart how to create your own custom files. First, we supply a sample folder including a full set of pcc and lst files for you to get started. We have extensive documentation in the program, and maintained on our website. Andrew Maitland has made several youtube videos explaining how to craft the files, and the common mistakes to avoid. Finally, we offer online support via our Yahoo Groups and direct help from our Support Desk Monkey - Help@PCGen.Org.
-== Is there support for problems? ==
+== Is there support for issues and recommendations? ==
 Yes, PCGen is a volunteer project run by monkeys and humans. We all know monkeys are a laugh, and humans are fallible. Thus, we have a Ticket Support system that is monitored by the various projects that go towards supporting PCGen. Our ticket support system is called 'JIRA' and anyone can log into the system after creating an account, and report a problem "Bug" or make recommendations for improvements (Feature Requests). The system is located at http://jira.pcgen.org.

@@ Line 1: / Line 1: @@
 This is just some tips to help along. It'll be a repository of Frequently Asked Questions and Help Tips that we've encountered a lot.
-== Java 7 ==
+== What is PCGen? ==
 PCGen versions prior to 5.17.11 (including the current production version, 5.16.4) are not compatible with Java 7. This is now the default version Java installed for most system types. Open JDK 6 on Linux exhibits the same problems and the same fix applies.
-=== Symptoms ===
+==== Symptoms ====
 When you start PCGen, all character tabs other than the summary tab are blank (i.e. the table outline is there but there is no table displayed and thus no races, classes, equipment etc. can be seen). The advanced sources tab is also empty.
-=== Fix ===
+==== Fix ====
 There are two options to fix this:
 # Install Java 6 and ensure PCGen uses that (may require downgrading
@@ Line 15: / Line 70: @@
-== Windows Installations ==
+=== Windows Installations ===
 * Vista & Win7 (32 & 64 versions) Install and Running
 ** If you are running 64-bit versions of Vista or Win7, the bat file may not find JAVA. You may have to hard-code the path to java.exe. To edit those either Right Click on my Computer -> Properties -> Advanced System Settings -> Environment Variables OR Control Panel -> System -> Advanced Syystem Settings -> Environment Variables.
@@ Line 37: / Line 92: @@
-==Homebrew OS Sheet for working 5.17.16 and forward ==
+=== Homebrew OS Sheet for working 5.17.16 and forward ===
 As part of an improvement to Display all the Allowable Range Increments properly for Thrown and Ranged Weapons, some changes were made to the BASE.XML file and the reliant XSLT files. Sadly, this change '''will''' break home-brew OS sheets going forward.
@@ Line 63: / Line 118: @@
-==Changing a Character's Sources==
+=== Changing a Character's Sources ===
 Sometimes you may need to change the sources a character is associated with, you could be adding a new source book you have started using or removing a book that is unused. Here's how to do it: