Fantasy Grounds 5E Parser

UI creation for Classes and NPC's is practically done, I may take a look at reference section or the story section next. The goal of my parser is simple and has 3 main corner stone functions

1) It has a UI to aid any users with the markup (either applied or automatic)
2) It supports existing RAW files that were used for par5e (Apart from #ZAL links everything else should be the same)
3) To keep up with FG's ever changing goodness! (If something like this is even possible lol)

Where the code is concerned I have used Strongly typed classes since it really helps a lot when building the XML's required for the modules.

UI for classes has been released! User guide included in the .RAR.

Front page has been updated accordingly. Enjoy folks!

UI for classes has been released!
Thanks.

I seem to have stumbled upon a problem... The #abh; tag which basically indicates that the line is a Archtype Name gets placed on the last feature before it, so in other words the last feature of that class does not parse properly. You can see the feature name however when you click on it you cannot see the feature description.

Immediate walk around can be to simply edit the word file and shift #abh; to the next line.

Happy parsing!

I get an error when trying to parse a class file with a cleric class. The file parses fine with Par5e.
Attachment 16468

Thanks for any help

(The german message means: Index out of array-range)

Okay here are some things you can check initially.

First thing would be to make sure there are no line breaks between the text of the classes. The only line break should be to differentiate between two classes.

Make sure all your features and ability features have proper levels assigned to them.

Edit : remove any zal zl type links as well from the input file.

Quote:

---

Originally Posted by Thegroo

I get an error when trying to parse a class file with a cleric class. The file parses fine with Par5e.
Attachment 16468

Thanks for any help

(The german message means: Index out of array-range)

---

Ok found that one: an #abf was missing the level

Found a bug/feature:

If there is a ' in a feature-name, it wont parse.

Bye the way, thanks for your work

Alright I'll look into that, would just need to add ' to the list of things to convert.

Quote:

---

Originally Posted by Thegroo

Found a bug/feature:

If there is a ' in a feature-name, it wont parse.

Bye the way, thanks for your work

---

It seems to work for me, I've checked it on

Feature Name
Archtype Name
Ability Feature Name

In all the three cases I have had it correctly parse.

Can you share a screen shot of whats not working for you so that I can try to replicate it?