Importing Stat Blocks from Text 5e

Doesn't look like the Shaped sheet/api or the Stat Import api are working anymore. I have text NPC stat blocks that I would like to import into new NPCs. Is there a method or updated API that will work get allow me to quickly add my content to the character sheets instead of manually entering/copy/pasting? This really shouldn't be this hard folks.

Robert V. said: This really shouldn't be this hard folks. I cannot write API, so perhaps it really IS that hard?  I really have to thank all the API folks that do put in the very hard work of writing the API scripts that I and others enjoy.  Perhaps acknowledging their effort will get you a better response than telling them it isn't difficult?

As someone who has written several statblock parsers. Yes, it really is that hard. This isn't quite natural language parsing (which you really need machine learning for), but it's about as close to it as you can get without needing machine learning. Even the most organized statblocks are actually extremely disorganized over the spectrum of possible use cases. Compare the 5e statblock of an Ancient Dragon, an Archmage, and a simple goblin. They each follow the same form, but are drastically different. Parsing actions and abilities is particularly difficult in 5e statblocks because it's mostly text formatting that separates one action from another action, or one trait from another trait. Unfortunately, this formatting is lost in any format that could be easily presented to the API or character sheet. And, as Gauss said, being polite in your request is more likely for someone to actually help you. This is especially true when it's community built, free functionality you are complaining about.

To be fair - my grousing is aimed at the Roll20 team for making this difficult.  Very grateful to the folks who take a stab at it  - but as Roll20 makes changes it blows up those efforts.

Can't agree there. Roll20 does what it needs to do to make things work. Subsidiary projects like import tools need to do the heavy lifting here. The last thing I want is for Roll20 to worry about breaking someone's third party product. That's on the maker of a third party product.  GIMP needs to learn how to open recent version Photoshop files, not the other way around.