Troubleshooting

Every heading here is something that actually happens, with the console output the plugin really emits. If you are seeing something not on this page, the log line is the thing to search for — every message includes an identifier you can grep.

The plugin disables itself on startup

"The JDBC driver for storage.type=SQLITE is not on the classpath"

[ZyAuctions] The JDBC driver for storage.type=SQLITE is not on the classpath.
             Paper downloads it at startup from the libraries listed in plugin.yml —
             check the server had network access on first run.

Paper downloads the database driver from Maven Central the first time the plugin loads. That download failed.

Check the server can reach repo1.maven.org on port 443.
Look further up the log for Paper's own library resolution errors — they are more specific than ours.
On an air-gapped server, copy the libraries/ folder from a machine that has downloaded them once.

"Could not open storage"

[ZyAuctions] Could not open storage (mysql (db.example.com:3306/zyauctions)). The plugin
             will disable itself rather than run without persistence and lose listings.

The stack trace underneath says which part failed. Usually one of:

the database does not exist — the plugin creates its tables, not the database itself;
the user lacks CREATE TABLE;
the host, port or password is wrong;
for SQLite, the data folder is not writable.

The plugin disables itself on purpose here. Running without persistence would mean every listing on the server evaporating at the next restart.

"Could not load language files"

[ZyAuctions] Could not load language files. The plugin cannot run without them and will
             disable itself.

This means the bundled English file could not be read out of the jar, which almost always means the jar is corrupt or was truncated during upload. Re-download it.

Note that a broken file in lang/ does not cause this — those are skipped with a warning and the plugin carries on.

Nothing can be bought or sold

[ZyAuctions] No Vault economy provider found. Listings, purchases and bids are disabled
             until an economy plugin is installed.

Vault is installed but nothing has registered an economy behind it. Install an economy plugin — EssentialsX Economy, CMI, or similar — and restart.

Players see: The auction house has no economy to work with. Ask an admin to install one.

Check what is hooked with /ah info:

Economy: none

A player says their money vanished

Two places to look, in this order.

They bid on an auction. A bid is held from their balance the moment it is placed. They get it back in full when they are outbid, when the seller withdraws the listing, or when an admin removes it — but while they are winning, the money is committed. That is not a bug and there is nothing to fix.

Something actually failed. These lines mean a player is genuinely owed money:

[ZyAuctions] Could not refund 3f2a... their bid of 500.0 on listing 8b1c...
             They are owed this money; check your economy plugin.
[ZyAuctions] Economy refused a deposit of 1140.0 to 3f2a...

Both come from your economy plugin refusing a transaction — a balance cap, a frozen account, a database failure on its side. Fix the cause there, then refund the player by hand using the amount and UUID in the log line.

A listing is stuck past its end time

Expired listings are settled by a task that runs every sweep-interval (5 seconds by default). Up to that long is normal.

Longer than that means the task is not running. Check for an exception during startup, and check /ah info responds at all — if the plugin failed to enable, nothing is sweeping.

Item names or lore show `<something>` literally

A translation file is using a tag that does not exist. The two common causes:

A colour that is not a token. <red>, <gold> and <#FF0000> are not valid here. Use <error>, <warning>, <primary> — the full list is on Appearance.
An argument that message does not have. <price> only works in messages the plugin actually passes a price to. Compare against en_US.reference.yml, which shows exactly which arguments each key gets.

A language file is not loading

[ZyAuctions] Skipping lang/german.yml — 'german' is not a locale name. Use a form like
             de_DE.yml or fr.yml.
[ZyAuctions] Skipping lang/de_DE.yml — no translation keys found in it.
[ZyAuctions] lang/de_DE.yml is not valid YAML: ...

Each case names itself. The third one usually means an unescaped " inside a quoted value, or inconsistent indentation.

Confirm what loaded with /ah info:

Languages: en_US

/ah reload did not change anything

Three things do not respond to a reload:

The storage section. You will see a warning saying so. Restart the server.
Menus a player already has open. They pick up new settings when reopened.
Anything that failed to parse. Look for a warning naming the option — a bad value falls back to the default rather than being applied.

If the language files themselves were broken:

[ZyAuctions] Could not reload language files; keeping the previous ones. Fix the file and
             run /ah reload again.

The plugin keeps running on the last good set of text. Fix the file and reload again.

Recent changes disappeared after a restart

[ZyAuctions] Storage writes did not finish within 10s; some recent changes may not have
             been saved.

The server was stopped while writes were still queued. This should be rare — writes are small and fast. Seeing it repeatedly points at a slow or overloaded database; check MySQL latency, or move to SQLite.

[ZyAuctions] Storage write failed (save listing 8b1c...). The change is live in memory but
             will be lost on restart.

A single write failed. The listing works normally until the next restart, at which point it reverts to its last saved state. The exception underneath says why.

Some listings did not come back after a restart

[ZyAuctions] Skipped 2 listing(s) whose item could not be read. They remain in the
             database; nothing was deleted.

Two items could not be deserialised — almost always because the server was rolled back to an older Minecraft version, and the items were saved in a newer format.

The rows are still in the database and were not touched, so going back to the newer version brings them back. If you are staying on the older version, those specific items are not recoverable and the players will need compensating by hand.

Getting help

Include this when you report a problem:

the full startup block from [ZyAuctions] in your log;
the output of /ah info;
your config.yml;
your server version from /version.

On this page