1.20.3+ - Text not bold
Since 1.20.3 text configured to be bold (using &l) may not appear bold. Steps to reproduce are currently unknown, if you have any information that may help, let us know
I had both working and not working groups in my setup. I figured out that the difference was the working gradients were ending with a standard non-hex color. Then I figured out that when I swap and use bold inside gradient instead of gradient inside of bold, the bold works with hex:hex gradients also.
<bold><gradient:#aa0000:red>HELLO1</gradient> </bold> works fine.
<bold><gradient:#aa0000:#ee2222>HELLO2</gradient> </bold> loses bold.
<gradient:#aa0000:#ee2222><bold>HELLO3</bold> </gradient> works fine.
I was able to reproduce the issue in tabprefix/tabsuffix on vanilla 1.20.4 client with fresh build of Paper (1.20.4 build 454) and TAB (4.1.3 #2ff30dd). No other plugins installed, all default configs.
Expected behavior
Bold gradient should work in all described cases.
Steps to reproduce
/tab player NAME tabprefix <bold><gradient:#aa0000:red>HELLO1</gradient> </bold>
/tab player NAME tabprefix <bold><gradient:#aa0000:#ee2222>HELLO2</gradient> </bold>
/tab player NAME tabprefix <gradient:#aa0000:#ee2222><bold>HELLO3</bold> </gradient>
I'm not sure about this one, but I noticed something weird going on with my only hex:color, seems to behave incorrectly in tagprefix, at least in unlimited mode. Needs further testing as I recall something similar from dev env that was gone after a restart:
After testing a bit, I'm not sure if this is even related, as tested with exact same pattern as one working at the time of testing, the issue is still present. Still pretty weird, this one doesn't want to resolve minimessage, but resolves hex colors instead.
Confirmed the issue is still present after a restart. I'm gonna just leave it here for now, for a chance this is related.🤷
Checklist
[X] I am running latest version of the plugin
[X] I have read the wiki to make sure it's not an issue with configuration
[ ] I ticked all of the boxes without actually reading them
[X] I have read the Compatibility wiki page and am not trying to run the plugin on an unsupported server version / platform
[X] I am willing to cooperate to get this issue resolved faster, including providing any additional information requested or testing new builds
Server version
Paper 1.20.4 build 454
TAB version
4.1.3 #2ff30dd
Describe the bug
I had both working and not working groups in my setup. I figured out that the difference was the working gradients were ending with a standard non-hex color. Then I figured out that when I swap and use bold inside gradient instead of gradient inside of bold, the bold works with hex:hex gradients also.
<bold><gradient:#aa0000:red>HELLO1</gradient> </bold>works fine.<bold><gradient:#aa0000:#ee2222>HELLO2</gradient> </bold>loses bold.<gradient:#aa0000:#ee2222><bold>HELLO3</bold> </gradient>works fine.I was able to reproduce the issue in tabprefix/tabsuffix on vanilla 1.20.4 client with fresh build of Paper (1.20.4 build 454) and TAB (4.1.3 #2ff30dd). No other plugins installed, all default configs.
Expected behavior
Bold gradient should work in all described cases.
Steps to reproduce
/tab player NAME tabprefix <bold><gradient:#aa0000:red>HELLO1</gradient> </bold>/tab player NAME tabprefix <bold><gradient:#aa0000:#ee2222>HELLO2</gradient> </bold>/tab player NAME tabprefix <gradient:#aa0000:#ee2222><bold>HELLO3</bold> </gradient>Additional info
Apparently I found another
bugwhile testing this: https://github.com/NEZNAMY/TAB/issues/1253I'm not sure about this one, but I noticed something weird going on with my only hex:color, seems to behave incorrectly in tagprefix, at least in unlimited mode. Needs further testing as I recall something similar from dev env that was gone after a restart:After testing a bit, I'm not sure if this is even related, as tested with exact same pattern as one working at the time of testing, the issue is still present. Still pretty weird, this one doesn't want to resolve minimessage, but resolves hex colors instead.Confirmed the issue is still present after a restart. I'm gonna just leave it here for now, for a chance this is related.🤷Checklist