1. Download KRYNTHEX for your server version.

2. Download a compatible PacketEvents release.

3. Stop your server.

4. Place both JAR files in the plugins folder.

5. Start your server.

Check the plugin’s status:

/ac status

Open the configuration menu:

/ac config

When updating, back up your KRYNTHEX data folder and replace the old JAR. Keep only one KRYNTHEX JAR installed.

Use a full restart instead of /reload.

Open the configuration menu:

/ac config

Browse detection modules, adjust thresholds, change messages and configure supported responses.

Fresh installations start with shadow mode enabled and automatic punishments disabled.

Test your settings and review findings before enabling automatic actions. Enforcement depends on the check, its settings and safety conditions. Some checks remain review-only.

Existing installations keep their saved settings when updating.

KRYNTHEX can run alongside GrimAC or Vulcan. Both are optional, separately installed plugins.

When either is enabled, KRYNTHEX blocks its own native automatic punishments and lagbacks.

KRYNTHEX can still run observations, send qualifying alerts and relay supported companion alerts. Manual staff actions remain available.

Manage GrimAC or Vulcan’s punishments through that plugin’s settings.

Enable your alerts:

/ac alerts on

Disable your alerts:

/ac alerts off

Show extra alert details:

/ac staffview on

Return to compact alerts:

/ac staffview off

Hide review-only observations:

/ac alerts observations off

Restore your notification defaults:

/ac alerts reset

Each staff member has their own notification preferences. These do not change the server’s detection settings.

Add a player to your watch list:

/ac watch <player>

Filter alerts to watched players:

/ac watchmode on

Receive alerts for everyone again:

/ac watchmode off

Clear your list and disable filtering:

/ac watch clear

Adding a player does not enable filtering automatically.

View a player summary:

/ac inspect <player>

Review movement diagnostics:

/ac inspect <player> movement

View protocol information:

/ac inspect <player> network

Review recent findings:

/ac history <player>

Check detection and alert eligibility:

/ac diagnose <player>

An alert gives staff something to investigate. It does not prove a player is cheating.

View a player’s reported client brand:

/ac brand <player>

View additional brand information:

/ac brand <player> details

Review brand changes during the connection:

/ac brand <player> history

Browse online players’ reported brands:

/ac brands

Client brands are self-reported and can be spoofed. A Fabric or Forge brand does not reveal installed mods.

A brand name alone is not evidence of cheating.

Administration access:

krynthexac.admin

Receive staff alerts:

krynthexac.alerts

Additional permission required for manual bans:

krynthexac.ban

Exemption from checks:

krynthexac.bypass

Only give bypass permission to players you intend to exempt.

• KRYNTHEX version.

• Server software and Minecraft version.

• The player’s Minecraft version.

• PacketEvents version.

• ViaVersion version, if installed.

• Check name and exact alert message.

• Steps to reproduce the problem.

• Whether GrimAC or Vulcan was running.

Keep server passwords and other credentials out of reports.

Start a recording before reproducing the issue:

/ac record <player> start

Reproduce the problem, then stop the recording or let it finish:

/ac record <player> stop

Once saved, review the latest recording:

/ac recordings summary latest

Share recordings with trusted staff.