Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: "monster" field overwrites "name" field #243

Closed
3 of 7 tasks
Tamei opened this issue Jul 14, 2023 · 1 comment · Fixed by #249
Closed
3 of 7 tasks

[Bug]: "monster" field overwrites "name" field #243

Tamei opened this issue Jul 14, 2023 · 1 comment · Fixed by #249
Assignees
Milestone

Comments

@Tamei
Copy link

Tamei commented Jul 14, 2023

Check for existing bug reports before submitting.

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

Expected Behavior

The following code sould render a statblock containing all stats of an "Undead", but with the name "Bloated Corpse":

```statblock
monster: Undead
name: Bloated Corpse
```

The "Undead" is available in the Bestiary:

Screenshot 2023-07-14 185846

Current behaviour

The statblock gets rendered and instead of "Bloated Corpse", the name gets set to "Undead":

grafik

Reproduction

  1. Make sure that you have a folder configured to automatically scan for Bestiary entries in
  2. Create a new note with name A in this folder and paste the following text into it:
---
statblock: true
name: A
---
  1. Open the settings of the plugin and make sure that A was added to the bestiary
  2. Create a new note with name B outside the folder and paste the following text into it:
```statblock
monster: A
name: B
```
  1. The statblock is not rendered with name B but A.

Which Operating Systems are you using?

  • Android
  • iPhone/iPad
  • Linux
  • macOS
  • Windows

Obsidian Version Check

1.3.5

Plugin Version

3.6.7

Confirmation

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

Possible solution

No response

@sigrunixia
Copy link
Member

This is afflicted by the same bug as #224 and #228. Tracking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants