Config escaping "<" in velocity motd

[jeremylvln]

Config escaping "<" in velocity motd

[jeremylvln]

Hi,

This is so weird. The ConfigMap for the ProxyFleet seems to be created correctly:

config-version = "2.5"
bind = "0.0.0.0:25577"
motd = "<red>▓▒░             ⚡</red>   <gradient:red:blue><bold>BridgeSplash</bold></gradient>   <red>⚡             ░▒▓</red>"
show-max-players = 100
online-mode = true
force-key-authentication = true
prevent-client-proxy-connections = false
forwarding-secret-file = "/mnt/shulker/forwarding-secret/key"
player-info-forwarding-mode = "modern"

[servers]
lobby = "localhost:30000"
limbo = "localhost:30001"
try = ["lobby", "limbo"]

[forced-hosts]

[advanced]
haproxy-protocol = false
tcp-fast-open = true

And my init script does nothing except copying the file from the mount volume to the correct place, Velocity expect. So there is something in-between that re-write the file. I continue investigating.

[jeremylvln]

If Velocity is not breaking its own config file (which I'm pretty sure it doesn't), then it means that the culprit is the init script of the Docker image I use, especially this function: https://github.com/itzg/docker-bungeecord/blob/master/scripts/run-bungeecord.sh#L180

Still not sure why, I continue...

[jeremylvln]

I thought it was you that added the

# What should be the MOTD? This gets displayed when the player adds your server to
# their server list. Only MiniMessage format is accepted.

Part in your velocity.toml snippet, but I have the same. So it's Velocity that is nuking its own configuration file. Not sure why.

[jeremylvln]

I found the issue. Shulker was creating Velocity configuration files with a version being 2.5. This was triggering this Velocity migration that was rewriting the MOTD to be a valid MiniMessage (which it was already, that's weird).

I pushed a commit to set the version to 2.6 which should avoid running the migration so fixes the issue. I'll make a release once I confirmed the fix is working

[jeremylvln]

I confirm the commit fixed the issue, I'm creating a release right now! Please confirm me that the problem is solved.

[TropicalShadow]

Thanks for going through and finding the issue, I can confirm it has resolved the issue!