Seamless translation between two languages in one channel. Or manual translation to various languages.
Fluent uses google translate by default, with Flowery as a fallback.
Fluent also supports Deeple and OpenAI for translations.
Use [p]fluent openai and [p]fluent deepl to set your keys.
Fallback order (If translation fails):
1. OpenAI
2. Deepl
3. Google Translate
4. Flowery
Check the current server's locale
- Usage:
[p]serverlocale
Translate a message
- Usage:
[p]translate <to_language> [message] - Slash Usage:
/translate <to_language> [message]
Base command
- Usage:
[p]fluent - Restricted to:
MOD
Remove a translation button from a message
- Usage:
[p]fluent removebutton <message> <target_lang>
Add a channel that translates all messages to a single language
Unlike [p]fluent add which translates between two languages,
this translates all messages to the specified target language
regardless of the source language.
You can also specify a category channel to translate all channels within it.
- Usage:
[p]fluent only <target_language> [channel=None]
Add a channel and languages to translate between
Tip: Language 1 is the first to be converted. For example, if you expect most of the conversation to be
in english, then make english language 2 to use less api calls.
You can also specify a category channel to translate all channels within it.
- Usage:
[p]fluent add <language1> <language2> [channel=None]
Set a deepl key for translations
- Usage:
[p]fluent deepl - Restricted to:
BOT_OWNER
Set an openai key for translations
- Usage:
[p]fluent openai - Restricted to:
BOT_OWNER
Remove a channel or category from Fluent
- Usage:
[p]fluent remove [channel=None] - Aliases:
delete, del, and rem
View all translation buttons
- Usage:
[p]fluent viewbuttons
Reset the translations for saved buttons, to force a re-translation
- Usage:
[p]fluent resetbuttontranslations
View all fluent channels and categories
- Usage:
[p]fluent view
Add a translation button to a message
- Usage:
[p]fluent addbutton <message> <target_lang> <button_text>