MOTD ownership verification: troubleshooting

· MinecraftRating administration

MOTD is the text returned by a Minecraft status request. A personal challenge in this text verifies control of a project. It does not configure Votifier or prove reward delivery. In our Paper test a wrong code was correctly rejected; applying the right code and restarting the server verified ownership.

Apply the challenge

  1. Sign in, add the exact host/port and choose the edition.
  2. Obtain your current code from My servers. Codes belong to individual account claims.
  3. Temporarily set motd=YOUR_CURRENT_CODE in server.properties on a standalone Java server.
  4. Save and restart the correct server process. Editing a file alone does not change its live status reply.
  5. Check the externally visible response at the same address/port. A proxy or MOTD plugin may supply that response instead of the backend properties file.
  6. Confirm in your account. Respect the retry delay; replace an expired code if requested.
  7. After confirmation, restore the normal greeting and apply the setting again.

Use Paper server.properties documentation and the startup guide. For rewards see NuVotifier setup.

FAQ

Verify the process was restarted, the host/port is correct, and no proxy or plugin overrides the external MOTD. Localhost and internal container addresses are not public monitoring targets.

The challenge belongs to its account. Use your own current code; a different user's code must not transfer ownership to you.

A stale code, typo, inaccessible status endpoint, wrong port or external proxy response. Wait for rate limits instead of repeatedly generating challenges.

No. We saw it while configuring a flat-world generator. Check the layer format for that version separately; do not delete an existing world without a backup.

They concern plugin/native-library startup. Our Paper could answer status while VotingPlugin was disabled. Resolve that plugin error independently using the NuVotifier FAQ.

No. Reward transport, keys, ServiceSite, listener and actual command execution require a separate test.

All articles