FAQ¶

Why does `/quest` not open?¶

Check that the player has koraquest.command.open. Also confirm the server is running Paper or Folia with Java 21.

Why does a player see administrator commands?¶

KoraQuest shows administrator commands only when the sender has at least one KoraQuest administrator permission or the koraquest.admin parent permission. Review inherited permissions in LuckPerms.

Why do difficulty names show raw keys?¶

Version 1.1 includes fallback values for Easy, Medium and Hard. Restart the server or run /quest admin reload. Also verify that message/messages.yml is readable and valid YAML.

Why is the wrong remaining time shown?¶

Each quest item reads the reset time from its own cycle. Verify the quest's cycle field and the matching reset configuration under cycles.<name>.reset.

Why do only 14 quests appear?¶

The GUI reserves rows 3–4 for quest icons and displays 14 quests per page. Use the next-page arrow. A default Daily pool of 15 quests automatically creates page 2.

Why are new bundled quests missing?¶

Check:

settings:
  install-bundled-quest-updates: true

Bundled quests are inserted only when their IDs are missing. Existing customized IDs are never overwritten. Reset the relevant cycle to select a new pool.

Why is block-breaking progress not counted?¶

Possible reasons:

The block was placed by a player and count-player-placed-blocks is false.
The world is blacklisted.
The player's gamemode is not whitelisted.
A required WorldGuard region, island or plot check failed.
The quest target does not match the broken material.

Why are mob kills not counted?¶

Review:

anti-exploit:
  kill:
    allowed-spawn-reasons: [NATURAL, SPAWNER]
    count-custom-named-mobs: false
    count-mythic-mobs: true

Plugin-spawned or summoned entities may use a spawn reason not included in the list.

Why does shift-click crafting count incorrectly?¶

KoraQuest 1.1 calculates the real crafted amount for shift-click, number-key and recipe-book crafting. Confirm the server is actually loading version 1.1 with /quest version.

Why did a reward not arrive?¶

KoraQuest stores reward claims before executing them. Check the console for a failing command, confirm the required economy/reward plugin is loaded, then run:

/quest admin retryrewards

A failed reward is not silently discarded.

Can I use KoraQuest on multiple backend servers?¶

Yes. Use MySQL or MariaDB for shared data and enable network synchronization. Give every backend a unique network.server-id. Redis Pub/Sub is optional.

Does KoraQuest support Bedrock players?¶

Yes. Enable Bedrock support and install Floodgate. Bedrock players receive native forms when available; other players use the Java inventory GUI.

PlaceholderAPI returns `0` or `UNAVAILABLE`. Why?¶

KoraQuest placeholders do not block scoreboard threads with database queries. Data must already be cached, normally after the player joins or opens KoraQuest.

Can I add a custom objective from another plugin?¶

Yes. Use KoraQuestAPI.progress(...), progressCustom(...), or register an objective provider. See Developer API.

How do I check for a new version?¶

Run:

/quest update

The update checker uses SpigotMC resource ID 137091. It only reports updates and does not replace the JAR automatically.

Which files should I back up?¶

Back up the entire plugins/KoraQuest folder, especially:

config.yml
quests.yml
message/
data/

For MySQL or MariaDB, also back up the KoraQuest database tables.