You bought a plugin pack, or picked up a free one. You installed it, it works — but somebody else's server name is showing everywhere: ConConCraft, TheLegend or whatever it happens to be. On the scoreboard, in the tab list, in chat, in the MOTD, in the menus... Replacing all of that with your own server brand is not as easy as it first looks; you have to open dozens of config files and learn the format each one uses. This guide walks through the name and branding changes inside a plugin pack step by step: server name, MOTD, scoreboard, tab, chat, menu titles and notification messages — all of it.

Colour Code Systems: Legacy vs MiniMessage

Before you start, you need to know the two different colour systems. Older plugins use legacy colour codes (things like &a, &4, &l). Modern plugins use the MiniMessage format (<green>, <red>, <bold>).

Legacy Codes

text
&0 = black       &1 = dark blue   &2 = dark green
&3 = dark aqua   &4 = dark red    &5 = dark purple
&6 = gold        &7 = gray        &8 = dark gray
&9 = blue        &a = green       &b = aqua
&c = red         &d = light purple &e = yellow
&f = white       &k = obfuscated  &l = bold
&m = strikethrough &n = underline &o = italic
&r = reset

# Hex codes (1.16+):
&#FF5733

MiniMessage Codes

text
<red>, <green>, <blue>, <yellow>, <aqua>, <gold>
<bold>, <italic>, <underlined>, <strikethrough>, <obfuscated>
<reset>

# Hex:
<#FF5733>

# Gradient:
<gradient:#FF0000:#00FF00>Coloured Text</gradient>

# Rainbow:
<rainbow>Colourful</rainbow>

# Hover and click:
<hover:show_text:'Click!'><click:run_command:/help>Command</click></hover>

1. Server Name and MOTD

The MOTD (Message Of The Day) is the short description shown in the server list. It can be two lines, at most 45 characters wide.

server.properties

properties
# server.properties in the root directory
motd=\u00A7aYOURSERVER\u00A7r \u00A77Survival\n\u00A76&#10;play.yourserver.net &#10;\u00A7e1.20.4

# A simpler alternative:
motd=&aYOURSERVER &7Survival\n&6play.yourserver.net

In practice, though, it is easier to use MOTD plugins:

An Advanced MOTD Plugin

If the pack contains MotdManager, SuperMotd or AdvancedMotd, the real MOTD is managed there; changing server.properties is pointless.

yaml
# plugins/AdvancedMotd/config.yml
motds:
  - line1: '&a&lYOURSERVER &7- &eSurvival'
    line2: '&6play.yourserver.net &8| &b1.20.4'
  - line1: '&c&lYOURSERVER &7- &fEVENT RUNNING'
    line2: '&a+500 Players &7- &emonday event'

sample-players:
  - '&a&lWelcome to our server!'
  - '&7play.yourserver.net'
  - '&e'
  - '&b1.20.4 Paper'
  - '&7Survival &8| &cPvP &8| &aEvents'

2. Chat Format

The chat format is usually managed by EssentialsXChat or DeluxeChat.

EssentialsXChat

yaml
# plugins/EssentialsChat/config.yml
format: '{DISPLAYNAME}&f: &7{MESSAGE}'

group-formats:
  default: '&7{DISPLAYNAME}&f: &7{MESSAGE}'
  vip: '&6[VIP] &e{DISPLAYNAME}&f: &f{MESSAGE}'
  admin: '&c[ADMIN] &4{DISPLAYNAME}&f: &c{MESSAGE}'
  owner: '&4&l[OWNER] &c{DISPLAYNAME}&f: &f&l{MESSAGE}'

DeluxeChat

yaml
# plugins/DeluxeChat/config.yml
formats:
  default:
    priority: 1
    format:
      - '&7{displayname}&f: &7{message}'
    hover: '&7Playtime: &a%statistic_time_played_formatted%'
    click:
      type: suggest_command
      value: /msg {name}
  vip:
    priority: 10
    permission: rank.vip
    format:
      - '&6[VIP] &e{displayname}&f: &f{message}'

3. The Scoreboard (Side Panel)

The scoreboard is usually drawn by FeatherBoard, Scoreboard-revision or the scoreboard module of the TAB plugin.

A Scoreboard With TAB

yaml
# plugins/TAB/config.yml
scoreboard:
  enabled: true
  default-scoreboard: main
  scoreboards:
    main:
      title: '&6&lYOURSERVER'    # TOP TITLE
      lines:
        - '&7&m                    '
        - '&a◆ &fPlayer'
        - '  &7%player%'
        - '
        - '&a◆ &fRank'
        - '  &e%luckperms-prefix%'
        - '
        - '&a◆ &fBalance'
        - '  &6%vault_eco_balance% ₺'
        - '
        - '&a◆ &fOnline'
        - '  &b%server_online% &7/ &b%server_max_players%'
        - '&7&m                    '
        - '&6play.yourserver.net'

5. BungeeCord / Velocity MOTD

If you run a proxy network, the MOTD is managed on the proxy side; whatever the backend servers have in their server.properties is never seen.

BungeeCord config.yml

yaml
listeners:
  - host: 0.0.0.0:25577
    motd: '&a&lYOURSERVER &7Network\n&6play.yourserver.net'
    max_players: 1000

Velocity velocity.toml

toml
[motd]
motd = "<green>YOURSERVER</green>\n<gold>play.yourserver.net</gold>"

6. Menu and GUI Titles

In GUI plugins such as DeluxeMenus, ChestCommands and CS-CoreLib, every menu has its own config. The menu title is usually at the top of the config, in a menu-title or title field.

yaml
# plugins/DeluxeMenus/gui_menus/main.yml
menu_title: '&6&lYOURSERVER - Main Menu'
open_command: menu
size: 54

items:
  welcome:
    material: PAPER
    slot: 22
    display_name: '&a&lWelcome %player%'
    lore:
      - '&7Our server: &eYOURSERVER'
      - '&7IP: &6play.yourserver.net'
      - '&7Discord: &bdiscord.gg/yourserver'

7. The Economy Currency

Your server's currency can carry your own branding instead of a generic Dollar.

yaml
# plugins/EssentialsX/config.yml
currency-symbol: '₺'
currency-names-major:
  - Credit
currency-names-minor:
  - Credit Cent

# Exact starting balance
starting-balance: 100
max-money: 1000000000
min-money: -10000

8. The /spawn, /rules and /vote Messages

These commands are handled by EssentialsX; custom messages such as /rules and /info live in plugins/Essentials/rules.yml and motd.txt.

yaml
# plugins/Essentials/rules.yml
lines:
  - '&8&m                                     '
  - '&6&l   YOURSERVER RULES'
  - '&8&m                                     '
  - '&a1. &fCheating is forbidden'
  - '&a2. &fInsults and swearing are forbidden'
  - '&a3. &fGriefing is forbidden'
  - '&a4. &fAdvertising is forbidden'
  - '&a5. &fToxic behaviour is forbidden'
  - '&8&m                                     '
  - '&cBreak the rules and you get banned!'

9. Finding Every Branded String in the Pack at Once

Instead of hunting for the old server name plugin by plugin, run a bulk search from the Linux command line:

bash
# Searching for the old name in the plugins folder
cd plugins/

# Find every occurrence of "ConConCraft" in the config files
grep -rn "ConConCraft" --include="*.yml" .
grep -rn "ConConCraft" --include="*.json" .
grep -rn "concon" -i --include="*.yml" .  # case-insensitive

# Bulk replace (use with care!)
find . -type f \( -name "*.yml" -o -name "*.json" \) \
  -exec sed -i 's/ConConCraft/YOURSERVER/g' {} +

10. Old Names Left Behind in the Database

Some plugins write their data to MySQL, and the old string stays in the database even after you change the config. Examples: warp descriptions in PlayerWarps, listing descriptions in Auction, ban reasons in BanManager.

sql
# Bulk replace in MySQL
USE mcserver;

-- First find the tables and columns
SHOW TABLES;
DESCRIBE tablename;

-- Replace (carefully)
UPDATE essentials_users SET displayname = REPLACE(displayname, 'ConConCraft', 'YOURSERVER');
UPDATE warps_data SET description = REPLACE(description, 'ConConCraft', 'YOURSERVER');

11. Changing the BungeeCord Brand

When a player opens the F3 debug menu they see Server Brand: Paper. To change that:

With ServerUtils

yaml
# plugins/ServerUtils/config.yml
fake-brand: 'YOURSERVER'

BungeeUtils (for the proxy)

yaml
# plugins/BungeeUtils/config.yml
server-name: YOURSERVER
show-brand: true

12. Webhooks and Discord Integration

If you use DiscordSRV or EssentialsXDiscord, the embed titles sent to Discord need changing too.

yaml
# plugins/DiscordSRV/messages.yml
ServerStartup:
  Message: '**YOURSERVER is online!** Come and enjoy yourselves.'
ServerShutdown:
  Message: '**YOURSERVER is offline.** We will be back soon.'
PlayerJoin:
  Message: '%name% joined the server!'
PlayerQuit:
  Message: '%name% left the server.'

13. Checklist: Every Place That Needs Changing

  • server.properties — motd
  • plugins/AdvancedMotd/config.yml (if present)
  • plugins/EssentialsChat/config.yml — chat format
  • plugins/DeluxeChat/config.yml (if present)
  • plugins/TAB/config.yml — header/footer, scoreboard
  • plugins/FeatherBoard/boards.yml (if present)
  • plugins/DeluxeMenus/gui_menus/*.yml — menu titles
  • plugins/Essentials/messages_en.yml — notification messages
  • plugins/Essentials/rules.yml
  • plugins/LuckPerms/prefixes.yml — rank prefixes
  • plugins/DiscordSRV/messages.yml
  • bungeecord/config.yml (if you run a proxy)
  • The MySQL essentials_users table — display names of players who registered under the old brand

14. Testing

To test after the changes:

  • Look at the MOTD in the server list — try an older MC client too
  • Join the server, open F3 → is the brand right?
  • Run /tab — is the tab list header right?
  • Send a message → is the chat format right?
  • Look at the scoreboard → are the title and the lines right?
  • Open /menu → are the menu titles right?
  • /rules → is the rules text right?
  • Trigger an event that reaches Discord → is the embed right?

Common Mistakes

  • The colour code does not work: the plugin may not understand old legacy codes; switch to MiniMessage
  • The server name still shows the old one: it may be cached; do a full restart instead of /reload
  • The old name in some menus: use grep to find the file you missed
  • The old name on Discord: check the bot's own name as well as the DiscordSRV config
  • Scoreboard lines overflow: you may have gone past the 32 character limit

Custom Rank Tags (OWNER, ADMIN and So On)

Plugin packs usually ship with generic rank labels like VIP, ADMIN and OWNER. Tailoring these to your own server identity strengthens your brand. KEYDAL Projects' Rank Tag Generator produces ready-made rank tags as 122×20 PNGs for tab, scoreboard and Discord.

Where Are Rank Tags Used?

  • The TAB plugin: the rank appears next to the player name in the tab list
  • Chat format: the rank label shows up on every message
  • Scoreboard: the player's rank on the side panel
  • Discord: when chat is synced through DiscordSRV
  • Leaderboards: in the top player list
  • Website: on the admin panel and the ban list page

Unicode Emoji and Icons

Modern servers use emoji and special icons in chat. Defining these in the config makes a difference:

yaml
# plugins/EssentialsChat/chat-icons.yml
icons:
  heart: ❤
  star: ⭐
  crown: 👑
  diamond: ♦
  sword: ⚔
  shield: 🛡
  arrow: ➤
  check: ✓
  cross: ✗
  info: ℹ

# Using them in the chat format
format: '%icon_crown% %luckperms_prefix%%player%&f: &7%message%'

MOTDs for Minecraft Server List Sites

Listing sites such as minecraft-server-list.com and topg.org index your MOTD and show it to players. An MOTD meant to be seen on those sites should be put together like this:

  • First line: server name + game mode (30 characters max)
  • Second line: IP + a promotional line
  • Use colour, but not too much (3-4 colours is enough)
  • Gradients and hex codes do not render properly on listing sites — keep it simple
  • If you do want a hex code, write it in the &#RRGGBB format (some plugins cannot parse it)

Designing Your Own Brand

A brand is not just a name; it is a whole of colour palette, tone, symbols and style. For a consistent brand image, settle these decisions:

  • Primary colour: the hex code to be used in every heading and prefix
  • Secondary colour: the accent, for places you want to emphasise
  • Tone of voice: formal, friendly or humorous?
  • Logo mark: a coloured character or a Unicode symbol
  • Slogan: a one or two word summary of the server

Example: A Brand Book

yaml
# BRAND.yml - keep it as a reference, use the same values in every config
brand:
  name: 'YOURSERVER'
  tagline: 'The best Survival experience around'
  domain: play.yourserver.net
  discord: discord.gg/yourserver

  colors:
    primary: '&6'        # Gold
    secondary: '&e'      # Yellow
    accent: '&a'         # Green
    danger: '&c'         # Red
    muted: '&7'          # Gray

  symbols:
    logo: '♛'
    bullet: '➤'
    arrow: '→'
    check: '✓'

  prefixes:
    chat: '&6&l♛ YOURSERVER &8»'
    broadcast: '&e⚡ &6'
    staff: '&c[STAFF]'

Frequently Asked Questions

The name I changed still shows the old one — could this be a cache issue?

Yes. The player's client cache or the proxy cache may still be holding the old name. The fix: (1) restart the server, (2) have the player restart their client, (3) if you run a proxy, /bungee reload.

I bought the plugin pack — can the seller do the rebranding for me?

Many sellers offer a rebrand service; after you buy the pack they reconfigure it around your server name. It usually costs an extra 200-500 TL, but it saves you hours.

The hex code gives the plugin no colour — why?

If your server version is older than 1.16, it does not support hex codes. 1.16+ is required. The plugin itself also has to be able to parse hex codes; older plugins only support legacy. Moving to MiniMessage is recommended.

What happens if I stay on legacy instead of MiniMessage?

Functionally nothing breaks, but modern plugins (the ones using the Adventure API) are moving to MiniMessage. Staying stuck on the old legacy format will bring incompatibilities in the long run. Migrating to MiniMessage step by step is a good strategy.

Changing Menu and Item Display Names

Item names and lore in GUI menus are a world of their own — most plugins define item display names in their own config. In DeluxeMenus, for example:

yaml
# plugins/DeluxeMenus/gui_menus/shop.yml
items:
  diamond_sword:
    material: DIAMOND_SWORD
    slot: 10
    display_name: '&b&lYOURSERVER Special Sword'
    lore:
      - '&7Only on &6YOURSERVER&7!'
      - '&ePrice: &6%vault_eco_balance%'
      - '
      - '&a▸ Click to buy'
    enchantments:
      - DAMAGE_ALL;5
    item_flags:
      - HIDE_ATTRIBUTES
    commands:
      - '[console] give %player_name% diamond_sword{Enchantments:[{id:sharpness,lvl:5}]} 1'
      - '[message] &a&lYOURSERVER&7: You bought a Diamond Sword!'
      - 'eco take %player_name% 1000'

Text Inside the Quest System

Quest plugins (Quests, BetonQuest) use a great deal of text, from NPC dialogue to quest descriptions. To update it in bulk, first find the quest configs:

bash
# Find the quest config files
find plugins/Quests -type f -name "*.yml" | head -20

# Search for the name in NPC dialogue text
grep -l "oldname" plugins/Quests/quests/

# BetonQuest conversations
ls plugins/BetonQuest/conversations/

Message Management: The messages.yml Standard

In professional plugin packs every message is collected in a single messages.yml file. That matters for maintenance and for localisation alike.

yaml
# plugins/YourServerMessages/messages.yml
# Every plugin references this file (through PlaceholderAPI)

general:
  prefix: '&8[&6YourServer&8] '
  reload: '&aConfiguration reloaded.'
  no-permission: '&cYou do not have permission to use this command.'
  player-only: '&cThis command can only be used by players.'
  invalid-usage: '&cCorrect usage: &7%usage%'
  cooldown: '&e%time% &euntil you can use this again.'

player:
  not-found: '&cNo player named '%player%' was found.'
  offline: '&c'%player%' is currently offline.'

economy:
  insufficient: '&cYou need &e%amount% &ccredits for this.'
  success: '&aTransaction complete. &eRemaining balance: &6%balance%'
  invalid-amount: '&cInvalid amount. Enter a positive number.'

teleport:
  requesting: '&eTeleport request sent. &aAccept: &7/tpaccept'
  countdown: '&eTeleporting in %seconds% seconds...'
  cancelled: '&cTeleport cancelled.'

A Second Language: Running a Multilingual Server

If you attract players from other countries, it pays to install your plugins with support for their languages too. Most plugins support localisation through files such as messages_en.yml, messages_tr.yml and so on.

yaml
# plugins/EssentialsX/config.yml
locale: en  # default language

# per-player language override (an Essentials command)
# /locale <en|tr|de|es>

# plugins/EssentialsX/messages_en.yml is generated automatically
# plugins/EssentialsX/messages_tr.yml works the same way
# Players see messages in the language they picked

A Colour Code Converter Tool

Converting from legacy to MiniMessage by hand is painful. You can use online tools: webui.advntr.dev is the official tester for MiniMessage; it converts legacy codes automatically. The preview updates live.

Advanced Colour Design: Gradients and Hover Effects

In modern Minecraft, messages are not static. With MiniMessage you can add gradients, hover actions and click actions. This noticeably raises the professional feel of your server.

yaml
# Gradient rank tag
vip_prefix: '<gradient:#FFD700:#FFA500><bold>[VIP]</bold></gradient>'

# Rainbow OWNER
owner_prefix: '<rainbow><bold>OWNER</bold></rainbow>'

# Hover text — a tooltip when the mouse is over it
chat_format: '<hover:show_text:"<gold>Playtime: <green>%stat_time%">%prefix%<player></hover>'

# Click action — click the message to run a command
help_link: '<click:run_command:/help>[Click for help]</click>'

# Opening a link
website_ad: '<click:open_url:"https://yourserver.net">[Our website]</click>'

The KEYDAL Gradient Generator

Writing gradients by hand is tedious — with KEYDAL's Gradient Generator you can design one visually and copy the MiniMessage code with a single click.

Brand identity is more than colour and a name; it is the whole experience, from a player's first impression through to chat. Servers that care about the details stand out when it comes to player loyalty.

Always Check Every Plugin's Default Settings

Many plugins write their own default messages to a file on first install. Those messages are usually in English, or in the plugin author's native language. Go through all of your plugins:

bash
# All message files inside the plugin folders
find plugins/*/ -name "messages*.yml" -o -name "lang*.yml" -o -name "text*.yml"

# Open each file and check it
vim plugins/EssentialsX/messages_en.yml

# If it is not there, the plugin may not have generated a default yet;
# wait for the plugin's first run, then check again

When you are still seeing messages in the wrong language after the first week or two of running your pack, track down that plugin's locale file and translate it.

The Welcome Message and Global Broadcasts

Tools that strengthen how the server presents itself to players:

  • /motd: a multi-line welcome message through EssentialsX's motd command
  • Join message: the text shown automatically when a player logs in
  • Broadcast schedule: automatic announcements at regular intervals (the ScheduledAnnouncer plugin)
  • Login rewards: the message shown with the reward given on first login (the LoginRewards plugin)
  • Action bar / title: a large central message (the TitleManager plugin)

A Brand Identity Checklist

Follow this list to adapt your pack fully to your own brand:

  • □ server.properties motd
  • □ Advanced MOTD plugin (if present)
  • □ Chat format (EssentialsX or DeluxeChat)
  • □ Scoreboard (TAB, FeatherBoard)
  • □ Tab header/footer
  • □ Menu titles (DeluxeMenus)
  • □ Rank prefixes (LuckPerms)
  • □ Broadcast messages
  • □ Login message
  • □ Rules text (Essentials rules)
  • □ Info/help text
  • □ Discord bot messages (DiscordSRV)
  • □ Voucher/VIP text
  • □ Achievement messages
  • □ Proxy MOTD (BungeeCord/Velocity)
  • □ The name of the economy currency
  • □ Old display names in the database