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 .
×
Advertisement Create a free account

Is it just me or the pathfinder companion API is broken?

Hey everybody! I just came back to DMing after a break of a few months and I noticed that the API giving me messages that the version I'm using isn't compatible. Naturally I went to google to see if anybody here or anywhere else spoken up about it and if there's a solution or an update but nothing I could see so I tried to work with it anyways. I tried to parse a statblock and while it did create a new sheet for me it I noticed it missed all the information. It created new abilities and spells but they were empty. For some reason however, it did paste all of the information to the parsing tool in the NPC tab (which is always up btw, even when the sheet is not NPC checked.) so I reviewed it and clicked parse and it parsed everything correctly, however, the empty spells and abilities are still there. That API is really old and doesn't seem like it's going to get updated any time soon and with the pathfinder community sheet being version 1.798 I think it's going to be completely broken soon. Are there other people who use this API? I didn't see anybody say anything about this nor other problems I had with it as of late and it's saddens me. Perhaps there's something superior and this is why this API is neglected?
1633794802
Scott C.
Forum Champion
Sheet Author
API Scripter
Compendium Curator
Hi Nevela, I apologize for the inconvenience. I've gotten a few other reports of the parser not working. I'm working on some script improvements and improved sheet integration, but I'm a little busy at the moment, so it's slow going.
Scott C. said: Hi Nevela, I apologize for the inconvenience. I've gotten a few other reports of the parser not working. I'm working on some script improvements and improved sheet integration, but I'm a little busy at the moment, so it's slow going. I understand that, and I mean no disrespect when I say that I've messaged you privately about something more than half a year ago and still the API hasn't seen an update in 3 years. In general when I look at APIs it seems that it's been years since the last update and I can't speak for everybody but some of the people I know don't want to use API because they don't trust scripts that haven't been updated in years.  A huge part of being a pro account is API and seeing the APIs in this state kinda makes me think that it doesn't worth the money. Thank you for your reply, I hope this will be updated.
1633849986

Edited 1633902019
vÍnce
Pro
Sheet Author
The NPC tab always showing is apparently a bug I introduced in the last sheet update...&nbsp; ;-( Very sorry.&nbsp; I'll try and get that fixed up ASAP. Curious, if you see the statblock info posted in the the "Monster statblock import" on the NPC tab and hit the Parse button, does that seem to do anything? edit: PR for npc tab <a href="https://github.com/Roll20/roll20-character-sheets/pull/9608" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/9608</a>
vÍnce said: The NPC tab always showing is apparently a bug I introduced in the last sheet update...&nbsp; ;-( Very sorry.&nbsp; I'll try and get that fixed up ASAP. Curious, if you see the statblock info posted in the the "Monster statblock import" on the NPC tab and hit the Parse button, does that seem to do anything? edit: PR for npc tab <a href="https://github.com/Roll20/roll20-character-sheets/pull/9608" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/9608</a> Sorry for the late reply. Yes, as I mentioned above, all the information from the statblock is pasted to the monster statblock import and when you click parse it parses the information and creates everything the statblock has. So it works, it just requires me to go through extra steps.
1634058765
JP
Pro
Interesting. Piggybacking onto this conversation since this seems to be a similar error to the statblock importer the 5e shaped companion script is having, but you are able to somehow solve the issue here.&nbsp; I wonder if there is a clue to fixing it for the script I use somewhere in this script. <a href="https://app.roll20.net/forum/post/10191536/does-anyone-still-use-the-5e-shaped-sheet/?pagenum=2" rel="nofollow">https://app.roll20.net/forum/post/10191536/does-anyone-still-use-the-5e-shaped-sheet/?pagenum=2</a>
1634081925
vÍnce
Pro
Sheet Author
Nevela said: vÍnce said: The NPC tab always showing is apparently a bug I introduced in the last sheet update...&nbsp; ;-( Very sorry.&nbsp; I'll try and get that fixed up ASAP. Curious, if you see the statblock info posted in the the "Monster statblock import" on the NPC tab and hit the Parse button, does that seem to do anything? edit: PR for npc tab <a href="https://github.com/Roll20/roll20-character-sheets/pull/9608" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/9608</a> Sorry for the late reply. Yes, as I mentioned above, all the information from the statblock is pasted to the monster statblock import and when you click parse it parses the information and creates everything the statblock has. So it works, it just requires me to go through extra steps. Scott is WAY more qualified to comment on this..., but given that you can finish parsing after an import from PFC using the sheet's parse button, there may just be an issue (roll20, PFC, and/or the sheet) in triggering the appropriate events.&nbsp; Since neither the sheet's NPC parser function or the PFC script has changed in three years, there just may be "something" that's changed on roll20.&nbsp; What that is, I really have no clue. This also might explain the 5e companion import breaking as well... If all that is needed to complete a statblock import from PFC is to trigger the sheet's parsing event, maybe that could simply be added to PFC as a quick/temp fix?&nbsp; (Scott?)