Troubleshooting Guide

Common installation issues, database connectivity problems, and FastAsyncWorldEdit (FAWE) reset failures.

Plugin Fails to Enable on Startup

Check your console logs for these boot failures:

Error: "Unknown dependency: FastAsyncWorldEdit"

ShyamDuels lists FAWE, LuckPerms, packetevents, and PlaceholderAPI as hard dependencies. The server will refuse to load the plugin if any of these are missing from your plugins folder. Ensure all four are installed and enabled.

Error: "Unsupported Class Version Error (Major.Minor 65)"

This indicates that the server JVM is running an older runtime version (e.g. Java 17 or older). The plugin is compiled targeting Java 21 features. Upgrade your server launch configurations to run on Java 21 or newer.

Arena Resets or Block Rollbacks Fail

If blocks placed or broken during duels do not clean up when a match ends:

FAWE API Hooks are Broken

Do not reload the server using /reload. Performing reloads breaks FAWE's internal world wrappers and causes chunk reset queue locks. Always perform complete server restarts (e.g., using /stop) when modifying configs or plugin files.

The Region Boundary is Too Small

If blocks placed near the edge of the arena are not cleaned up, the selection corners do not fully enclose the build region. Stand further back to select a larger diagonal bounding box, then update the corners using:

/arena corner1 ArenaName
/arena corner2 ArenaName

The Arena is Marked as "UNAVAILABLE"

The plugin changes an arena state to UNAVAILABLE if FAWE pastes fail multiple times. Force an immediate block paste and reset the status using:

/arena reset ArenaName

No Arenas Available for a Kit

If players queue for a kit but get No arenas available for this kit while arenas appear free in /arena list, check build mode first:

Matchmaking only claims arenas whose build mode matches the kit. An arena with build enabled will not be used for a non-build kit, and vice versa.

Database Connection Issues

If player ELO statistics do not persist or matches fail to save:

MySQL Credentials are Invalid

If database log warnings display in your console, confirm the username, password, and port properties inside your database.yml configuration file. If using MySQL, verify that the database table exists before starting the server.

SQLite Lock Errors

If multiple threads attempt to read and write database files simultaneously, SQLite can lock up. We recommend switching to MySQL if your server hosts more than 200 concurrent players.