5etools importer is largely dysfunctional

[dralois]

Check for existing bug reports before submitting.

• [x] I searched for existing Bug Reports and found no similar reports.

Expected Behavior

When importing stat blocks from 5etools json, the resulting stat blocks should have their tags replaced with text, should have complete spell lists and all traits & actions should be in the stat block. They should reflect the actual stat block as it is on 5etools:

Current behaviour

When importing stat blocks from 5etools json files, the resulting stat blocks are incomplete (a combination of spells, traits, actions are usually missing) and have untranslated tags. In this example, tags such as the attack roll text in the faerie dust action are not transformed, several spells are missing in the spell casting section and the "Burst of Wonder" bonus action is completely absent.

Reproduction

Import Pixie Wonderbringer.json into Obsidian. Render the stat block in a file.

Which Operating Systems are you using?

• [ ] Android
• [ ] iPhone/iPad
• [ ] Linux
• [x] macOS
• [x] Windows

Obsidian Version Check

1.8.10

Plugin Version

4.9.1

Confirmation

• [x] I have disabled all other plugins and the issue still persists.

Possible solution

The json scheme has likely changed since it was implemented and thus the importer needs to be updated.

[ObsidianTTRPGProject]

@dralois this is a feature that is largely not used anymore since the introduction of the CLI tool which creates notes from 5eTools. I would recommend you have a look at that.

[dralois]

Yeah I found the discussion after opening the issue and am now using that instead.

Since it is a bug and may help other people I'll leave the issue open.

[erlioniel]

@ObsidianTTRPGProject I wouldn't say anything, but actually what you refer is far from being trivial for any normal user, unsure why 5e.tools import can't be fixed really.

[matthttam]

#510 I started a pull request that has some change to help get 5e.tools imported items working properly. I too was trying to use it because the CLI application wasn't very clear as to what it really did and ran into issues.