The Homebrew Item Creation flow includes a field for "Attunement Description." Once the item is created, text entered into that field shows up as: "requires attunement by a [whatever]." The "a" in "requires attunement by a" is hard-coded -- which causes a grammar problem when the word that follows the "a" starts with a vowel. There's no way to turn the "a" into "an."
For example, if I'm creating a homebrew moonblade, the attunement description needs to read "requires attunement by an elf..." But the hard-coded "a" means the attunement description has to read either "requires attunement by a elf" or "requires attunement by a n elf," with the "n" separate and floating.
The easiest fix is probably just to delete the hard-coded "a" and let users supply it in their Attunement Description fields.
Understood and I bumped into this a couple of times when creating my own homebrew.
For now, I suggest just phrasing your attunement text differently, so you could have, "Requires attunement by a character of Elven race," or something similar to that.
It's been nearly two years that this thread has been open. Any chance that this is being addressed at some point? Perhaps the "by a" component can just be removed and replaced by a ":" or a "-"? That would alleviate the grammatical issue altogether.
This is still an issue for me, and also, sometimes I don't want to put anything in that field. Many published items simply say "Requires attunement" and there's no "by..." at all.
I wonder if some folks are unknowingly in a 'Beta' of sorts and others aren't? Just like @Davedamon, I was able to create an item, click Requires Attunement and hit Create without any issues. The little red required indicator (*) shows on the field, but it doesn't seem to make any difference. I'm using a Chrome browser... maybe it's a difference in that? :shrug:
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The Homebrew Item Creation flow includes a field for "Attunement Description." Once the item is created, text entered into that field shows up as: "requires attunement by a [whatever]." The "a" in "requires attunement by a" is hard-coded -- which causes a grammar problem when the word that follows the "a" starts with a vowel. There's no way to turn the "a" into "an."
For example, if I'm creating a homebrew moonblade, the attunement description needs to read "requires attunement by an elf..." But the hard-coded "a" means the attunement description has to read either "requires attunement by a elf" or "requires attunement by a n elf," with the "n" separate and floating.
The easiest fix is probably just to delete the hard-coded "a" and let users supply it in their Attunement Description fields.
Understood and I bumped into this a couple of times when creating my own homebrew.
For now, I suggest just phrasing your attunement text differently, so you could have, "Requires attunement by a character of Elven race," or something similar to that.
I know it's not ideal, but a suggestion for now.
Pun-loving nerd | Faith Elisabeth Lilley | She/Her/Hers | Profile art by Becca Golins
If you need help with homebrew, please post on the homebrew forums, where multiple staff and moderators can read your post and help you!
"We got this, no problem! I'll take the twenty on the left - you guys handle the one on the right!"🔊
It's been nearly two years that this thread has been open. Any chance that this is being addressed at some point? Perhaps the "by a" component can just be removed and replaced by a ":" or a "-"? That would alleviate the grammatical issue altogether.
Just wanted to say that as far as I know, this still hasn't been fixed and if there is a way around it I can't find it.
This is still an issue for me, and also, sometimes I don't want to put anything in that field. Many published items simply say "Requires attunement" and there's no "by..." at all.
You can leave the field blank and it won't display any requirement in that item, just that it needs attunement
Find my D&D Beyond articles here
It's a required field, so it gives me an error.
I just made an item, ticked 'Requires Attunement' and left the 'Attunement Description' field blank and hit save:
I was able to save the item just fine, which gives an item with non-specific attunement
Find my D&D Beyond articles here
Interesting. I recently made an item for my campaign and tried to leave it blank like Fruitbat did. I too got an error.
I wonder if some folks are unknowingly in a 'Beta' of sorts and others aren't? Just like @Davedamon, I was able to create an item, click Requires Attunement and hit Create without any issues. The little red required indicator (*) shows on the field, but it doesn't seem to make any difference. I'm using a Chrome browser... maybe it's a difference in that? :shrug: