Diagnose a ChestShop sign that does not become a shop
A sign that stays ordinary has failed before any customer payment. Check sign recognition, the linked chest and creation permissions instead of refilling stock or changing the economy balance.
Before you start
ChestShop connects a sign, stock container and economy account. Test the buyer and seller separately: permission to create a shop does not prove stock access or payment works. Read the installed release documentation before changing signs on public shops.
Work through the check
- Reproduce beside a single test chest using the sign layout shown by the installed ChestShop release.
- Check that the sign targets the intended container and that its owner line and item description follow the documented syntax.
- Use an ordinary permitted shopkeeper, watching chat and the server log for the first creation denial or item-parsing error.
- Compare another plain material and an unprotected test location to separate sign formatting from region, spawn or claim restrictions.
What to compare
Leave the failed sign text in your private notes before trying the corrected form. A screenshot can hide spacing or punctuation, so record each line exactly and compare it with the installed release instructions.
Confirm the result
The plugin should acknowledge shop creation and recognize the intended item and quantity. A customer should see a shop response when interacting with that sign.
If the result differs
An unknown item points to parsing or version support; a protection denial points to the creation location. A different sign plugin may intercept interaction, so retain the exact message.
Recover safely
Remove only the unsuccessful test sign after recording its details. Do not delete the shop database or disable all land protection to make sign creation succeed.
Documentation and related help
Check the ChestShop maintainer documentation and ChestShop maintainer reference against your installed release before applying changes.