Hello,
When i want to install the parser, the program stop directly after I click on "Install" :(
If you have an idea for my problem :)
S.
Printable View
Hello,
When i want to install the parser, the program stop directly after I click on "Install" :(
If you have an idea for my problem :)
S.
I haven't seen this error before. The installer is a Standard Visual Studio installer, which will require .NET (which is usually installed if it is not present).
You might try searching the Internet for the error/s you're getting to see if there is a solution to your issue. Sorry I can't be more help.
I've checked over this one guy several times but can't seem to find where the error is.
What does this error mean?
Is there a bad character in there somewhere that I can't see somehow?Code:4/5/2016 10:53:18 AM: ReadWriteFormattedCreature: Error Message: System.ArgumentException: '', hexadecimal value 0x1F, is an invalid character.
EDIT: Weird.. this line.. was bad:
Melee mwk greataxe +5 (1d12+4/3)
Ooo.. lookie there... when I paste it here.. a weird character shows up between the / and the 3.. it was invisible in notepad. Hrm.
A lot of Paizo's PDFs don't use an ASCII 'x' for the character in front of crit multiplier, but rather use an extended unicode character that looks similar, but has a different numeric value, messing up the parser. I've seen the same for hyphen, apostrophe and quote marks as well. I usually sanitize the entire text file after I'm done pasting in all the stat blocks by doing a search and replace for each of these. If you use notepad++ you can change the character set from UTF-8 to ASCII which makes these weird characters show up in their hexadecimal form making them easier to pinpoint.
Highly recommend downloading and using notepad++, it's a much superior plain-text editor.
Sorry if this buried somewhere in the thread, but I didn't want to read all 28 pages.
Should I be using this, or the npc statblock import in the advanced bestiary?
Also, is there a hotkey based method for pasting plain text when using windows, or an app that can strip it directly from the clipboard ( also preferably with a bindable hotkey)?
more like ctrl-c to copy followed by ctrl-shift-v to paste plain text stripped of formatting, since the clipboard in windows will maintain it. or like ctrl-alt-shift-v to remove formatting and convert to ascii encoding.
there are good plugins for chrome to both convert to ascii on copy and remove formatting, but when copying out of old pdf's with weird encodings something that modifies the clipboard directly would be most efficient
The advantages of the advanced bestiary is that you can use it in game if you need to, and you get a bit more feedback on what might be causing any parse issues.
The advantages of this parser is that it will give you a much more detailed output - especially if the creature uses spells/special abilities. And it's free. It can take a little bit of getting used to making sure you have the right format (usually the fault of the source statblock not conforming to Paizo standards). But most regular PF GMs on these forums swear by this parser.
If you already have the advanced bestiary, fire it up and give it a go and see if it works for you. If you don't have it, there is some info in the links in this post: https://www.fantasygrounds.com/forum...l=1#post196265
Either way, definitely give this parser a go - it's ideal for preparing a bunch of creatures in advance, and fantastic for getting all of those beasties out of a PDF scenario and into FG.
Cool, thanks. I just bought the advanced bestiary this week and have been using it. There's a learning curve for sure, but I'm a devops by day so I get what's going on in the background. Makes it a bit easier to grok. Are the guidelines you have in the first few posts, in terms of tips and formatting blocks the same for the AB NPC parser? Is there like, a reference doc or spec the logic in each of these parsers? I'll be giving this a go on my next module, as I bought the AB before I knew about this product (to help me get through the current module)