Documentation

01

Install and activate Nova

1. Download the current Nova JAR.

   The same Nova JAR works with every server version listed below.

2. Install a supported PacketEvents version.

   Nova requires PacketEvents and only starts with one of the versions listed below.

3. Put both plugin JARs in the server’s plugins folder.

   Start the server once. Nova creates config/auth/auth.yml first and adds the remaining configuration files after the license is accepted.

4. Add the license details.

   Open plugins/NovaAntiCheat/config/auth/auth.yml and enter the exact username and license-key issued for the license.

5. Restart and read the startup log.

   Restart the server normally instead of loading either plugin while it is already running. Check the console for the Nova version, PacketEvents version and a successful license message.

Required plugin

Install a tested PacketEvents version

Download PacketEvents from its official release page and install the Spigot plugin JAR. Use 2.13.0 unless your setup requires another supported version.

PacketEvents versions can behave differently. Fully restart the server whenever you change PacketEvents or Nova.

Compatibility

Server support and client support are different

The server version is the Minecraft version running Nova. The client version is the version a player uses to join, either directly or through a plugin such as ViaVersion. A supported client version does not make an unsupported server version compatible.

Server support

Which server versions are stable?

Tested server versions

Nova was installed on all 69 server builds below: 26 Paper builds, 25 Purpur builds and 18 Leaf builds. On every build, it loaded successfully, stayed online and shut down without errors. This confirms that the plugin runs on those builds, but individual checks have not been manually tested in every possible situation on every older release.

The detailed list below ends at 1.21.11 and does not include 26.1 or 26.2. Their current support stages are shown above.

Java version for each server version

Nova requires at least Java 17. Use the Java version shown for your server instead of automatically choosing the newest one installed. The same Nova JAR is used on every supported server version.

Other Paper-compatible server software and versions not listed here may work, but test them on a private server before using them with players.

Client support

Java, Bedrock and Eaglercraft players

Set client-checking.java, client-checking.bedrock and client-checking.eagler independently in config/main.yml. ViaVersion or another version translator can let different client versions join, but it does not add support for server versions that are not listed above.

Nova does not block client versions by default. Servers that choose to enable versionCheck can set their own allow or block rules.

Eaglercraft

Enable Eaglercraft support

Install EaglerXServer on Velocity and EaglerXBackendRPC on each Paper server running Nova. Together, they allow Nova to recognize Eaglercraft players correctly.

1. Install EaglerXServer 1.1.0 on Velocity.

   Place the EaglerXServer JAR in the proxy’s plugins folder.

2. Install EaglerXBackendRPC 1.1.0 on every Paper server running Nova.

   Place it in the same server plugins folder as Nova and PacketEvents.

3. Enable backend RPC in EaglerXServer.

   In Velocity’s plugins/eaglerxserver/settings.toml, set enable_backend_rpc_api = true and use_modernized_channel_names = true.

4. Enable Eaglercraft checking in Nova.

   Set client-checking.eagler to true in config/main.yml. The Java and Bedrock settings beside it can be switched independently when another anticheat handles one of those editions.

5. Fully restart Velocity and every connected Paper server.

   Do not load or reload the proxy plugin, EaglerXBackendRPC, PacketEvents or Nova while the servers are running.

Configuration

What each configuration file controls

Nova Guard / Nova Pro

Server-owner setup

Nova Guard is Nova’s client-side anti-cheat, available exclusively with Nova Pro, and a first-class Guard check category. It does not modify Minecraft, require Fabric or Forge, inject into the client, require Administrator access, or send arbitrary typed keys. It reduces foreground context locally to a capture-quality boolean and never sends window titles or process names; uncertain focus pauses Guard evidence. Ordinary Nova checks remain fully active for Guard-verified players. Standard licenses cannot enable Guard, while ordinary Nova server-side checks remain fully available.

Standalone Paper

1. Have an authenticated Nova Pro license.
2. Set enabled: true in plugins/NovaAntiCheat/config/guard/guard.yml.
3. Ensure the Guard connection can reach the public server.
4. Done.

Velocity

1. Have an authenticated Nova Pro license.
2. Install NovaGuardVelocity.jar in Velocity's plugins folder.
3. Set enabled: true in Nova's config/guard/guard.yml.
4. Done.

Pairing lifecycle

Each NovaGuard launch creates a fresh ephemeral key and pairing code. Players use /nova guard pair <code>; Nova takes the UUID and username from the live command sender. Pairing survives reconnects, Nova server changes and Velocity backend switches while that same process remains alive. It ends immediately on a normal close, after a short control-heartbeat loss, or at the 24-hour maximum. Restarting Guard always requires pairing again. Continuous HID telemetry travels directly to the public Nova server or Velocity gateway, never through the central website backend.

Guard briefly classifies the foreground executable/window and checks its active Windows TCP-owner metadata locally to authorize the real server endpoint. It also processes bounded control identities in memory to maintain held counts. PIDs, socket tables, connection history, titles, process names, exact key identities and typed text are never transmitted or persisted. Server owners must provide any player notice or lawful basis required where they enable Optional or Required Guard.

Players can download Nova Guard and see the privacy details at novaac.top/guard.

Staff tools

Common commands and permissions

nova.* grants every Nova command and alert permission. Give staff only the permissions they need. Nova writes individual-check bypass permissions to permissions.yml; category and family patterns are listed in PERMISSIONS.txt.

Detection

How Nova organizes its checks

Nova groups checks into Combat, Movement, Packet, Player, World, Prediction and Guard. Guard is an independent evidence bucket and appears as [Guard] in alerts; it does not increase ordinary Combat or Movement pressure. Java players also use prediction-based movement checks, while Bedrock players use checks made for Bedrock. In the public check list, the outlines show whether a Java check also supports Eaglercraft or runs only for Java players.

Start with Nova’s default configuration. If you believe an alert is wrong, record the check name, Nova version, PacketEvents version, server version, client version and what the player was doing. Avoid disabling a whole category because of one repeatable problem.

Responses

Setbacks and combat mitigation

Normal and prediction setbacks

Normal setbacks are used by individual movement checks. Prediction setbacks return a player to a valid position when Nova cannot accept their movement. main.yml contains both global switches. In Nova’s GUI, Normal has one global switch and prediction setbacks are controlled separately for each prediction check.

Combat mitigation

Combat mitigation temporarily limits the advantage of a player who repeatedly triggers combat checks. It affects only selected hits, and normal combat gradually returns when the suspicious activity stops.

Web tools

License Panel walkthrough

Open the License Panel and enter the license username and key. The panel shows the plan, expiration date, devices and active servers for that license.

1. Devices: review registered computers or VPSs and reset only ones you no longer use.
2. Instances: review the Minecraft servers currently using the license.
3. Downloads: download the Nova builds included with the plan.
4. Security: review recent sign-ins and block a device or server you do not recognize.
5. Alerts: configure Discord notifications for license and security events.
6. Cloud Sync: review reputation activity when the feature is enabled on a Standard, Pro or Enterprise license.

One HWID represents one physical or virtual machine. One active instance represents one running Minecraft server. Several servers on the same machine normally use one HWID and one instance per server. Servers shown as offline do not use instance capacity.

Developer API

Build directly on Nova’s server state

Other Bukkit plugins can read Nova state, inspect checks and violations, work with prediction context, and integrate Nova Guard into ranked or tournament access flows. Nova owns the API instance and exposes it through its plugin getter, a static helper, and Bukkit’s services manager.

Compatibility

Third-party plugins

Versions marked Tested have been tested in depth with Nova. Versions marked Runtime verified loaded with Nova and passed automated tests, but were not tested in depth. Newer releases need another verification.

Plugins not listed here may still work. Test your exact setup on a private server before using it live, and include the exact plugin version when asking for support.

PlaceholderAPI placeholders

With PlaceholderAPI 2.12.3 installed, Nova provides %nova_version%, %nova_status%, %nova_tps%, %nova_client_edition%, %nova_client_version%, %nova_checks_enabled%, %nova_ping% and %nova_average_ping%, plus the Nova Guard placeholders documented in the full API reference. They show basic server and player status only; they do not expose license keys, machine identity, violation history or moderation data.

Troubleshooting

Fix common problems

Maintenance

Update Nova safely

1. Back up Nova’s configuration and keep the last working JARs.
2. Read the build notes and check whether the required PacketEvents build changed.
3. Update a private test server first, using a copy of the live configuration.
4. Fully restart the server. Do not replace or reload Nova or PacketEvents while it is running.
5. Test normal combat, movement, teleports, vehicles, custom plugins, alerts, setbacks and punishments.
6. Use the build on your live server only after startup and testing complete without errors.

FAQ

Common questions