AnhyLingo

Language Personalization with Commands for All Players:

Players have the option to select languages for system messages, plugin notifications, and the display of game items that support multiple languages. If the language chosen by the player has been added by the administrators, all relevant informational messages will be displayed in that language. In cases where the player has not selected any specific language, the system will use the language settings of the Minecraft client. If the chosen language is not supported in the localization, the player will receive messages in the default language set in the plugin.

1. Set the desired languages

• (no permission is required)
• /lingo set <langs>
• <langs> - can be one or more languages, for example en or en it es. Plugin will search for the translation in order.



2. Resetting the set language

• (no permission is required)
• /lingo reset
• Clears the list of selected languages, the plugin will receive the language from the minecraft client.



3. Get languages

• (no permission is required)
• /lingo get
• View selected languages for translation.

Reloading and information commands:

1. Reloading the plugin

• (with permission anhylingo.reload)
• Reloads the general configuration and language files configurations
• /lingo reload



2. Information about available item localizations

• (with permission anhylingo.items.info)
• Displays a list of "keys" for all items that have a translation in the specified language.

/lingo items list <lang>




3. Show localization for key

• (with permission anhylingo.items.info)
• Shows the name and lore in the specified language for the given key.
• /lingo item <lang> <key>

Working with files

(with permission anhylingo.file.*)

1. File Uploading

   • File YAML AnhyLingo uploading

   • (with permission anhylingo.file.lingo)
   /lingo fl (flingo) link_to_file folder true|false:
   • Uploading language files to subfolders of the AnhyLingo plugin directory.
   • link_to_file: Direct link to the file.
   • folder: Folder where the file is uploaded items|system.
   • true|false: Parameter to determine the possibility of overwriting the file.
   • File requirements: valid yml format, file name corresponds to the pattern xxx_[language_code].yml.
   
   

   • File uploading

   • (with permission anhylingo.file.other)
   /lingo fo (fother) link_to_file directory true|false:
   • Uploading any files into the directory within the server plugins folder.
   • Important: Uploading is only possible in the directories defined as allowed in the plugin configuration file (allowed_directories).
   • If a subdirectory within the allowed directory does not exist, it will be automatically created during the execution of the command.
   • link_to_file: Direct link to the file for download.
   • directory: Target directory for the file within the server plugins directories.
   • true|false: Parameter that determines whether overwriting existing files is allowed.



2. Deleting files

   • Deleting a file

   • (with permission anhylingo.file.other)
   /lingo fd (fdel) directory file_name:
   • Important: Deleting is only possible in the directories defined as allowed in the plugin configuration file (allowed_del_directories).
   • directory: File path.
   • file_name: File name



3. File view

   • View folder contents

   • (with permission anhylingo.file.view)
   /lingo dir [directory]:
   • Displays the contents of the directory folder located in the server plugins directory.
   • If [directory] is set to 0, it will show the contents of the ./plugins/ folder.

Configuration (config.yml)

• The comments in the configuration file explain each point:

Loading YAML content...

Directory Structure

• items: Files with translations of names and lore of custom items.

Loading YAML content...



• system: Files with translations of system messages and messages from plugins.

Loading YAML content...

• Files must have the name format: "xxx_[language_code].yml", for example, "lingo_en.yml", files that do not meet the standard are not read.

An example of using the repository

Class for Language Management:

package myplugin.lang;

import myplugin.MyPlugin;
import ink.anh.lingo.api.lang.LanguageManager;

public class LangMessage extends LanguageManager {

    private static LangMessage instance = null;
    private static final Object LOCK = new Object();

    private LangMessage(MyPlugin plugin) {
        super(plugin, "lang"); // 'lang' is the name of the folder containing language files
    }

    public static LangMessage getInstance(MyPlugin plugin) {
        if (instance == null) {
            synchronized (LOCK) {
                if (instance == null) {
                    instance = new LangMessage(plugin);
                }
            }
        }
        return instance;
    }
}

lang is the name of the folder containing language files.

Files must have the name format: "xxx_[language_code].yml", for example, "name_en.yml", files that do not meet the standard are not read.

The contents of the files must conform to the YAML standard, and have the form key: "Value", where "value" is the translation for the given key in this language.

Initialization in the Plugin Main Class:

import myplugin.lang.LangMessage;
import ink.anh.lingo.api.lang.LanguageManager;

public class MyPlugin extends JavaPlugin {

    private static MyPlugin instance;
    private LanguageManager languageManager;

    @Override
    public void onEnable() {
        instance = this;
        languageManager = LangMessage.getInstance(this);
    }
    
    public static MyPlugin getInstance() {
        return instance;
    }

    public LanguageManager getLanguageManager() {
        return languageManager;
    }
}

Example Use in Other Classes:

import org.bukkit.command.CommandSender;
import org.bukkit.command.ConsoleCommandSender;
import org.bukkit.entity.Player;
import ink.anh.lingo.api.Translator;
import ink.anh.lingo.messages.MessageType;
import ink.anh.lingo.messages.Messenger;
import ink.anh.lingo.utils.LangUtils;

public class OtherClass {

    private MyPlugin plugin;
    private LanguageManager languageManager;

    public OtherClass(MyPlugin plugin) {
        this.plugin = plugin;
        this.languageManager = plugin.getLanguageManager();
    }

    public static String[] checkPlayerPermissions(CommandSender sender, String permission) {
        if (sender instanceof ConsoleCommandSender) {
            return null;
        }

        String[] langs = new String[] {null};
        if (sender instanceof Player) {
            Player player = (Player) sender;
            langs = LangUtils.getPlayerLanguage(player);
            if (!player.hasPermission(permission)) {
                sendMessage(sender, Translator.translateKeyWorld("shop_err_not_have_permission", langs, MyPlugin.getInstance().getLanguageManager()), MessageType.ERROR);
                return langs;
            }
        }
        return langs;
    }

    private static void sendMessage(CommandSender sender, String message, MessageType type) {
        Messenger.sendMessage(MyPlugin.getInstance(), sender, message, type);
    }
}