# Velocity (templates/Proxy/velocity.toml), MiniMessage, two centred lines.
# Centred with the font's advance table: area 270 px, space 4 px, bold +1 px per glyph.
# Line 1: 161 px -> 14 spaces; line 2: 166 px -> 13 spaces.
motd = " <#00E5FF>VECTOLYN<#FFD23F>.NET<#FFD23F> ■ [1.8 - 26.3]\n NEW LOBBY • <#FFD23F>JAVA & BEDROCK"
# Java 1.8 to 1.15 (no hex colours): planned as a separate MOTD from our own proxy plugin (stage 3),
# § codes, same centring. Until then these clients get the MOTD above, which Velocity downsamples
# via Adventure: cyan becomes §3 (dark aqua).
motd-legacy-1: " §b§lVECTOLYN§6§l.NET§6 ■ §8§l[§f§l1.8 - 26.3§8§l]"
motd-legacy-2: " §f§lNEW LOBBY§8 • §6§lJAVA & BEDROCK"
# Legacy proxy (templates/Legacy-Proxy/velocity.toml), MiniMessage, same centring. Line 1 shows the network-wide
# range like the main proxy; its clients are 1.8 clients (PandaSpigot 1.8.8 backends), so named 1.8 colours.
# Line 1: 161 px -> 14 spaces; line 2: 169 px -> 13 spaces.
motd = " VECTOLYN.NET ■ [1.8 - 26.3]\n LEGACY 1.8 • JAVA & BEDROCK"
# Geyser (plugins/Geyser-Velocity/config.yml), Bedrock § codes, not centred.
# Bedrock shows motd1 in the server list; per a Geyser source comment the sub-MOTD only shows locally.
primary-motd: "§b§lVECTOLYN§p§l.NET§p ■ §8§l[§f§lJAVA + BEDROCK§8§l]"
secondary-motd: "§f§lNEW LOBBY§8 • §p§lJAVA & BEDROCK"