I've got the tooltip linking, but be damned if I can get the link to show the spellname and a new colour. What am I missing here? Style change... can't get the ahref to work out right...
I can get the hyperlink to work pretty perfectly but I can't get the hover pop-out window like the one above. Is there a specific setting to make sure that happens?
**Nevermind, I was trying to link a homebrew spell to a homebrew item and spells don't use the same tooltip code at the end so it might be a completely different thing.
I stumbled on this post after working up some homebrew with cross references to other homebrew. I used the browser's console to take a look under the hood at the HTML. Here's what I found:
This will format the tooltip properly for the tooltip type (e.g., monster, item, spell, etc.) and make the tooltip an active link. Just replace the underlined segments with the proper info from your homebrew creation.
I was having the same problem, but then I noticed the "Source Code" button in the top bar of the text edit field. I added the link to the source code in the appropriate spot, and it worked fine.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
It makes sense for private items not to have tooltips, but what about public ones? I haven't seen any on the forums, but I wanted to ask just in case.
No. At this time creating tooltips for homebrew is not supported. Staff did mention ways they could implement it if there's enough interest though.
Site Rules & Guidelines --- Focused Feedback Mega Threads --- Staff Quotes --- Homebrew Tutorial --- Pricing FAQ
Please feel free to message either Sorce or another moderator if you have any concerns.
They really only need to update a few parses. You can manually create a tool tip quite easily on the local end by messing with the inspect console.
DM for the Adventures in Erylia Podcast
Where five friends sit around the table and record themselves playing Dungeons and Dragons
I think I've found a workaround, tooltips are loaded through requests to ddb servers when the user hovers it.
Tooltips for magic items follow the pattern:
https://www.dndbeyond.com/magic-items/{item id}-tooltip?disable-webm=1
So if you visit a homebrew magic item like this one: homebrew magic item you can see the id from the url (48531 in this case)
And adding a link from the editor to the pattern using this id results in:
A Bad Copper
Changing the style of the link to look like a magic item tooltip:
A Bad Copper
And I cast Heroism on the community.
Sorry for the necropost, but does this trick still work? I'm trying it and I'm failing.
I would love to know too...
STILL WORKS GUYS!
404 not found
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I can see it though...
The link doesn't work, but the tooltip does. Strange
I've got the tooltip linking, but be damned if I can get the link to show the spellname and a new colour. What am I missing here? Style change... can't get the ahref to work out right...
I can get the hyperlink to work pretty perfectly but I can't get the hover pop-out window like the one above. Is there a specific setting to make sure that happens?
**Nevermind, I was trying to link a homebrew spell to a homebrew item and spells don't use the same tooltip code at the end so it might be a completely different thing.
I stumbled on this post after working up some homebrew with cross references to other homebrew. I used the browser's console to take a look under the hood at the HTML. Here's what I found:
<a class="tooltip-hover spell-tooltip" href="/spells/detect-thoughts" data-tooltip-href="//www.dndbeyond.com/spells/2067-tooltip?disable-webm=1&disable-webm=1">Detect Thoughts</a>
This will format the tooltip properly for the tooltip type (e.g., monster, item, spell, etc.) and make the tooltip an active link. Just replace the underlined segments with the proper info from your homebrew creation.
I was having the same problem, but then I noticed the "Source Code" button in the top bar of the text edit field. I added the link to the source code in the appropriate spot, and it worked fine.