Skip to content

7 Troubleshooting

Jump to bottom
MaksyKun edited this page Jul 25, 2026 · 1 revision

7 - Troubleshooting

This page lists frequent setup or runtime issues encountered when using Divinity, along with quick solutions. If you can't resolve your issue here, join our Discord for support.

Administrator recovery rules

  • Stop the server and make a timestamped backup before deleting, regenerating, migrating, or replacing plugin data.
  • Reproduce the issue on staging with the same versions before changing production.
  • Change one variable at a time and keep the first relevant console error.
  • Redact passwords, tokens, database hosts, IP addresses, and player data before sharing logs or configuration.

Plugin does not load

Error:
Plugin 'Divinity' could not be loaded: ClassNotFoundException or NoClassDefFoundError

Fix:

  • Check java -version against the Java version required by your Paper build. Current Paper releases may require a newer Java version.
  • Ensure the required CodexCore plugin is installed and loaded before Divinity.
  • Use the server and Divinity versions intended for each other; do not mix jars from unrelated release lines.
  • Read the first Divinity or CodexCore stack trace in logs/latest.log, not only the final disable message.

Missing configuration files or folders

Symptoms:
Files like worth.yml, config.yml, or folders like item_stats/ or modules/ are missing.

Fix:

  • Stop the server and make a timestamped backup of /plugins/Divinity/.
  • Rename only the missing or broken file, then restart to regenerate that default. Do not delete the complete data folder unless you intentionally want to remove player data and all custom content.
  • Make sure the .jar file is valid and not corrupted.
  • Ensure the server account has write permissions in the plugins directory.
  • Compare regenerated defaults with your backup and reapply changes one section at a time.

YAML parsing errors

Symptoms:
The console reports an invalid key, unexpected token, indentation problem, or a module fails during reload.

Fix:

  • Restore the last known-good copy first.
  • Use spaces, preserve indentation, and quote values containing special characters when required.
  • Validate the exact file with a YAML parser, but remember that a generic parser cannot validate Divinity-specific IDs or formulas.
  • Restart and inspect the console. Repeatedly reloading malformed YAML can leave a module only partially available.

Placeholders do not work

Symptoms:
%divinity_itemstat_strength% or %qrpg_damage_fire% show raw text instead of values.

Fix:

  • Confirm PlaceholderAPI is installed.
  • Restart the server after installing both PlaceholderAPI and Divinity.
  • Make sure placeholders are used inside a supported plugin (e.g. TAB, EssentialsX, Scoreboard plugins).

Items do not register in MythicMobs

Symptoms:
MythicMobs throws an error or doesn't recognize a Divinity item.

Fix:

  1. Hold the item you want to import.
  2. Run: /mm items import <itemName>
  3. Use that name in your MythicMobs configs under equipment: or drops:.

Economy features do not work

Symptoms:
Modules like sell or repair don’t function; players can't buy or sell.

Fix:

  • Ensure Vault is installed and hooked into an economy plugin like EssentialsX or CMI.
  • Confirm the relevant module is enabled in config.yml.
  • Check that worth.yml contains pricing entries for the items involved.
  • Confirm there is exactly one active economy provider and that Vault reports it successfully during startup.
  • Test with a non-operator account that has the module command and GUI permissions.

Items have no stats or appear blank

Fix:

  • Use the module's get or give command to create a known test item. Vanilla /give does not create a configured Divinity module item.
  • Review your module item files and make sure keys like material, stats, and type are present.
  • Confirm the referenced tier, stat, damage, defense, socket, module, and item IDs still exist.
  • Restart after changing global item-stat definitions or engine lore.

Permission denied for valid commands

Fix:

  • Test with a non-operator account; operator status can hide permission mistakes.
  • Check the exact divinity.* node from Commands and Permissions.
  • Older setups may use the equivalent quantumrpg.* node.
  • GUI access and command access can be separate permissions.

Still stuck?

If you're still having trouble, join our Discord support channel and include:

  • The first relevant error and surrounding lines from logs/latest.log
  • Paper build, Minecraft version, and java -version
  • Exact Divinity and CodexCore jar versions
  • A list of integration plugins involved in the failure
  • The affected configuration file with passwords, tokens, database hosts, and player data removed
  • Reproduction steps and whether the issue also occurs on staging with default configuration

Clone this wiki locally