Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Does anyone still play Pathfinder? Any working option to import NPC statblocks?

I used to use CreatureGen years ago, but it seems as the Pathfinder Community Sheet and other elements of the framework evolved, that API has become unreliable for all but the most basic of statblocks.  Is there any time-saving method to import statblocks that still works as intended?  I know we have the compendium now, but that is comparatively limited and harder for me to make small edits to outside of roll20 while I'm prepping.
1618552341
vÍnce
Pro
Sheet Author
You can use the Pathfinder Companion Script (pro perk) with the PF Community sheet to import a text-based copy from the srd.  PFC is available from the API one-click install page. 
Thanks Vince.  I had tried to use that alternative as well, but haven't been able to do so successfully.  I have tried posting very simply SRD blocks to both a token's GM notes and a new character sheet's GM notes, pulling the character ID, and running !pfc --parse|- asdasdadasdasd (whatever the ID is).  Would you be able to confirm whether this feature of the script actually still works?
1619397403

Edited 1619397856
vÍnce
Pro
Sheet Author
I couldn't get !pfc --parse|character_id to work... ;-( but try using !pfc --parse|{{ <PASTE THE SRD STATBLOCK HERE> }}  I noticed the creatures name and CR were combined when I pasted into a text editor. ie "CLOAKERCR" If left this way, it seemed to break the import.  I added a space between the name and CR and the import worked. I'll let Scott(script author) know there may be an issue with the parse using gm_notes/character_id method. Cheers
1619410267
vÍnce
Pro
Sheet Author
Looks like there was a change a few years back that causes a conflict with how the API parses GM Notes.  Not sure if this can be fixed.