Ammunition/Arrows/Bolts are not currently an option in the homebrew item system. If I base a new item on +1 Arrow or Arrow of Slaying, the weapon subtype is blank, and DnDBeyond will not allow me to save the item with the field blank. There is no weapon subtype for ammunition. The current best solution seems to be to call them wondrous items but then the equipment manager does not allow me to track a quantity.
See, for example, my public homebrew items Arrow of Exploding, Arrow of Paralysis, and Arrow of Confusion.
This is something that is actually on the roadmap. You can see the D&D Beyond feature requests here: ddb.ac/feature-requests. The workaround that I use is create a homebrew bow with the number of charges equal to the number of special ammunition that you're currently carrying. It's not ideal, but it does get the job done. Hope this helps.
Yeah, I found the "main thread" for this subject after I wrote this. I found the same solution you suggest, and it seems like the best workaround for now :)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Ammunition/Arrows/Bolts are not currently an option in the homebrew item system. If I base a new item on +1 Arrow or Arrow of Slaying, the weapon subtype is blank, and DnDBeyond will not allow me to save the item with the field blank. There is no weapon subtype for ammunition. The current best solution seems to be to call them wondrous items but then the equipment manager does not allow me to track a quantity.
See, for example, my public homebrew items Arrow of Exploding, Arrow of Paralysis, and Arrow of Confusion.
I would like to see this as well.
I'm setting the Base Item Type to Item and the Magic Item Type to scroll, just so I don't have an item for each arrow.
This is something that is actually on the roadmap. You can see the D&D Beyond feature requests here: ddb.ac/feature-requests. The workaround that I use is create a homebrew bow with the number of charges equal to the number of special ammunition that you're currently carrying. It's not ideal, but it does get the job done. Hope this helps.
Yeah, I found the "main thread" for this subject after I wrote this. I found the same solution you suggest, and it seems like the best workaround for now :)