Common Issues & Fixes

Three issues account for most of the tickets buyers open: a license that stops validating after infrastructure changes, configuration edits that refuse to apply, and a plugin that does not come up at all. All three have short, worked answers — and one general diagnostic flow that solves most everything else before a ticket is needed.

#The general diagnostic flow

1. Check the [status page](/status) — if the license server or the store is down, that alone explains a surprising number of symptoms.
2. Read the startup console — the first error is usually the cause; everything after it is often fallout.
3. Ask what changed recently — an IP, the hardware, the host, the Java version, a config edit. Change and breakage together are rarely a coincidence.
4. Open the product's documentation section — each product's docs cover its own configuration files, commands and requirements.
5. Still stuck? Open a ticket with your order ID and the console output, as described in Contacting Support.

#License rejected after a migration

Licenses are IP-bound and hardware-bound, so a server that changed its IP or its hardware will fail validation by design until staff update the binding. The license and your purchase are fine — only the recorded binding is stale. The fix is one ticket: Requesting a License Reset walks through it, and IP & Hardware Binding explains why it happens.

After the reset, restart your loader — validation now passes against the new binding. If the failure happens with no infrastructure change at all, skip the reset flow and go straight to License Troubleshooting.

#Configuration changes not applying

• Validate the file first. A YAML file with broken indentation is quietly ignored or partially loaded — a validation error in the console at load time is the tell.
• Check you edited the right file, in the right place. Each product keeps its configuration in its own directory under plugins/ — the product's documentation section maps every file.
• Apply the change the way the product expects. Some changes need the product's reload command (BedWars, for example, applies configuration with /bw reload), others are read at startup — the documentation page for the file you edited says which.
• One change at a time. If five edits went in at once and something broke, you are debugging five candidates instead of one.

#Plugin not enabling

1. Confirm the loader ran. Nerotek products activate through your personal loader — a jar dropped into plugins/ without the loader's activation will not come up (see The Personal Loader, Explained).
2. Check the Java version. The products require a modern Java runtime — Java 21+. An old system Java is a classic silent killer.
3. Check the operating system. The personal loader runs on Linux game servers — which is what virtually all production Minecraft servers run anyway.
4. Check dependencies. Each product's documentation lists what must be present — for BedWars, that is PlaceholderAPI as the only required dependency.
5. Read the startup error, then ticket it. If the console names a real error and the steps above do not cover it, the error text plus your order ID is exactly what the ticket needs.