It's supposed to do +1d6 bludgeoning damage per level above 2, but no matter how many times I tweak and save the spell, it does not show this on a character sheet. Am I doing something wrong, or is it just bugged?
Be sure that you Save Changes at the main edit page for the homebrew after you make a change. Also, it might take up to 20 minutes for the changes to percolate over to the character sheet.
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
After you change/add/remove a modifier you MUST re-save the entire homebrew using the main [SAVE CHANGES] button under Basic Information or the system won’t pick up your changes. After that it takes 20 minutes. You might need to “wake up” your character sheet by adjusting the level up and down again.
Also, just to point it out the spells description makes absolutely no mention of dealing more damage at higher levels.
However, now that the spell has been published you within need to “create new version” and the old version will haunt your homebrewer forever. It is best practice to not publish anything until it is guaranteed working correctly.
Again, NEVER PUBLISH UNTIL SOMETHING IS PERFECT. We don’t need to see it and I’m not adding any malfunctioning Homebrew to my collection so I ain’t ever gonna test it. The Moderators and Staff can look into such things even when they are not published. That’s their job. Let them do their jobs.
Now, because you have republished the original link you provided is useless and you need to provide a link to the new version of the spell. And a link to your character sheet as well. (Not the share link, the actual URL.) We will be able to see the spell on your character sheet, which is why you don’t need to publish. Don’t publish anything until it is perfect.
Are you perhaps running any ad/popup blockers, browser extensions (like Beyond20), or a VPN that may be interfering with DDB?
PS- if it reduces a creature’s speed that spell should also have the “control” tag as well.
Look mate I didn't know staff could see things that weren't shared. I'd seen a thread somewhere where the person was asked to publish their thing so the person helping could see it. Either way, it works now. What was happening was I had the 3 versions in my collection. I removed the old ones, and the newest one works properly.
Unfortunately, whenever you go to homebrew anything in future, if you attempt to attach any spells you will notice that there are three versions of that spell that will now permanently haunt your ‘brewer forever with no indication which is the correct version. You will never be able to rid yourself of them. And the more stuff that gets republished over and over, the worse it gets. Maybe you don’t care about the side effects, in which case ignore me and publish whatever you want as many times as suits you. But if you want to minimize the impact on your future efforts, don’t publish stuff that isn’t working.
As basic users, all we will be able to see is the text, never the guts. Anyone who would ask another user to publish a malfunctioning homebrew so they could see it is giving bad advice since it won’t actually help and it just makes fixing it more complicated as you discovered due to the multiple versions in your collection. If it hadn’t been published, any edits you made would have worked on the original version without creating duplicates and without your needing to switch versions or police your collection like that.
I’m trying to give you advice to make your life easier mate, not mine. (My life would be easier if I didn’t try to help anybody.) But feel free to ignore me, many folks do. (Until the ghosts get to be a big enough pain in the neck that they wish they hadn’t.)
It was published? Ah geeze. I didn't even follow the link since the screenshots provided the necessary info, so I assumed it was just also provided for the staff's benefit.
(I try to ask certain people to stop telling others to "publish so they can look", and this is why...)
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
I'm pretty recent to the world of homebrewery and am seeing some really cool content. Some of it doesn't work as advertised, particularly with spell leveling. I'm about to attempt my first homebrew spell. wondering if there's a way to test it before publishing? Forgive any noobish questions.
I'm pretty recent to the world of homebrewery and am seeing some really cool content. Some of it doesn't work as advertised, particularly with spell leveling. I'm about to attempt my first homebrew spell. wondering if there's a way to test it before publishing? Forgive any noobish questions.
Absolutely! In fact, you never need to publish any of your homebrews. You can already use any homebrew in Your Homebrew Collection, which automatically includes anything you make unless you remove it. (Removing something from your collection doesn’t delete it, simply stops it from appearing as something you can add to a character.) Not only that, but all of your friends can use it too. All they need to do is join the same campaign with you on this site, and they will also automatically gain access to everything in your collection, and you will also automatically gain access to everything in their collections too.
Publishing is completely unnecessary, is only so that absolute strangers can use it, and is supposed to be only for stuff that has already been thoroughly tested, adjusted, proofread, and edited.
this page was super helpful to me, I do a lot of Homebrew for my one champaign and I always have to go to one of my random character's built for the item/spell and add it to them to test run it. it's helped out a lot in fixing some bugs. however, I was stuck for the longest time on a spell scaling damage die, couldn't figure it out for the longest time. and you guys just helped me out so much! I feel a little silly for not realizing the solution sooner, but I love that it works out so well. the spell I'm working on is called 'Amethyst Storm' basically the user surrounds themselves in a giant bubble of lightning and anyone who fails the dex save is stunned till the start of the user's next turn. I was having a hell of a time with the damage die upscaling and now I'm having a little issue with range because for every spell slot you use you increase the damage die by 1 but you also add 5ft to the range.
dose anyone have a solution for the increase in range issue?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
This is the spell: https://www.dndbeyond.com/spells/1089730-resonating-earth
It's supposed to do +1d6 bludgeoning damage per level above 2, but no matter how many times I tweak and save the spell, it does not show this on a character sheet. Am I doing something wrong, or is it just bugged?
It's mostly correct, but in the At Higher Level, for Modifier "Damage - Budgeoning (4d6)", use Type "Additional Points" instead of "Additional Count".
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
Thanks for pointing that out. I changed it now, will check if it works.
Nope, still doesn't work
Be sure that you Save Changes at the main edit page for the homebrew after you make a change. Also, it might take up to 20 minutes for the changes to percolate over to the character sheet.
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
It's been longer than 20 minutes. I removed the spell from the character last night, then readded it just now. Still doesn't scale properly.
After you change/add/remove a modifier you MUST re-save the entire homebrew using the main [SAVE CHANGES] button under Basic Information or the system won’t pick up your changes. After that it takes 20 minutes. You might need to “wake up” your character sheet by adjusting the level up and down again.
Also, just to point it out the spells description makes absolutely no mention of dealing more damage at higher levels.
However, now that the spell has been published you within need to “create new version” and the old version will haunt your homebrewer forever. It is best practice to not publish anything until it is guaranteed working correctly.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I swear I did press that save button. Just clicked "Create new version" to double check everything (and add text for higher level scaling).
I only published the spell so those in this forum could see it and perhaps test it on their sheets. Just re-published.
Again, NEVER PUBLISH UNTIL SOMETHING IS PERFECT. We don’t need to see it and I’m not adding any malfunctioning Homebrew to my collection so I ain’t ever gonna test it. The Moderators and Staff can look into such things even when they are not published. That’s their job. Let them do their jobs.
Now, because you have republished the original link you provided is useless and you need to provide a link to the new version of the spell. And a link to your character sheet as well. (Not the share link, the actual URL.) We will be able to see the spell on your character sheet, which is why you don’t need to publish. Don’t publish anything until it is perfect.
Are you perhaps running any ad/popup blockers, browser extensions (like Beyond20), or a VPN that may be interfering with DDB?
PS- if it reduces a creature’s speed that spell should also have the “control” tag as well.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Look mate I didn't know staff could see things that weren't shared. I'd seen a thread somewhere where the person was asked to publish their thing so the person helping could see it. Either way, it works now. What was happening was I had the 3 versions in my collection. I removed the old ones, and the newest one works properly.
Good, I’m glad the new one works properly.
Unfortunately, whenever you go to homebrew anything in future, if you attempt to attach any spells you will notice that there are three versions of that spell that will now permanently haunt your ‘brewer forever with no indication which is the correct version. You will never be able to rid yourself of them. And the more stuff that gets republished over and over, the worse it gets. Maybe you don’t care about the side effects, in which case ignore me and publish whatever you want as many times as suits you. But if you want to minimize the impact on your future efforts, don’t publish stuff that isn’t working.
As basic users, all we will be able to see is the text, never the guts. Anyone who would ask another user to publish a malfunctioning homebrew so they could see it is giving bad advice since it won’t actually help and it just makes fixing it more complicated as you discovered due to the multiple versions in your collection. If it hadn’t been published, any edits you made would have worked on the original version without creating duplicates and without your needing to switch versions or police your collection like that.
I’m trying to give you advice to make your life easier mate, not mine. (My life would be easier if I didn’t try to help anybody.) But feel free to ignore me, many folks do. (Until the ghosts get to be a big enough pain in the neck that they wish they hadn’t.)
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
It was published? Ah geeze. I didn't even follow the link since the screenshots provided the necessary info, so I assumed it was just also provided for the staff's benefit.
(I try to ask certain people to stop telling others to "publish so they can look", and this is why...)
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
I know this is 2 years later, but are you always so rude when you're "helping" someone? You're the kind of person that turns people away from D&D
Sorry I offended you.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I'm pretty recent to the world of homebrewery and am seeing some really cool content. Some of it doesn't work as advertised, particularly with spell leveling. I'm about to attempt my first homebrew spell. wondering if there's a way to test it before publishing? Forgive any noobish questions.
Absolutely! In fact, you never need to publish any of your homebrews. You can already use any homebrew in Your Homebrew Collection, which automatically includes anything you make unless you remove it. (Removing something from your collection doesn’t delete it, simply stops it from appearing as something you can add to a character.) Not only that, but all of your friends can use it too. All they need to do is join the same campaign with you on this site, and they will also automatically gain access to everything in your collection, and you will also automatically gain access to everything in their collections too.
Publishing is completely unnecessary, is only so that absolute strangers can use it, and is supposed to be only for stuff that has already been thoroughly tested, adjusted, proofread, and edited.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
this page was super helpful to me, I do a lot of Homebrew for my one champaign and I always have to go to one of my random character's built for the item/spell and add it to them to test run it. it's helped out a lot in fixing some bugs. however, I was stuck for the longest time on a spell scaling damage die, couldn't figure it out for the longest time. and you guys just helped me out so much! I feel a little silly for not realizing the solution sooner, but I love that it works out so well.
the spell I'm working on is called 'Amethyst Storm' basically the user surrounds themselves in a giant bubble of lightning and anyone who fails the dex save is stunned till the start of the user's next turn. I was having a hell of a time with the damage die upscaling and now I'm having a little issue with range because for every spell slot you use you increase the damage die by 1 but you also add 5ft to the range.
dose anyone have a solution for the increase in range issue?