Hey everyone,
I’m currently developing a translation system for Minecraft networks and wanted to get some feedback before I go "all-in" with the release.
We all know the struggle with current translation plugins: Either you have to translate everything manually (Triton style), or you have to deal with complex API keys, credit cards at DeepL, and potential server lags during packet interception.
My concept is different:
I’d love to hear your thoughts:
I’m currently developing a translation system for Minecraft networks and wanted to get some feedback before I go "all-in" with the release.
We all know the struggle with current translation plugins: Either you have to translate everything manually (Triton style), or you have to deal with complex API keys, credit cards at DeepL, and potential server lags during packet interception.
My concept is different:
- Plug & Play: No DeepL key required for the admin. I’m hosting a central REST-API that handles everything.
- Global Redis Cache: If a sentence has been translated once (e.g., for another server), it’s pulled instantly from the global cache. This makes it faster and cheaper for everyone.
- Full Packet Coverage: Not just chat. I'm working on Items, GUIs, Scoreboards, and Signs via ProtocolLib.
- Smart Command Protection: The AI won't break your /help or /warp commands.
I’d love to hear your thoughts:
- Would you prefer a "Managed Service" (I handle the API) or would you rather use your own API keys?
- Is a one-time fee + credit-based system fair for you?
- Which feature is more important to you: Real-time player chat or translated GUIs/Items?
