[Bug]: FTB Essentials: /nick is incompatible with ChatHeads

[hideki2k02]

Mod

FTB Essentials

Mod version

ftb-essentials-fabric-2001.2.2

Forge / Fabric version

1.20.1 0.16.5

Modpack & version

No response

What issue are you having?

FTB Essentials modifies the player entity's display name, which affects chat, but not the tab display name. This causes it to be incompatible with ChatHeads.

Crashlogs

No response

Steps to reproduce

1. Rename player using /nick
2. ChatHead no longer works

Anything else to note?

Already opened a issue on the ChatHeads Repo dzwdz/chat_heads#113

[Fourmisain]

Just to add to this:

This is only an issue for servers which send system messages instead of player messages, e.g. if they're running No Chat Reports.
(Which this is extremely common nowadays.)

One way to 'fix'* this is to change the player's tab display name too.
I think you can broadcast a ClientboundPlayerInfoUpdatePacket with an UPDATE_DISPLAY_NAME action for that.

Another, (at least partial**) 'fix' is to add back the vanilla chat decorations. What I mean by that is that Vanilla's Player.getDisplayName() returns
decorateDisplayNameComponent(PlayerTeam.formatNameForTeam(getTeam(), getName()))

Ideally, only the value of getName() should be changed here, but currently everything is replaced.
decorateDisplayNameComponent specifically adds a /tell click command on the player's name (you know the thing where you click on a player name and it'll autocomplete the command to dm that player).
Chat Heads looks for those as well to identify the message's sender.

(*) I say 'fix' because I never know what people understand under a nickname. Them being different from the tab display names might intentional. Them not containing a \tell command with the profile name might be intentional - as a sort of anonymization maybe? I never understood it.

(**) I just realized that I'd have to patch Chat Heads to make it fully work for that specific case. It would identify the sender, but it wouldn't know where exactly to place the head.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[manmaed]

Please disregard the previous reply from the stale bot, it's been a bad bot and sent for recycling.