Greetings!

I have been trying to put together a homebrew race with a couple of awfully particular racial traits with secondary effects that trigger from specific damage types, and I ran into this issue while placing tooltips as part of the trait descriptions.

Though I'm only using a few damage types, I chose to attempt to test this a little more exhaustively and check all of them. In order to do so, I tested the following combinations of input for every damage type as follows (I provide "acid damage" here as the example, and insert the spaces within the bracketed sections to prevent linking these tooltips within this post):

[ rule ]Acid Damage[ /rule ]
[ rule ]acid damage[ /rule ]
[ rule ]Acid damage[ /rule ]
[ rule ]acid Damage[ /rule ]
[ rule ]Acid Damage;Acid[ /rule ]
[ rule ]Acid Damage;acid[ /rule ]
[ rule ]acid damage;Acid[ /rule ]
[ rule ]acid damage;acid[ /rule ]

Based on testing the equivalent of the above example for each damage type, I've determined that the [Tooltip not found] error shows up in the following cases:

Lightning Damage
lightning Damage
Lightning Damage;Lightning
Lightning Damage;lightning

Piercing Damage
piercing Damage
Piercing Damage;Piercing
Piercing Damage;piercing

Psychic Damage;Psychic
Psychic Damage;psychic

Slashing Damage
slashing Damage
Slashing Damage;Slashing
Slashing Damage;slashing

I do not have any significant personal experience with code, so I'm unsure as to the cause of this (though I feel it probably has nothing to do with having custom written text for the tooltip, at least). On a whim, I also tried the entries of "aCiD dAmAgE" and "AcId DaMaGe", and the first one produced the error while the second one didn't, amusingly enough. In any case, I hope this post is of use to someone, for bug fixing purposes.

I have just tested all of these tooltips and they all work for me. All I can speculate is that maybe you've got some zero width characters or other erroneous formatting sneaking in that's disrupting your tooltips. Are you by chance running an extension such as Beyond20 or AboveVTT?

I'm have not been running any extensions on this browser, and I attempted to "Clear Formatting" in the text box of the racial trait entry to no effect.

However, when I went through and manually typed out some of the entries which were giving the error, the tooltips ended up working just fine.

To follow up on this, I checked the remaining entries giving the error, and found there were no extra characters where there shouldn't have been any, even of the zero width sort. Visually the text in the remaining entries giving the error appeared to have nothing non-standard about it, so I put one of those entries through an online unicode text analyser on one browser tab and then typed out the same thing manually on another tab of the same site, and it showed them as identical.

This one's a bit of a mystery, as I can simply copy-paste the entries giving the error and reproduce it as much as I like (even out of a Notepad document that lacks any sort of formatting). I guess it might just be good practice to manually retype any tooltip entry giving the error before considering it possibly bugged, especially if using a non-U.S. layout keyboard for input. Ah well, many thanks for your help, and please accept my apologies for having taken up your time.

Instead of a standard space between the words you have a “no-break space” which looks identical until you look at the raw html. In html it registers as “ ” which was what was throwing off your tooltips. Those automatically get used whenever you paste something here on DDB and then hit space. In future, make sure whatever you paste is bookended by punctuation marks so as to preclude those pesky no-breaks from getting plopped in there.

Oh, I see! I'll keep this in mind in the future. Many thanks!

Happy to help.

Quote from IamSposta >>

Instead of a standard space between the words you have a “no-break space” which looks identical until you look at the raw html. In html it registers as “ ” which was what was throwing off your tooltips. Those automatically get used whenever you paste something here on DDB and then hit space. In future, make sure whatever you paste is bookended by punctuation marks so as to preclude those pesky no-breaks from getting plopped in there.

 Sposta with the detective work!

Similar problem 

This is copied form my </>

<p class="Core-Styles_Core-Body"><strong> Wrathfu l([rule]fire damage;fire[rule] )</strong>. Perhaps the most iconic mindset&nbsp;of the raging barbarian, this mostly manifests as pyrokinesis. The Wrathful mind deals fire&nbsp;damage.</p>

 This is in a subclass if that matters.

Quote from MaesterOlorin >>

Similar problem 

This is copied form my </>

<p class="Core-Styles_Core-Body"><strong> Wrathfu l([rule]fire damage;fire[rule] )</strong>. Perhaps the most iconic mindset&nbsp;of the raging barbarian, this mostly manifests as pyrokinesis. The Wrathful mind deals fire&nbsp;damage.</p>

 This is in a subclass if that matters.

 
The second rule tag is missing the /. 

[rule]fire damage;fire[rule]

Should be

[ rule ]fire damage;fire[ / rule ] (no spaces)

Which will produce:

fire

I can't get any version of tooltip to show up for Psychic Damage -- I've tried [rules], [rule], and [damage] and none of those are working?

[rule]Psychic Damage[/rule]

 Produces:

Psychic Damage

Quote from spamandtuna >>

[ rule ]Psychic damage[ /rule ] = Psychic damage

[ rule ]psychic damage; psychic[ /rule ] = psychic

(You'll have to remove the spaces inside the brackets.)

 
If you use the "insert code block" icon (3rd on the right, after the youtube icon) you can insert the codes as normal without it being processed, so people can copy-paste without needing to remove spaces.