Kick Messages

Kick Messages

Custom messages tell players what to fix. Keep them specific enough to help, and read the matching server log before deciding why a check failed.

Configurable messages

Config key	Used for	Supported substitution
kickMessages.missingHidder	Presence not confirmed before the timeout.	None.
kickMessages.blacklistedMods	Normal-mode blacklist rejection.	{mods} and {plural}.
kickMessages.modlistTimeout	Mod-report attempts exhausted.	None.
kickMessages.modlistRequestFailed	Report request/send failure.	None.
kickMessages.modCountExceeded	Configured mod count exceeded.	{maxMods}.
launcherVerification.kickMessage	Detected launcher is denied.	No template substitution; ModSeeker appends the detected launcher name.

{plural} becomes s when more than one blocked ID is named, otherwise it is empty. {player} is not expanded by the current kick/welcome handlers; do not rely on it despite older config comments mentioning it.

For example:

kickMessages:
  missingHidder: "Install Hidder for your Minecraft version to join.\nhttps://modrinth.com/mod/hidder"
  blacklistedMods: "Remove these blocked mods before reconnecting: {mods}"
  modCountExceeded: "This server allows up to {maxMods} reported mods."

Edit these keys inside the existing section and keep its other settings. Double-quoted YAML strings interpret \n as a new line. Apply edits with /modseeker reload.

Messages with fixed wording

Message or opening text	Meaning and next step
Client update required.	Protocol mismatch. Install matching client/server releases.
Security Error: Mod installation incomplete.	Hidder's native library was not available for the launcher challenge. Check the client log and download/platform combination.
Security Error: Client error.	The client failed while handling the challenge. Check its log.
Security Error: Client verification failed.	A native challenge operation returned an error. Collect the client and server reason.
Invalid client verification.	The challenge signature was invalid for the server's recognized client identity. Check the release/custom pair.
Security verification failed.	A report failed validation or did not match the current request. Read the preceding console reason.
Unauthorized mods detected (...)	Advanced mode found unapproved file hashes. Review the intended files.
Mod Verification Failed	Mod-policy evaluation could not complete, including unavailable policy data or unidentified metadata. Check console warnings.
ModSeeker verification is disabled.	Both required checks are switched off; non-bypassed joins are denied.
Launcher verification timed out. or Challenge response too slow.	The launcher check missed its deadline. Check the client and connection.
Unexpected challenge response., Invalid message format., Handshake failed. or Verification failed.	The exchange was invalid or failed. Reconnect with the supported pair and inspect the same-session logs if it repeats.

These messages are not changed through the configurable kick-message keys. A verification error should be investigated as an installation, configuration or protocol problem before drawing conclusions about the player.

Troubleshooting gives the checks for each class of problem.