Common Global Message Provider

[CubBossa]

Each shaded TinyTranslation will create its own GlobalTranslator instance. This is okay, but it would be very good if actually the highest version of those instances serves as global and the other globals connect to it via any communication system. They cannot simply reference each other because they technically are different classes. They should, however, be always all be able to parse the latest syntax. What happens in the plugin directory does not be up to date

[CubBossa]

global messages should not be part of base, while a "proxy implementation" should be that only redirects to message service. For message service, JMS comes handy.
Platform implementation then creates the according server Translations instance (no longer global) based on uuids, and server translations can then again be linked, for example via database. Sounds overkill and is definitely overkill, but only then, the editing of a shared file like in /lang/global_styles.properties makes sense.