You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending item names on a 1.8 server as translatable components to players on 1.13+ such as "item.swordStone.name" the translatable key doesn't get migrated with viaversion before getting sent to the client.
It's sent as {"translate":"item.swordStone.name"} which the client displays as item.swordStone.name in chat.
This only happens when sent with the ViaFacet but if its sent with the CraftBukkitFacet ViaVersions converts the component keys and it displays correctly.
ViaFacet is using ProtocolBased which injects in to ViaVersion "1_16", "1_15_2" to do the hex color stuff but this causes the message to skip the 1.8 to 1.15.2 packet translations steps.
Spoke briefly with @KingOfSquares and @Electroid about this in the past who may be able to advise further.
The text was updated successfully, but these errors were encountered:
When sending item names on a 1.8 server as translatable components to players on 1.13+ such as "item.swordStone.name" the translatable key doesn't get migrated with viaversion before getting sent to the client.
It's sent as
{"translate":"item.swordStone.name"}
which the client displays asitem.swordStone.name
in chat.This only happens when sent with the ViaFacet but if its sent with the CraftBukkitFacet ViaVersions converts the component keys and it displays correctly.
ViaFacet is using ProtocolBased which injects in to ViaVersion "1_16", "1_15_2" to do the hex color stuff but this causes the message to skip the 1.8 to 1.15.2 packet translations steps.
Spoke briefly with @KingOfSquares and @Electroid about this in the past who may be able to advise further.
The text was updated successfully, but these errors were encountered: