Launcher Verification

Launcher Verification

Launcher verification compares Hidder's detected launcher label with the entries you allow in client-list.yml.

Enable it without blocking everyone

First enable the launcher entries you intend to accept. For example, the generated entry for Prism Launcher uses:

prism:
  enabled: true
  name: "Prism Launcher"

Then set the following in config.yml and reload:

launcherVerification:
  enabled: true
  kickMessage: "Please use an approved launcher to join this server"
  allowUnknownClients: false

All generated entries start with enabled: false. Turning on verification without allowing any applicable launcher can reject all test players.

Generated labels

ID	Display name
prism	Prism Launcher
multimc	MultiMC
atlauncher	ATLauncher
curseforge	CurseForge
modrinth	Modrinth App
gdlauncher	GDLauncher
technic	Technic Launcher
ftb	FTB App
lunar	Lunar Client
badlion	Badlion Client
feather	Feather Client
tlauncher	TLauncher
sklauncher	SKLauncher

These are recognized configuration labels. Their presence does not mean every listed product can load the required Hidder/Fabric combination on every Minecraft version. Confirm your intended client can actually run it.

Unknown launchers

allowUnknownClients: true permits a missing or unknown label. It does not allow a recognized launcher whose entry is disabled, create a new entry, or remove the Hidder requirement.

If a client you intend to allow is detected incorrectly, record the label shown in the server log and check that the user launched the correct instance. Include a redacted client log in a support report if the result persists.

Combine with mod policy

• Keep ModVerification: true for launcher checks plus your chosen blacklist or hash policy.
• Set ModVerification: false for launcher checks alone. This mode does not collect a mod report for policy checking or populate fresh mod-list caches.

ModSeeker requests the launcher challenge when this setting is enabled. Hidder returns the detected label with a signed response. Disabling launcher verification skips that launcher request in the normal ModSeeker flow.

Detection uses launcher signals; it is not an independent guarantee that a launcher or its running client is trustworthy. See Security Overview.