Skip to main content

Troubleshooting & Limitations

Common messages​

"GriefDefender was not found." Expected if GriefDefender is not installed. No properties are tracked, but the plugin still loads. Install GriefDefender to enable property tracking.

"No worlds are enabled in config.yml." Set worlds.enabled. Nothing is managed until you do — see Configuration → Choosing worlds.

"Failed to load configuration: properties.areas.x has unknown property size" A typo in properties.areas. The message names the key and the valid values (SMALL, STANDARD, LARGE, CUSTOM, COMBINED). Fix it and reload or restart.

Properties are missing or stale​

Reconciliation runs at startup and on /dw reconcile. There is no periodic scan yet, so anything that changed since the last of those will not be reflected. Run /dw reconcile to catch up.

A claim never appears​

Check its world is listed in worlds.enabled and not in worlds.disabled. Also remember that admin claims and subdivisions never appear on their own — admin claims are ignored, and a subclaim counts towards its parent claim. See Configuration → What counts as a property.

A shop restore fails​

QuickShop-Hikari requires, on restore, that the original owner is online, the target block is a valid chest, and there is an empty sign position directly above it. If any of these is missing the restore will not complete. See Shop Lifecycle → Restoring a shop.

Known limitations​

  • Not verified on a live server. The GriefDefender and QuickShop-Hikari integrations are covered by unit tests against fakes, but neither has been exercised against a real instance. Test before production.
  • No periodic reconciliation — only startup and /dw reconcile.
  • /dw reconcile runs synchronously on the main thread, so a very large district will pause the tick for the length of the scan.
  • Shop restore needs the owner online and a chest with free sign space above it, because of QuickShop-Hikari's shop-creation checks.
  • Shop archives preserve configuration, not container contents. Empty the chest before removing or moving a shop.
  • Releasing a whole property is not built yet. GriefDefender can delete a claim but cannot reset the blocks inside it; block reset will come from the WorldEdit archive provider, which is not finished.
  • Legacy records persist. Rows stored before PlotSquared support was removed stay in the database until deleted by hand.
  • Some permission nodes are declared but not yet wired. See Permissions.