We are moving away from natural language parsing. A better solution is on the books, just haven't completed it yet and there is no ETA.
Printable View
We are moving away from natural language parsing. A better solution is on the books, just haven't completed it yet and there is no ETA.
I see. OK, thanks for the information. I'll keep working on the conversion then, see where the holes are, report any other bugs that may or may not be fixed soon, and then decide how to proceed from there :).Quote:
Originally Posted by superteddy57
Cleric class has bard stuff going on....
Attachment 62559
Another bug with the parser. For creatures like the Chol Czol that have a "melee or ranged" attack (the dagger in this case), the parser sees this as a ranged attack only. This means they have disadvantage when stabbing someone with a dagger in the automation.
Groups of immunities and and resistances seem to be being ignored.
Example: Undead Resilience -
Should be immune to poison. Specters are still receiving full poison damage when applied.
Should be immune to the poisoned condition. You can still apply it.
Looking again at the specter, in addition to ignoring the resilience groups, there seems to be a data entry issue. It has a lot of condition immunities in the damage immunity section.
Another parser bug.
Doesn't look like ability and skill checks are being parsed correctly.
Ambush Hag - Mimicry has DC 16 WIS (Insight) check not being picked up. Same if I remove the (Insight).
With statblock set to "ToV" NPC's still do not have a condition resistance field. This is something ToV has. ToV also has condition vulnerability.
Spellcasting isn't being parsed quite right either.
Lizardfolk Shaman:
"...using WIS as the..." seems to be being ignored. It's cure wounds in the tracker is only getting a 1d8 not a 1d8+5
NPC's are missing XP values in the monster vault. Which makes sense, since ToV doesn't use XP. However the encounter window won't refresh the challenge rating of encounter (leaving it empty) unless the NPC's are given an XP value.
workaround solution would be to enter in the XP values for the appropriate CR's...however Encounter building is a little different in ToV than 5E (either 2014 or 2024). XP doesn't come into play, so maybe when using ToV as the ruleset the encounter window could calculate differently?