javalent / fantasy-statblocks

Create Dungeons and Dragons style statblocks for Obsidian.md
MIT License
352 stars 71 forks source link

šŸž Stat blocks with monster feature display blank in creature pane. #401

Open MattGRMP opened 5 months ago

MattGRMP commented 5 months ago

Check for existing bug reports before submitting.

Expected Behavior

name: Armored Acolyte
monster: Acolyte
ac: 20

The above statblock displays correctly in the note it is written. statblock: inline is in the frontmatter so that it is added to the bestiary. When searched in the creature pane it should look the same as in the note, pictured below. image

Current behaviour

The creature pane does not display the data that should be inherited from the monster feature. The only part of the statblock that displays correctly is the AC. image

Reproduction

  1. Launch Obsidian Sandbox via the 'Open Sandbox Vault' command.
  2. Install the Fantasy Statblocks plugin and enable it.
  3. Create a new note.
  4. Paste the following into the new note
    
    ---
    statblock: inline
    ---
name: Armored Acolyte
monster: Acolyte
ac: 20

5. Run the Fantasy Statblocks: Parse Frontmatter for Creatures command
6. Open the creature pane and search for Armored Acolyte. It will contain a statblock with 20ac and no other stats.

### Which Operating Systems are you using?

- [ ] Android
- [ ] iPhone/iPad
- [ ] Linux
- [ ] macOS
- [X] Windows

### Obsidian Version Check

1.5.12 and 1.5.3

### Plugin Version

4.2.4

### Confirmation

- [X] I have disabled all other plugins and the issue still persists.

### Possible solution

_No response_
MattGRMP commented 5 months ago

Statblocks created with monster feature present the same issue if you try to extend them. This can be seen by creating a new note and using the below stat block to extend the Armored Acolyte from the example.

---
statblock: inline
---

```statblock
name: Armored Acolyte Variant
extends: Armored Acolyte
speed: 100ft

![image](https://github.com/javalent/fantasy-statblocks/assets/140577176/df1da7b5-522b-45bd-bb8a-ca518ee0cf83)
addiebarron commented 3 months ago

Still running into the issue on my end too -- doesn't look like the above fix ^ addressed it.

MattGRMP commented 3 months ago

Still running into the issue on my end too -- doesn't look like the above fix ^ addressed it.

I am also still able to reproduce this issue, now using Obsidian v1.6.3 (installer version v1.5.3), and fantasy statblocks v4.4.2. I followed the same steps as in my original report.