Examples

💡 Examples for Server Owners

Here are some practical ways to use IGLanguages on your server!

1. Multilingual Welcome Message (Root File)

Make your players feel at home by welcoming them in their own language.

Step 1: Define messages In langs/en_us/messages.yml:

welcome: "&eWelcome &f%player_name% &eto the server!"

In langs/pt_br/messages.yml:

welcome: "&eBem-vindo &f%player_name% &eao servidor!"

Step 2: Use the placeholder Since these are in the root folder, use the key directly:

• %lang_welcome%

2. Translating Scoreboards (Organized Folder)

Make your scoreboard multilingual using PlaceholderAPI!

In langs/en_us/systems/board.yml:

title: "&bMy Server"
money: "Money"

In langs/pt_br/systems/board.yml:

title: "&aMeu Servidor"
money: "Dinheiro"

In your Scoreboard Config: Use the folder.filename_key namespace:

Title: "%lang_systems.board_title%"
Lines:
  - "%lang_systems.board_money%: %vault_eco_balance%"

3. Localization for Menus

If you use DeluxeMenus, you can create fully translated GUIs.

In langs/en_us/menus/main.yml:

title: "Server Menu"
shop: "Shop"

In DeluxeMenus/config.yml:

gui_menus:
  main_menu:
    menu_title: "%lang_menus.main_title%"
    items:
      'shop':
         display_name: "%lang_menus.main_shop%"

4. Parameterized Placeholders (Dynamic Arguments)

Pass dynamic values directly into your translations using {0}, {1}, etc. This lets you reuse the same translation template with different arguments — no need to create a separate key for every variant!

Syntax: %lang_<key>:<arg0>,<arg1>,...%

In langs/en_us/menus/lobby.yml:

server_name: "⚑ Lobby {0}"
server_lore:
  - " ● Connected: {0}"
  - " ● Max Capacity: {1}"

Usage in any plugin config (DeluxeMenus, scoreboard, etc.):

display_name: "%lang_menus.lobby_server_name:#01%"
lore:
  - "%lang_menus.lobby_server_lore:{server_online},{server_max_players}%"

Result:

⚑ Lobby #01
 ● Connected: 42
 ● Max Capacity: 100

How it works

Feature	Syntax	Example
Simple arg	{0}, {1}, ...	%lang_key:value% → replaces {0} with value
Multiple args	Comma-separated	%lang_key:a,b,c% → {0}=a, {1}=b, {2}=c
PAPI in args	Bracket placeholders	%lang_key:{player_name},{server_online}% → resolved automatically
Literal comma	Escape with \,	%lang_key:hello\, world% → arg = hello, world
Missing arg	Left as-is	{2} with only 2 args stays as {2}
No args	Works as before	%lang_key% → fully backward compatible

Tip: Arguments also work inside nested %lang_*% placeholders! If a translation contains %lang_other_key:arg%, the inner placeholder is resolved with its own arguments.

---

Next: Developer-API