TAB incompatibility with Velocity ScoreboardAPI and Triton results in missing translations in scoreboard

[dancebunny98]

Describe the bug

Hi @Rexcantor64!

I encountered an issue that arose after introducing the VelocityScoreboardAPI dependency into the TAB plugin.

Before introducing the VelocityScoreboardAPI dependency into the TAB plugin from the author, everything was fine. In new versions, VelocityScoreboardAPI is required, but then translations from triton in the TAB plugin do not work!

How can the bug be reproduced?

Problem:

In previous versions of TAB (before the introduction of VelocityScoreboardAPI), everything worked correctly.
After upgrading to a version that requires VelocityScoreboardAPI, translations from the Triton plugin to the scoreboard stopped working.

What was expected:

Translations from Triton should be displayed in the scoreboard as they were before.
What is actually happening:
Untranslated strings are displayed in the scoreboard.

Configuration:

TAB plugin (version 5.0.7) is installed on Velocity.
TAB-Bridge plugin is installed on Spigot.
Triton plugin is installed on Velocity.

Expected behaviour

https://github.com/NEZNAMY/TAB-Bridge/releases and VelocityScoreboardAPI
5.0.7 works with triton as it does not use https://github.com/NEZNAMY/VelocityScoreboardAPI
Without VelocityScoreboardAPI TAB does not work!
Triton translations in the plugin do not work with VelocityScoreboardAPI and TAB!

Which Spigot fork are you using?

Other (specify below)

What's your server version?

git-Leaf-"83c2468" (MC: 1.20.4) (Implementing API version 1.20.4-R0.1-SNAPSHOT) (Git: 83c2468 on ver/1.20.4)

Which proxy are you using?

Velocity

What's your proxy version?

Velocity 3.3.0-SNAPSHOT (git-0cd069ec-b431)

What's the MC version of your client?

1.20.4

What's the Triton version you're using?

4.0

Additional Information

https://discord.com/channels/395565283047374850/1014321555427315743/1299799021837226025

[diogotcorreia]

Unfortunately this seems to be unfixable given how Triton currently handles packets. Once Triton uses PacketEvents this will likely be fixed as well.

[diogotcorreia]

Work in #461 will fix this issue