Open PhoenixFireTea opened 4 days ago
In your config.yml change formatter: minimessage
to formatter: legacy
.
This did not fix the issue of the color of the nick not appearing on the nametag, as I mentioned previously. "If I have the formatter set to legacy, the hex color does not appear, and instead placeholders like %essentials_nickname% and %player_displayname% appear without color, as shown below. It appears in-game in chat and on TAB just fine, but not on the nametag itself."
Oh my bad I didn't see the message between the screenshots
I'll check this out tomorrow if I can get my laptop to get intellij working lmfao
Can I please have your entire config please @PhoenixFireTea just for consistency?
Edit since I forgot to mention it: I'm on 1.21.1 if that helps at all. Here is my NameTags Config: https://paste.md-5.net/adoqadufeq.shell
Here is my Essentials Config: https://paste.md-5.net/ekagududud.coffeescript
I have also found that it gives me the following error when I do /nametags-reload when I have my nick set as ΄c3fCoyotea :
[14:33:59 INFO]: Coyotea issued server command: /nick Coyotea ΄c3fCoyotea
[14:34:03 INFO]: Coyotea issued server command: /nametags-reload
[14:34:03 INFO]: Using LEGACY as text formatter.
[14:34:03 WARN]: Async task for NameTags v1.3-commit-ac52164 generated an exception
java.util.ConcurrentModificationException: null
at java.base/java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1863) ~[?:?]
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) ~[?:?]
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) ~[?:?]
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:575) ~[?:?]
at java.base/java.util.stream.AbstractPipeline.evaluateToArrayNode(AbstractPipeline.java:260) ~[?:?]
at java.base/java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:616) ~[?:?]
at java.base/java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:622) ~[?:?]
at java.base/java.util.stream.ReferencePipeline.toList(ReferencePipeline.java:627) ~[?:?]
at DisplayNameTags-1.3.jar/com.mattmx.nametags.config.ConfigDefaultsListener.lambda$registerDefaultRefreshListener$2(ConfigDefaultsListener.java:76) ~[DisplayNameTags-1.3.jar:?]
at DisplayNameTags-1.3.jar/com.mattmx.nametags.entity.trait.RefreshTrait.lambda$onEnable$0(RefreshTrait.java:41) ~[DisplayNameTags-1.3.jar:?]
at io.papermc.paper.threadedregions.scheduler.FoliaAsyncScheduler$AsyncScheduledTask.run(FoliaAsyncScheduler.java:217) ~[paper-1.21.1.jar:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]
@PhoenixFireTea Im not really able to access MC atm to test it, can you see if other legacy formatting things work?
e.g. %luckperms_prefix%
or something for a rank with the meta prefix ❵Rank
When I set my luckperms prefix to prefix.100.&#C70039[Admin]
, and then display it in DisplayNameTags with %luckperms_prefix%
, it does work with the legacy formatter. The %player_displayname%
and %essentials_nickname%
don't get set to the right color and seemingly go to defaults.
code in DisplayNameTags config:
text:
- "%luckperms_prefix%"
- "%player_displayname%"
- "%essentials_nickname%"
I have been attempting to have Essentials nicknames appear in my nametags, but regardless of what I try it does not work. I am not sure if this is supported, but it seemed like it would / could be. Using essentials, I do /nick Coyotea ΄c3fCoyotea. If I have the formatter set to legacy, the hex color does not appear, and instead placeholders like %essentials_nickname% and %player_displayname% appear without color, as shown below. It appears in-game in chat and on TAB just fine, but not on the nametag itself.
If I do minimessage as the formatter, the entire nametag disappears and I get the error that "Legacy formatting codes have been detected in a MiniMessage string - this is unsupported behaviour."