4E Item Parser

[valeros]

I put a new version (4eParser_2014_0201.zip) on the first post. There is now a button to the right of "Add Entries" called "Add All Books to Source". If you have already selected "Select Compendium Entries" and have waited for the page to finish loading, you can then use this button to add all the Source Book options to the "Source" filter. This adds all books, not just the relevant ones. Also, if you use this, you must have the "All Source Books.txt" file in the same directory as the parser (just like it requires the "Power Classes.txt" for powers.) You only have to use this button once, not each time you go to a new tab.

[Griogre]

Thanks Valeros, I'll try this.

[br0k30n3]

I put a new version (4eParser_2014_0201.zip) on the first post. There is now a button to the right of "Add Entries" called "Add All Books to Source". If you have already selected "Select Compendium Entries" and have waited for the page to finish loading, you can then use this button to add all the Source Book options to the "Source" filter. This adds all books, not just the relevant ones. Also, if you use this, you must have the "All Source Books.txt" file in the same directory as the parser (just like it requires the "Power Classes.txt" for powers.) You only have to use this button once, not each time you go to a new tab.

This is awesome , Thanks Sir

[spike1288]

Hi i have used the new updated parser on the players hand book with nps at all, when it came to parsing the dungeon masters stuff i got this error when i loaded up fantasy grounds so it wont load in the modules section

Database Error: A XML parse error occurred processing file 4E Dungeon Master's Guide:db.xml - Error on line 306486: Error reading end tag.

if someone could please help me fix this it would be awesome thank you for your time
Spike

[LootaBox]

Hey! There seems to be a bug with the new version, that causes a whole bunch of source book filters to appear, and none of them actually work as far as I can tell. Happens if you search for whatever, click something, so you open up a popup with login confirmation, and then detailed information about whatever you just clicked on. When you close that the filter is messed up.

It doesn't really bother me, since I can just open the compendium on a regular browser at the same time. And thanks, really, for an awesome parser!

This is a bit off topic, but as far as I know varelos has no plans to incorporate familiar, companions or summons parsing to his parser, and the other parser doesn't support companions or summons either. Is there a parser that does?

[br0k30n3]

Hi i have used the new updated parser on the players hand book with nps at all, when it came to parsing the dungeon masters stuff i got this error when i loaded up fantasy grounds so it wont load in the modules section

Database Error: A XML parse error occurred processing file 4E Dungeon Master's Guide:db.xml - Error on line 306486: Error reading end tag.

if someone could please help me fix this it would be awesome thank you for your time
Spike

I got the same issue, I have even attempted to package the Module manually , getting the same result

[valeros]

So I do not have my DDI subscription anymore, so hard for me to troubleshoot. To my knowledge, the only change to the most recent parser was for the "Source" option. Nothing else should have changed. And to my knowledge, no data in the Compendium should be changing since I do not think WoTC is updating that anymore. If you parse the downloaded data file (i.e., do not download the data again) with the oldest parser still posted, does the error still happen? If so, that probably means something changed in the data or the data downloaded incorrectly (although that does not seem likely since multiple people are having the issue.) If not, then it is the parser. But if that is the case, you should now have a working module. Another option is to try one of the older parsers and download all the data again. But if the previous step did not work, this is not likely to work either.

[br0k30n3]

So I do not have my DDI subscription anymore, so hard for me to troubleshoot. To my knowledge, the only change to the most recent parser was for the "Source" option. Nothing else should have changed. And to my knowledge, no data in the Compendium should be changing since I do not think WoTC is updating that anymore. If you parse the downloaded data file (i.e., do not download the data again) with the oldest parser still posted, does the error still happen? If so, that probably means something changed in the data or the data downloaded incorrectly (although that does not seem likely since multiple people are having the issue.) If not, then it is the parser. But if that is the case, you should now have a working module. Another option is to try one of the older parsers and download all the data again. But if the previous step did not work, this is not likely to work either.

I looked at the XML file that it made, I didn't see anything that looked off, Possibly because to the size or number of entries ? I'll try to use it and do it for each course separately. I was having issues prior to the new update with the DM entries, just didn't dive into it with any depth until now.

[xKrisx]

So every time I try and scrape the creatures info using the Parser I get a 'Database Error: A XML parse error occurred processing file Monsters:db.xml - Error on line 239812: Error reading tag.'

What is going on and how is that fixed? I can parse everything in the DM compendium except the Creature entries. Any help would be awesome.

[Trenloe]

So every time I try and scrape the creatures info using the Parser I get a 'Database Error: A XML parse error occurred processing file Monsters:db.xml - Error on line 239812: Error reading tag.'

What is going on and how is that fixed? I can parse everything in the DM compendium except the Creature entries. Any help would be awesome.

There is an XML format error in the monsters db.xml file - this will be caused by some issue in the data downloaded from the DDI website. It can sometimes be possible to identify what the error is and manually modify the db.xml file and then run this through the parser again (don't re-scrape from the website).

Open the file in an XML enabled editor (Notepad++ for example - which is free) or a XML validator website such as this: https://www.w3schools.com/xml/xml_validator.asp Although the website may not be able to process such a large file. These may help you to identify where the XML error is and fix the issue. The problem is that sometimes the line where the error is reported is not where the error occurs...

If that doesn't work for you, try posting some of the data here - perhaps 20 or so lines either side of line 239812 to see if it is something obvious. If you're not sure where that line is, open the file in Notepad++ (https://notepad-plus-plus.org/) which will show you the line numbers.