Skip to main content

Configuration

This guide covers all configuration options available in MultiLang.

Configuration File

The main configuration file is located at plugins/MultiLang/config.yml.

Configuration Options

Every title in the config represents a config option. Here’s what each option does:

prefix

The plugin prefix shown in all messages. All messages have this prefix at their start. Example:

storage

The storage type for player language preferences. Options:
  • MYSQL - Store languages in MySQL database (synchronizes across servers)
  • FILE - Store languages in local files
Example:
If you don’t have a MySQL server, you can use FILE storage. If you choose MySQL, you can synchronize player languages across multiple servers.

mysql

MySQL database settings. Only required if storage: MYSQL. Configuration:
If you choose FILE storage, you don’t need to configure MySQL settings.

default

The default language for players who haven’t selected a language yet. Example:

default-base

Default language base64 for the GUI. See the GUI guide for more information. Example:

languages

List of all languages that players can select. Example:

How does autodetect work?

You need to put the Locale code of that language. You can view a list of Minecraft locale codes here. How it works:
  • When a player joins, MultiLang checks their client language
  • If their language matches one in the languages list, it’s automatically selected
  • Players can still manually change their language using /lang
Example:

strings

All translated strings that can be used in placeholders. Structure:
Example:
How to use:
  • The placeholder will be %multilang_example% (PlaceholderAPI) or {multilang_example} (MVdWPlaceholderAPI)
  • If a player’s language is translated, they see the translated text
  • If not translated or language not selected, they see the default text

Complete Example Configuration

Best Practices

  1. Use descriptive identifiers - Choose clear names for your translation strings (e.g., welcome, server_name, player_count)
  2. Always provide defaults - Always include a default value for each string
  3. Organize by category - Group related translations together
  4. Test translations - Always test your translations with players who speak those languages
  5. Keep it simple - Use the identifier system - it’s simple and easy to use!
  • Translating - Learn how to translate entities and plugin messages
  • Messages - Configure plugin messages
  • GUI - Customize the language selection GUI
  • RealTime - Set up real-time translation

Still Confused?

Need help configuring MultiLang? Join our Discord server - we’ll help you configure the plugin!