![]() ![]() Our forums have transitioned from Yahoo Groups to groups.io which are free and will continue ( ), our discord channel will continue ( ) as long as there are people talking there, our old & broken wiki will be availible ( ), our Friends of PCGen FB page will continue ( ), and there is also a sub-reddit ( ) If anyone wishes to they can take a look at the code here ( ). Our website will remain up until such as a time that the host decides to quit maintaining it. We have had a fine 20 year run from the heady days of Bryan releasing hourly, then daily code updates, to the original D&D 3e SRD being released, through the choppy waters of getting hammered by WotC's refusal to consider the non-SRD info being included (prompting the formation of the separate corporation, Code Monkey Publishing), through the explosion of third party materials causing PCGen's code base to grow by leaps and bounds, though the formation of the 4e and the simultaneous rise of Pathfinder, Starfinder, and now the release of Pathfinder 2e. ![]() But again Andrew was the driving force and repository of why things were done the way they were. The Data team is in better shape because the data is generally easier for new users to start with. And the expected new math library to replace the woefully outdated JEP has never been able to get fully implemented (see above). The core Code Team have had attrition due to RL and nobody willing (or able) to pick up the code and run with it, and without the old time members to explain the code things are continually breaking, gating the releases. ![]() The core reasons for the project going dormant are the same as have been stated multiple times in the last year. We hope this is accomplished by the end of the year (2019) Paul Grosse the PR director will hang around and provide advice to anyone attempting to keep the project alive, but will also be limiting his involvement. As of the release of the Pathfinder 2 datasets for 6.08.00 RC7, Andrew Maitland, the Data Lead (the core driving and unifying member of the BoD) will be ceasing any ongoing upkeep and direct involvement with the project. ↳ D&D 3.It is with sad news the core team members of the PCGen BoD are stepping down (or handing off the reins to any new blood that wish to take up the challenge).↳ Tilesets, Token Libraries, and Complete Maps.I'm almost thinking that Lib:tokens should be exported when the campaign properties are exported. ![]() Oh, if you choose a token for your "template" that simply makes calls to a Lib:token, your macros won't have to change when the campaign properties do. Every campaign is likely to have different properties assigned, so not much else can be done. It then reads the rptok and replaces the sections with the XML, then adds the images.Īlthough thinking about it, the only stuff that's practical to import is the basic stats: ability scores, skills, and so forth. Perhaps the easiest way to handle this is for your import function to accept an existing rptok, an XML file, and one or two PNG images (token and portrait). However, I don't doubt that we'll soon have a way to do a multi-select drag-n-drop of macros from one token to another (hint, hint) so copying macros around won't be so much trouble. Usefulness of macros is directly related to the campaign properties, so there's not going to be a single good token to use as a template. Now will work on the xml sheet for PCgen since I think that it could be nice to use the one coming from Pathfinder.Īny suggestion on a ideal general token to use (one with the most of usefull macro)? ![]()
0 Comments
Leave a Reply. |