# Check which ServerListPlus virtual host owns a displayed message

A familiar server address can select a hostname-specific description while the same machine’s numeric address shows a default. Compare those routes deliberately when an edited message seems to appear for only some players.

## Prepare the test

Treat ServerListPlus as an existing integration to maintain, with release-specific compatibility. Preserve its complete configuration before an edit and check which instance answers the public server-list request.

## Make the change

1. Write down the exact multiplayer-list address and port for the affected player. Identify the ServerListPlus instance that handles its status ping, including whether a proxy answers before a backend receives any connection.
2. Preserve the configuration and inspect the Hosts section alongside Default and Personalized. Use the official virtual-host documentation for the deployed version, especially if a Bungee forced-host name participates in the existing selection.
3. Change one mapped description to a short harmless test label using the same valid YAML structure. Apply through the installed supported method, leaving the default and other host mappings unchanged during the experiment.
4. Refresh separate listing entries for the mapped hostname and a known default route. If personalisation is enabled, compare a previously joined test client with a fresh test context so a personalised override does not obscure the host comparison.

## Check the result

Only the intended address should select the trial message, with the default route remaining recognisable. Record the owning instance and relevant mapping so later branding edits do not get repeated on multiple inactive backends.

## If the test fails

Restore the original description if the wrong route changes. Check what hostname the client actually presents and whether another status plugin answers first; do not change DNS or joining ports merely to force an unverified message edit to appear.

Use existing version-appropriate host keys as the starting point. The project’s historical documentation includes proxy-specific naming conventions that should not be copied into a different proxy implementation without compatibility checks.

## References and related help

Check the [official ServerListPlus documentation](https://github.com/Minecrell/ServerListPlus/wiki/Virtual-Hosts) against your installed release before using a command or setting from another version.

- [Maintain an existing ServerListPlus configuration safely](https://help.cloudexa-hosting.com/books/minecraft-plugins/page/maintain-an-existing-serverlistplus-configuration-safely)
- [Update Paper, Purpur and plugins safely](https://help.cloudexa-hosting.com/books/game-hosting/page/update-paper-purpur-and-plugins-safely)